Search Issue Tracker
Won't Fix
Votes
2
Found in
2022.3.0f1
2023.1.0b19
2023.2.0a17
2023.3.0a3
6000.0.0b11
Issue ID
UUM-39724
Regression
Yes
[Oculus] Lights causing artifacts when Forward+ Rendering is selected
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Connect Quest 2 with Oculus Link
4. Enter the Play Mode
5. Observe the shown Scene in Quest 2 from different angles
Expected result: No artifacts appear in the Scene
Actual result: Artifacts are being drawn by the light as seen in Repro.jpg
Reproducible with: 2022.2.0a16, 2022.3.0f1, 2023.1.0b19, 2023.2.0a17, 2023.3.0a16
Not reproducible with: 2021.3.26f1, 2022.2.0a15
Could not test with:
Reproducible with devices:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Testing environment: Windows 10 Enterprise 21H2
Notes:
- Reproduces with the Android Player
- Reproduces in Play Mode with Windows and Android Platform
- Reproduces when using Forward+ Rendering
- Reproduces with Windows Standalone Player built-in Development and Release
- Reproduces with OpenXR and Oculus XR
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
- Warnings in the Bug Reporter window are cut off and not truncated when the Bug Reporter window is resized to its minimum size
- Color is incorrectly applied to objects when initialized with non-normalized parameters
- SerializationUtility.GetManagedReferencesWithMissingTypes() don't return null when “Prefab has missing SerializeReference Types“ warning banner is present
- Memory leak when VFX Graph is open and Camera has "Target Texture" enabled
- The Canvas component's warning box is missing an apostrophe when Additional Shader Channels is set to "Normal" and "Tangent" with Render Mode set to "Screen Space - Overlay"
Resolution Note:
We have looked into this case and the issue is not reproducible with 2023.3.0b11. We used the repro project provided in case and tested on Quest2 linked mode.
We believe the issue is fixed by the F+ XR changes added as part of 2023.2.0a10
If you believe the issue still happens, please feel free to reopen and provide more details.