You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When checking for a stable hash with the remix runtime debugging mode "geometry hash".
Please describe the feature/improvement?
I find that geometry hash debugging causes a pretty great amount of eye strain due to so many parts of the environment instantly flashing back and forth between different bright colors. It's intense enough that I need to take breaks in between doing it, and I typically don't struggle much with anything in video games or even on the design side of shaders and such.
What would be your solution? (optional)
What I'd prefer is a readout that has a more binary nature to it. Either "stable" or "unstable", which would be determined by tracking each mesh in the scene as soon as you enter the geometry hash view and flagging it as unstable if it ever changes hash. The meshes could be given simple white/grey colors (or any other binary color scheme) to represent whether they are stable or unstable, for both clear readability and minimal eye strain on the user.
This would have the added benefit of being MUCH easier to read from screenshots, because the user would no longer have to interpret the visuals in motion to gather useful info.
Version
0.6.0
Media
No response
The text was updated successfully, but these errors were encountered:
What is the context of the feature/improvement?
When checking for a stable hash with the remix runtime debugging mode "geometry hash".
Please describe the feature/improvement?
I find that geometry hash debugging causes a pretty great amount of eye strain due to so many parts of the environment instantly flashing back and forth between different bright colors. It's intense enough that I need to take breaks in between doing it, and I typically don't struggle much with anything in video games or even on the design side of shaders and such.
What would be your solution? (optional)
What I'd prefer is a readout that has a more binary nature to it. Either "stable" or "unstable", which would be determined by tracking each mesh in the scene as soon as you enter the geometry hash view and flagging it as unstable if it ever changes hash. The meshes could be given simple white/grey colors (or any other binary color scheme) to represent whether they are stable or unstable, for both clear readability and minimal eye strain on the user.
This would have the added benefit of being MUCH easier to read from screenshots, because the user would no longer have to interpret the visuals in motion to gather useful info.
Version
0.6.0
Media
No response
The text was updated successfully, but these errors were encountered: