Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0a1
2018.2.14f1
2018.3.0a1
2019.1.0a1
Issue ID
1108606
Regression
No
GameObjects glitch out in Game view when their world coordinates are set to a large number
Steps to reproduce:
1. Open original project
2. Press "Play"
3. Press the "Move" UI button in the top right corner until coordinates show "5000"
4. Observe "UnityChan" GameObject
Expected results: Rendering of the GameObject should not be affected by the world coordinates.
Actual results: GameObject starts displaying visual artifacts when world scale is set to a large number (video included).
Reproduced in: 2017.4.18f1, 2018.3.2f1, 2019.1.0a13
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note:
Similar issues will occur in Unity when using floating point precision in large scales, same with multiple cases like terrain and lighting. Won't fix.