Add pages on graphics debugging and profiling #11253
Draft
+494
−1
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
Calinou
added
content:new page
contributing/development/debugging/using_graphics_debuggers.rst
Outdated
Show resolved
Hide resolved
contributing/development/debugging/using_graphics_debuggers.rst
Outdated
Show resolved
Hide resolved
contributing/development/debugging/using_graphics_debuggers.rst
Outdated
Show resolved
Hide resolved
Calinou
force-pushed
the
add-graphics-debugging-profiling
branch
from
61e71bc to
6e9e998
Compare
TODO: - Document how to make use of markers in RenderDoc. Using `--verbose` doesn't seem to suffice for Vulkan on Linux at least (although it works on Windows in NSight). - Document how to access shader sources in RenderDoc. Using `--generate-spirv-debug-info` currently doesn't work due to an engine bug. - Document Radeon GPU profiling in graphics profiling page. - Document Radeon Memory Visualizer in graphics profiling page.
Calinou
force-pushed
the
add-graphics-debugging-profiling
branch
from
6e9e998 to
a0c161d
Compare
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.
This documentation is aimed at new and returning rendering contributors (as well as users wishing to get more information than with Godot's own visual profiler). It aims to describe basic usage of GPU debugging/profiling tools on Godot projects.
TODO
Render Sky) in RenderDoc. Starting Godot with--verbosedoesn't seem to suffice for Vulkan on Linux at least (although it works on Windows in NSight).--generate-spirv-debug-infocurrently doesn't work due to an engine bug.