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
- A 404 page is opened when selecting "Open Documentation" on the Emission Node in Shader Graph
- "Kernel 'KMain' not found" errors appear when using the "Screen Space Reflections" Post-Processing effect in a specific WebGL project
- Game View turns black, Scene View turns grey, Console error NullReferenceException when Wireframe is turned on because the DecalGBufferRenderPass references a non existent GBuffer
- A 404 page is opened when selecting "Open Documentation" on the Float Node in Shader Graph
- Shader Graph Importer's Documentation Reference button leads to a 404 page
Resolution Note (2020.1.X):
This bug has been forwarded to the VSTU team.