renderdoc

Tracy [1] is the first thing that comes to my mind, then RenderDoc [2]. After that Visual Studio while debugging. In general, I think graphical debuggers and profiling tools do a relatively good job of packing lots of information into many, small windows. [1] https://github.com/wolfpld/tracy [2] https://github.com/baldurk/renderdoc

Not quite: https://github.com/baldurk/renderdoc/blob/81b4d3d804c1974b0b...

Renderdoc, who has had code to do this since 2021 has a good comment that explains it. https://github.com/baldurk/renderdoc/blob/4a620bb5a16b4de4e2...

heh https://github.com/baldurk/renderdoc#readme is all "RenderDoc is intended for debugging your own programs only. Any discussion of capturing programs that you did not create will not be allowed in any official public RenderDoc setting, including the issue tracker, discord, or via email" but the 3 of the 4 screenshots are of dota2 :-D Still, that looks handy for sure

Renderdoc uses hooking to instrument your 3D API calls to provide excellent graphics debugging. Good example to dive into since it's also cross platform. https://github.com/baldurk/renderdoc I used graphics API hooking in a Source Engine game where I didn't have the source for the engine but needed to display the 2D Flash based GUI (Iggy) at the correct time. It was fun to get it working. Valve's Steam also does something similar since it has the ability to superimpose it's GUI over a running game.

Leaving math library and OS integration to developers is a good thing. Mandating them is already too limiting. Graphical debuggers on the other hand are useful indeed. LunarG stopped working on Glave: https://github.com/LunarG/VulkanTools/commit/87220f80a643860... Not sure what happened there. Valve were sponsoring Glave development. Renderdoc is active (not Linux UI yet however): https://github.com/baldurk/renderdoc

I suspect he's using graphics debugging tools like RenderDoc: https://github.com/baldurk/renderdoc

He used Renderdoc, which lets you pick a frame apart draw call by draw call, inspect shader bytecode, etc. https://github.com/baldurk/renderdoc

From part 3: >Links >The tech that built an empire: how Rockstar created the world of GTA 5 featuring an interview of Aaron Garbut. http://www.techradar.com/news/gaming/the-tech-that-built-an-... >GTA V NVIDIA Performance Guide with details about the different graphics settings. http://www.geforce.com/whats-new/guides/grand-theft-auto-v-p... >Renderdoc which made picking into GTA V internals a breeze. https://github.com/baldurk/renderdoc