Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2022.2.10f1
Issue ID
UUM-31995
Regression
No
Terrain shadows flicker while moving the Camera in the Player when Terrain contains GPU instanced materials
Reproduction steps:
1. Open the “Bug Report Shadows” Project
2. Open the “Assets/_Project/Scenes/Bug Report Scene.unity” Scene
3. Enter the Play Mode
4. Use the mouse to move the Camera and observe the flowers' shadows
5. In the top menu select File > Build And Run
6. In the Player repeat 4th step
Expected results: Flower shadows do not change positions
Actual results: Flower shadows change positions, flickering as you rotate the Camera
Reproducible with: 2022.2.10f1, 2023.1.0a18
Not reproducible with: 2023.1.0b7, 2023.2.0a5
Fixed in: 2023.1.0a19
Could not test with: 2020.3.45f1, 2021.3.20f1 (Grass and flowers are not visible)
Reproduced on: Intel MacOS 13.1
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:
We recognize this as a legitimate problem, but in the spirit of transparency we are closing this issue, because we are not going to be able to provide a fix in a near future. If the bug has no workaround and is blocking your production please feel free to reopen it with any additional information you might have. Sorry for the inconvenience this might cause.
This issue has been identified as having low priority and has been closed without a fix. If the bug has no workaround and is blocking your production please feel free to reopen it with any additional information you might have. Sorry for the inconvenience this might cause.
Resolution Note (2022.2.X):
We recognize this as a legitimate problem, but in the spirit of transparency we are closing this issue, because we are not going to be able to provide a fix in a near future. If the bug has no workaround and is blocking your production please feel free to reopen it with any additional information you might have. Sorry for the inconvenience this might cause.
This issue has been identified as having low priority and has been closed without a fix. If the bug has no workaround and is blocking your production please feel free to reopen it with any additional information you might have. Sorry for the inconvenience this might cause.