Debugging in visual studio is the most powerful debugging tool I’ve used. It’s the standard I measure all other debugging tools against
It’s worth your time to get really good at debugging in VS. Learn how to set break points, how to set watches on your variables, how to go up and down the call stack, how to look at your object memory, etc.
When I get really deep into the weeds with debugging something, I often create a notepad++ document and start copy/pasting debug information I want to track.
One really handy tip for debugging unreal games: When you want to debug something, press the “pause” button on your keyboard. The game will freeze its frame. Then you can open up a blueprint and set a breakpoint. Then, open the game window up and press “pause” again to unpause the game. If that blueprint executes any code on the next frame, you’ll hit your breakpoint with your instance variables. If you have the engine code available, you can also view the engine code for each blueprint node and step through that, line by line, to see what’s happening behind the scenes.
Protip: Make sure that you compile your game with “DebugGame Editor” configuration.