Search Issue Tracker
Fixed
Fixed in 2022.3.23f1, 2023.2.17f1, 6000.0.0b14
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.35f1
2022.3.19f1
2023.2.9f1
2023.3.0b6
6000.0.0b13
Issue ID
UUM-63267
Regression
No
[URP] Incorrect unity_WorldToCamera and unity_CameraToWorld matrices are set when performing the ShadowCaster pass
How to reproduce:
1. Open the attached “WorldToCameraMatrixRepro.zip“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Observe the shadow of the “Capsule“ GameObject in the Game view
4. Rotate the Scene view Camera
5. Observe the shadow of the “Capsule“ GameObject in the Game view
Expected result: The shadow of the “Capsule“ GameObject stays the same
Actual result: The shadow of the “Capsule“ GameObject moves
Reproducible with: 2021.3.35f1, 2022.3.19f1, 2023.2.9f1, 2023.3.0b6
Reproducible on: macOS 14.2.1 Sonoma (Intel)
Not reproducible on: No other environment tested
Notes:
- This issue can be observed more easily if the Game view and Scene view are placed side by side and then entering Play Mode and rotating the Scene view Camera
- The user noted that in the Frame Debugger, the unity_WorldToCamera matrix inside the MainLightShadow pass is different from the one inside the DrawOpaqueObjects pass
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
- Shadows are not cast when the Light's CullingMask and the GameObject's Layer do not match
- Graphics.DrawMeshInstanced does not work when 2D Renderer and 2D Shaders are used
- SpeedTree does not move when using WindZone
- "Undeclared identifier 'LinearToSRGB'" error is thrown when creating a color variable with HDR color mode and assigning a Custom Render Texture target in Shader Graph
- Input System package is missing when creating a new HDRP project
Resolution Note (2021.3.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The issue will be fixed in 2022.3 and later versions.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.