Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.3.X
Votes
1
Found in
2018.4
2019.4.11f1
2020.2
Issue ID
1281930
Regression
No
Shadows are flickering when Scene is offset from origin and Camera has a low near clip plane
Reproduction steps:
1. Open the user's attached project "914797-ShadowsFlicker.zip"
2. In the Project window under the "Assets/Scenes" open "SampleScene.unity"
3. Enter Play mode
Expected result: Shadows remain static in relation to their objects
Actual result: Shadows are moving randomly in relation to their objects
Reproducible with: 2018.4.27f1, 2019.4.11f1, 2020.1.7f1, 2020.2.0b5
Notes:
-The scene is offset from the origin. It's at (0,0,4000). The near clip plane of the camera was also reduced to 0.01
-The camera has a simple script slowly rotating it
-This behavior is reduced if the near plane is pushed farther and when the scene is moved closer to the origin or if the camera doesn't move
-
florahmelda
Oct 05, 2020 12:52
Online case study help services have become very popular for those seeking business case study writing as they engage the best Case Study Writing Services.
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
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
- [Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
Resolution Note (fix version 2021.1):
Updated shadow ray calculations in monoscopic and stereo contexts to stabilize rays at extreme distances.
Resolution Note (fix version 2020.3):
Fixed in 2020.3.6f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.24f1