Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
2022.3.38f1
6000.0.11f1
Issue ID
UUM-76244
Regression
No
[XR]Shadows in the Player are hard when using soft shadows
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/DevDunkStudio/ShadowReceiverURP/Samples/Scenes/ShadowReceiverDemo.unity” Scene
3. Switch to Android Platform
4. Build and Run
5. Observe the Player
Expected result: The first 4 shadows from the camera are soft
Actual result: Mostly hard shadows are present
Reproducible with: 2022.3.38f1, 6000.0.11f1
Could not test with: 2021.3.40f1 (error CS0246: The type or namespace name 'PointerOverLinkTagEvent' could not be found)
Reproducible on:
Windows 10 Enterprise 21H2
Play Mode (Windows Platform)
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: Exynos 9 (9825), GPU: Mali-G76
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
Not reproducible on:
Play Mode (Android Platform)
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- Reproducible with Mono and IL2CPP
- Reproducible with OpenGLES3 and 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
- Invalid Clip Method
- WebGPU error with Fantasy Kingdom and GPU Resident Drawer
- WebGPU fails with height fog in Fantasy Kingdom
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
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.
Resolution Note (6000.0.X):
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.