Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The documentation now reflects the current renderer behaviour, including previously undocumented limitations of direct drawing identified during the investigation.
The compute shader documentation includes a complete mesh-generation guide covering:
A placeholder page was also added for a future high-level compute API. The expanded low-level examples show the amount of setup currently required and why a higher-level API would be useful.
Writing and testing these examples also exposed limitations in the current rendering pipeline, which are now documented. These changes describe existing functionality and behaviour.
For the proposed renderer changes addressing these limitations, see Renderer V2 proposal. This PR focuses on documenting the current renderer and compute shader usage.