Search Issue Tracker
Won't Fix
Votes
1
Found in
2020.3.43f1
2021.3.16f1
2022.2.2f1
2023.1.0a25
Issue ID
UUM-24668
Regression
No
[GLES] Camera stops rendering subtractive shadows when reentering Camera view
Steps to reproduce:
1. Open the attached project “BugRepro”
2. Build and Run the project on Meta Quest 2
3. Observe the shadow under the cube
4. Look away and back and/or wait until the other camera rotates away and back.
Expected result: The shadow under the Cube is present
Actual result: The shadow under the Cube disappears
Reproducible with: 2020.3.43f1, 2021.3.16f1, 2022.1.24f1, 2022.2.2f1, 2023.1.0a25
Reproducible on: Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Built using MacOS 12.4 (Intel)
Notes: Toggling Vulkan options in Oculus settings may be necessary, go to “Edit > Project Settings > XR Plug-in Management > Oculus” and turn off the settings that are for Vulkan
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 CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.