Blueprint Debugger
summary
Visual Studio gains a Blueprint debugger that surfaces Blueprint stack frames and shows which Blueprint node calls C++ methods, demonstrated by tracing an AttachWeapon call to BP_Pickup_Rifle → AttachWeapon node → OnPickup event. Without the optional Unreal plugin VS shows only names and types; with the plugin it populates the Locals window with pin values in Locals and node inputs (example: DPWeapon instance visible), removing editor/IDE context switches and working as shown in the live pickup demo.
AI-written summary · about
chapters (6)
- 0:00Blueprint Debugger intro
- 3:37Context switching problem
- 4:19Solution and plugin benefits
- 5:04Demo setup and breakpoint
- 8:19Enhanced debugging plugin
- 11:12Summary
related talks
06mMy favorite feature in Visual C++ Update 3
07mUnreal Engine and Game Development in Visual Studio
02mVisualizing Macro Expansion in Visual Studio
05mImproving Windows debuggers from the inside out
04mHot Reload for C++
37mBehind Enemy Lines - Reverse Engineering C++ in Modern Ages
24mEmbedded development with VS and VS Code
53mDebug C++ Without Running