Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.11f1
2018.4.0f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1178077
Regression
No
Visual Studio breakpoint is not hit if it's placed inside a namespace that is not used in the scene
How to reproduce:
1. Open the "Breakpoint_Broken.zip" project
2. Open the "ExampleScene.unity" scene
3. Open the vList.cs in Visual Studio
4. Add a breakpoint on line 54 (Debug.Log) and attach debugger to Unity
5. Enter Play Mode
Actual result: The message is logged, but the breakpoint is not hit.
Expected result: The breakpoint is hit.
Reproducible with: 2020.1.0a2, 2019.3.0b1, 2019.2.3f1, 2018.4.8f1.
Notes:
- Uncommenting line "public vList<string> listOfStrings = new vList<string>();" DebugBroken.cs:10 resolves the issue as it makes the vTime namespace usable in the script.
- Adding any other MonoBehaviour with usable vTime namespace to the scene resolves the issue.
- Can't test Unity 2017.4 because of compiler errors.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (2020.1.X):
This bug has been forwarded to the VSTU team.