Search Issue Tracker
Won't Fix
Votes
0
Found in
Issue ID
1178961
Regression
Yes
Dynamic Clipping works poorly with large scenes / terrains with the pivot point is near
Summary:
Basically the Dynamic Clipping (which is set by default) works very poorly with large scenes, especially terrain, especially when the camera's pivot point is close to the scene view camera.
Repro:
1) Download project ClippingRepro project.
2) Open up the SampeScene.scene.
3) Make sure 'Dynamic Clipping' is set for the scene view camera (at the top right of the scene view > click the camera icon).
4) In the Hierarchy, double click on the "Look at me!!!" game object, which will make the camera zoom to it (also also set the camera's pivot point to it)
5) Now, as seen in the gif, start to zoom towards the cube.
> The far clipping plane will start to cut out the terrain as you do so, alternating between bad and very bad.
This is a problem because it seems like something is very broken with the scene view camera and most users won't know what to do about it.
Reproduced with: 2019.1.0a1
not reproducible with: 2018.4.7f1
Note:
happens with build in and Universal.
Work Around:
Manually set the clipping planes (which may result in new problems, and even bugs)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (2020.1.X):
As of Unity 2019.1 it is possible to set the camera frustum manually, which is noted as a workaround for this case. I spent some time tinkering with the frustum calculations, but failed to find any solution that behaved much better than the current situation and did not introduce additional edge cases. Since this is a relatively rare case, there is a trivial workaround, and no obvious solution to improving the current behavior is apparent I am going to say this is a "won't fix."