Search Issue Tracker
Won't Fix
Won't Fix in 2017.4.X, 2018.1.X
Votes
0
Found in
2018.1.0b3
Issue ID
989379
Regression
Yes
[VR] Directional Light shadows render at low resolution
iOS, iPhone 7, GLES and Metal, Cardboard
Android, Note 5, GLES, Oculus
Android, Pixel 2, GLES, Daydream
Even with Quality Settings at maximum, shadows cast from Directional Light (both baked and realtime) render at a very low resolution. Point light and spot light render correctly.
Steps to repro:
1) Create a scene that uses directional light (can be baked or realtime)
2) Build to iOS/cardboard
3) Observe shadows
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Shadow Artifacts appear while using directional light with Single Pass Instanced stereo rendering Mode.
- Checked with Oculus Rift (Windows Standalone)
- Unity Version 2019.1.0b4
Occurs only with directional light shadow if the output is directed to VR headset.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
XR Management has evaluated this issue and determined that it does not meet our current bug severity threshold. If you would like your issue to be reviewed again, please re-submit your bug.
Resolution Note (2017.4.X):
XR Management has evaluated this issue and determined that it does not meet our current bug severity threshold. If you would like your issue to be reviewed again, please re-submit your bug.