Search Issue Tracker
Fixed
Fixed in 2022.2.0b15, 2023.1.0a18
Votes
0
Found in
2022.2.0b8
2023.1.0a10
Issue ID
UUM-14837
Regression
Yes
[XR] Lights render only when their position is near 0,0,0
Reproduction steps:
# Open the user's attached project
# Enter Play mode
# Observe the Game view
# Put on the VR headset on
# Observe
Expected result: All 5 Point lights work
Actual result: Only 2 Point light works
Reproduced with: 2022.2.0a8, 2022.2.0b8, 2023.1.0a10
Not reproduced with: 2020.3.39f1, 2021.3.9f1, 2022.1.15f1, 2022.2.0a7
Reproducible on: Windows 11, Oculus Rift S
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
- Sahder errors in Player when "Strict shader variant matching" is enabled and the rendering path is set to "Deferred"
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
Resolution Note (fix version 2023.1.0a18):
Fixed in: 2023.1.0a18
Resolution Note (fix version 2022.2.0b15):
Fixed in: 2022.2.0b15