Debugging Godot C# Games with Visual Studio Code (Godot Series, Part 6)
In this episode, dotnet demonstrates essential debugging techniques for C# game development in Godot, using both Godot and Visual Studio Code tools to help developers confidently troubleshoot common game issues.
Debugging in Godot & Visual Studio Code (Part 6 of 9)
Author: dotnet
Debugging is an essential process in game development. In this video, the .NET team walks through practical techniques to diagnose and fix issues in Godot C# projects, leveraging both Godot's built-in debugging features and Visual Studio Code's debugging capabilities.
Key Topics Covered
- Godot’s Built-In Debugging Tools: Learn to use Godot’s debugger and Remote tab for live scene data inspection.
- Visualizing Collisions: Visualize collision shapes and physics bodies to better understand gameplay issues.
- Using Print, Warnings, and Errors: Add diagnostic output to trace problems.
- Visual Studio Code Debugging: Set standard and conditional breakpoints, use watch expressions, examine the call stack, and explore the debug console.
- Challenge: Try adding conditional breakpoints that trigger only when certain values are met, pausing gameplay to inspect state.
Timeline
- 00:04 Debugging Mindset: Bugs Are Normal
- 00:36 Godot’s Built-In Debugging Tools
- 01:03 Inspecting Live Scene Data with Remote Tab
- 01:52 Using Print, Warnings, and Errors
- 02:58 Visualizing Collision Shapes
- 04:30 Debugging in Visual Studio Code
- 05:30 Breakpoints, Watch Expressions, and Call Stack
- 07:00 Conditional Breakpoints Explained
- 08:30 Logging and Hit Count Breakpoints
- 10:00 Wait-For Breakpoint Demo
- 11:00 Wrap-Up and Coding Challenge
Resources
Connect with .NET:
Summary
Whether you’re troubleshooting physics or input problems, this hands-on video gives you actionable tools for understanding what’s really happening inside your Godot C# games. The conditional breakpoint challenge helps you build confidence as you debug more effectively.