Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0f3
Issue ID
897134
Regression
Yes
[Mac] Debugger corrupts vector2 values
Repro steps:
1. Open the provided scene
2. Open the script
3. Press the "Play" button in MonoDevelop
4. Add a breakpoint on line 10 (where the vector2 is declared)
5. Enter play mode in Unity
6. Press the "Step over" button in MonoDevelop
7. Hover over the "v" in "Vector2 v =..." until a menu pops up
8. Expand the pop up menu
9. See that the values have changed to nonsense
Expected: to see the same values as declared before.
Actual: the values have changed drastically
Reproduced with: 2017.1.0a6, 5.6.0f3, 5.5.3f3
Working with: 5.4.5f1 (regression here)
Bug only happens on a mac
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Standalone Profiler recording data with Play Mode target selection when Play Mode is not entered
- [HDRP] Assertion printed when Maximum Reflection Probe count is higher than 64 due to k_MaxCubeReflectionsOnScreen when Raytracing is enabled
- Seams are visible on the Water System when multiple tiles are used and their Surface type is set to River
- Matching Game View creates unsaved changes even though nothing to save
- AudioClips do not have path or GUID in Build Report and incorrect size is reported
Add comment