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
- A shader error is thrown when building a project containing a material using "Bent normal map"
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
Add comment