is presently its sole maintainer,
You can support him:
Run the game and consider how to develop the profiler
handmade_debug.cpp: Make DrawProfileIn do PushRectOutline instead of PushRect
handmade_render_group.cpp: Introduce a PushRectOutline that takes the same arguments as PushRect
Run the game and see that the outlined rectangles don't seem to be correct
Debugger: Step into PushRectOutline and inspect its values
handmade_render_group.cpp: Make PushRectOutline use the thickness
handmade_debug.cpp: Get that thickness back in there
Run the game and view the profiler
handmade_debug.cpp: Introduce DrawProfileBars
handmade_debug.cpp: Call DrawProfileBars in DrawProfileIn
Run the game and see that the profile view is the same
handmade_debug.cpp: Call DrawProfileBars recursively
Run the game and view the entire call stack in the profile
handmade_debug.h: Introduce MouseTextStackY to enable us to see information for multiple debug elements
Run the game and see this information
handmade_debug.cpp: Introduce GetLineAdvance to give us a more robust way to write multiple lines
Run the game and see our correctly spaced lines
win32_handmade.cpp: Increase the PushBufferSize
Run the game, view the profiler and consider implementing zoom
handmade_debug.cpp: Begin to implement zoom
handmade_debug.h: Introduce debug_view_profile_graph
handmade_debug.cpp: Provide the ability to set RootNode based on a search
handmade_debug.h and handmade_debug.cpp: Provide the ability to set the profile graph root for zooming
Run the game and try out the zoom
Debugger: Break into DEBUGEndInteract and inspect the values upon zooming
Debugger: Break on ZoomInteraction, inspect the values and find that we're currently picking the wrong Frame
handmade_debug.cpp: Search for the correct Frame to set the RootNode
Run the game and successfully try out the beautiful zoom
deepmist: Q: Are you as productive in a single 8 hour period as you are on the show over 8 sessions?
Popcorn0x90 Q: Do you have that in your current game at work?
jessem3y3r Q: Is our debug tooling sophisticated enough to detect OS slowness, i.e. problems with heap / mem performance, etc? [see Resources, Casey's Blog]
SoysauceTheKid Q: When doing playback, is the debug info showing the past CPU info?
oscarnuwar Q: Only in C/CPP?
cynikhul Q: What type of game is this, e.g. FPS, RPM etc?
Popcorn0x90 Q: Yes profiler!
guitarm87 Q: I discovered why I didn't see the font rendering. I'm on a 2560 x 1440 screen with 200% DPI scaling. Do I have to use a specific resolution to make it work?
erdomina Q: Was there a factor in not implementing moving backwards in the threading system?