-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Render Debug Overlay #22412
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Render Debug Overlay #22412
Conversation
|
You added a new feature but didn't update the readme. Please run |
|
This generally needs a cleanup pass, I was mostly interested if others thought this was a sensible approach for the shader and bindings. 🙂 |
This comment was marked as outdated.
This comment was marked as outdated.
|
I've wanted this for a while. I'll try to get to a review this weekend. |
| } | ||
| } | ||
|
|
||
| /// Automatically attach keybinds to make renderer debugging tools immediately available without |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't that the same comment as the handle_input system?
IceSentry
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be cool if there was a way to render that to an intermediate texture so we could throw it in a UI node and have a bunch of those debug views in separate textures. Definitely more of a long term idea, doesn't have to be in this PR.
Other than the comment that looks copied LGTM
Objective
Solution
Testing
Showcase
Screen.Recording.2026-01-07.at.8.41.08.PM.mp4