Search Issue Tracker
Fixed
Fixed in 6000.2.X, 6000.2.0b2
Votes
0
Found in
6000.2.0b2
Issue ID
UUM-105398
Regression
Yes
Scene View stops rendering when Scene Camera is moved in first person with Isometric perspective
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Enable the Cameras overlay in the Scene View
- Enable the "Control a camera" mode in the Cameras overlay
- Enable the Isometric perspective
- Move the camera around with right-click
- Return to Scene camera (Disable the "Control a camera" mode in the Cameras overlay)
- Observe the Scene View
Actual results: The Scene View is gray and nothing is rendered in the scene
Expected results: Everything is rendered properly the same as at the beginning of the reproduction
Reproducible with versions: 6000.2.0b2
Not reproducible with versions: 6000.0.49f1, 6000.1.4f1, 6000.2.0b1
Tested on (OS): macOS Silicon Sequoia 15.3, Ubuntu 22.04, Windows 11
Notes:
- When moving the camera around in step 5, the perspective icon in the Scene View is jittering
- Restarting the Editor does not fix the issue
- Closing the Scene View and reopening the Scene View fixes the issue
- Creating a GameObject after step 6 throws an error:"Invalid worldAABB. Object is too large or too far away from the origin."
- The MainCamera position is changed to very random numbers, resetting the transform does not fix the issue
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 6000.2):
Reverting the PR causing the issue.