Uploaded August 2022 | Updated September 2026, 1 hour ago
👨💻 Compile, run-time, or logic errors?! There are several things that could go wrong when running your own Unity game. XR Bootcamp Instructor Ian Berget walks you through the process of where to look for answers, find out what's going on, and what might go wrong.
💡 Unity Troubleshooting Tips:
1. Save your error messages for search terms
2. Remove project-specific keywords
3. Start with official documentation for errors and methods
4. Check multiple Stack Overflow answers, the more recent the better!
5. Add breakpoints before code triggering error messages. The real issue might be much earlier.
6. Use two breakpoints if the execution order isn't clear. Check which breaks first.
7. Valid code isn't always correct. When there's no error message you need to discover the issue yourself.
8. Rubber duck debugging: Explain your code to whoever will listen aloud. You'll spot your own errors even if your audience doesn't.
---
👉 About XR Bootcamp:
XR Bootcamp is a global online academy, offering beginner to advanced-level VR/AR Master Classes and Bootcamps.
xrbootcamp.com
---
👋Join the XR Creators Discord discord.gg/38THNzEh4P
If you have questions, feel free to join the server and connect with the community. Or, if you feel like you're able to mentor young talents, show your skills and answer questions! We welcome everyone, beginner and advanced-level VR developers! !
⌚ Timestamps
🔔 Subscribe to the XR Bootcamp channel!
https://www.youtube.com/channel/UCTMO...
👨💻 Compile, run-time, or logic errors?! There are several things that could go wrong when running your own Unity game. XR Bootcamp Instructor Ian Berget walks you through the process of where to look for answers, find out what's going on, and what might go wrong.
💡 Unity Troubleshooting Tips:
1. Save your error messages for search terms
2. Remove project-specific keywords
3. Start with official documentation for errors and methods
4. Check multiple Stack Overflow answers, the more recent the better!
5. Add breakpoints before code triggering error messages. The real issue might be much earlier.
6. Use two breakpoints if the execution order isn't clear. Check which breaks first.
7. Valid code isn't always correct. When there's no error message you need to discover the issue yourself.
8. Rubber duck debugging: Explain your code to whoever will listen aloud. You'll spot your own errors even if your audience doesn't.
---
👉 About XR Bootcamp:
XR Bootcamp is a global online academy, offering beginner to advanced-level VR/AR Master Classes and Bootcamps.
xrbootcamp.com
---
👋Join the XR Creators Discord discord.gg/38THNzEh4P
If you have questions, feel free to join the server and connect with the community. Or, if you feel like you're able to mentor young talents, show your skills and answer questions! We welcome everyone, beginner and advanced-level VR developers! !
⌚ Timestamps
🔔 Subscribe to the XR Bootcamp channel!
https://www.youtube.com/channel/UCTMO...
