Search Issue Tracker
Fixed in 2022.3.52f1
Fixed in 2022.3.X, 6000.0.X, 6000.1.0a2, 7000.0.0a7
Votes
0
Found in
2022.3.50f1
6000.0.23f1
6000.1.0a1
Issue ID
UUM-84287
Regression
Yes
GameObject's shadows affected by custom shaders change their scale and position when the Scene camera is adjusted
How to reproduce:
1. Open the attached “IN-85278” project
2. Open the “TestShadows” Scene
3. If needed, arrange the Editor layout so that both the Scene and Game windows are visible simultaneously
4. Observe the Game window and note the position of the "Sphere" GameObject's shadow.
5. Rotate and scale the camera view in the Scene window, and observe the behavior of the "Sphere" GameObject's shadow in the Game window
Expected result: The shadow of the "Sphere" GameObject remains unchanged regardless of the Scene window camera view adjustments
Actual result: The shadow of the "Sphere" GameObject dynamically changes as the Scene window camera view is adjusted
Reproducible in: 2022.3.23f1, 2022.3.50f1, 6000.0.23f1
Not reproducible in: 2021.3.44f1, 2022.3.22f1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: The issue does not affect the project's build
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
Add comment