Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.1.0f3
Issue ID
934880
Regression
No
Using Flythrough mode, you can get out of scene view bounds
Scrolling back with a mouse there are boundaries which stops you from scrolling further. Using flythrough mode tho, you can evade those boundaries and go out of scene view boundaries and corrupt the whole scene view.
To reproduce:
1.Create new Unity project
2.Open scene view
3.Click right mouse button to enter flythrough mode
4.While in flythrough mode go forward with W + SHIFT until you start to see scene view corrupting
Reproduced on: 5.4.6f1 5.6.2p4 2017.1.0f3 2017.3.0a1
Using Unity 5.4.6f1 you get these error in the console: transform.position assign attempt for 'SceneCamera' is not valid. Input position is { NaN, NaN, NaN }.
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
mickaelb_simthetiq
Feb 16, 2018 18:38
I need to add there is another issue with Flythrough mode. If you are in this mode and you have something which blocks the next frame update (like loading a big additive scene in my case), during the next update, the sceneview camera is usually out of bounds since its position is computed using time elapsed, last position and speed. I don't think it cares about time elapsed to update the frame.