Search Issue Tracker
Won't Fix
Votes
1
Found in
2022.3.19f1
2023.2.9f1
Issue ID
UUM-62842
Regression
No
URP Shadows are inconsistently rendered when observed in the Player
Reproduction steps:
1. Open the attached “Egg Game.zip” Project
2. Open the “BaseScene” and enter the Play mode
3. Move in the Game so that the “słoiki (3)” (Jar) GameObject is visible, using WASD keys
4. Observe the “słoiki (3)” GameObjects' shadow on the wall while moving up and down
5. Exit the Play mode
6. Build and Run the Project (File > Build and Run)
7. Repeat 3rd and 4th steps
Expected result: “słoiki (3)” GameObjects' shadow on the wall is consistently shown, like in the Play mode
Actual result: “słoiki (3)” GameObjects'' shadow disappears based on the Players' position
Reproducible with: 2022.3.19f1, 2023.2.9f1
Couldn’t test with: 2021.3.34f1 (Unfixable compiler errors due to downgrading), 2023.3.0b6 (3rd Party Package associated errors)
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Note:
- Build would usually only be successful on the second try
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
- Unity Events added to a ScriptableObject are not invoked if they are added in Edit mode and their Call State is set to "Runtime Only"
- The Visual Effect GPU Event is forced into sleep until another Event is sent when the visual effect consists of two particle systems that communicate with Trigger Event set to On Die
- Nativeplugin Vulkan image gets deleted while in use and AccessTexture returns an invalid texture causing a crash or corruption when QualitySettings.anisotropicFiltering is called
- Error "DllNotFoundException: __Internal assembly:<unknown assembly> type:<unknown type> member:(null)" when attaching a managed debugger for the build of a specific project with Mono Scripting Backend
- Unable to select UI Toolkit Foldout element when using a gamepad controller
Resolution Note:
The keywords for Main Light Shadows were incorrectly set up. In the shader it was possible to have both _MAIN_LIGHT_SHADOWS and _MAIN_LIGHT_SHADOWS_CASCADE enabled at the same time, which is incorrect as only one should be active. Fixing that solves the issue presented in this case.