Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.2.6f1
Issue ID
UUM-60627
Regression
No
[HDRP][XR] Graphical Global Illumination artifacts appear when loading XR in runtime with Ray Marched or Ray Traced Screen Space Global Illumination enabled
Steps to reproduce:
1. Open the attached user's project "APV_Repro.zip"
2. Enable Oculus link on Quest 2/3
3. Enter Play Mode
4. Toggle XR Initialization via "V" button on the keyboard
4. Observe Visual artifacts appearing (See attached screen2.png)
Expected Result: no graphical Global Illumination artifacts when loading XR in runtime
Actual Result: Graphical Global Illumination artifacts appear when loading XR in runtime with Ray Marched or Ray Traced Screen Space Global Illumination enabled
Reproducible with: 2023.2.6f1
Could not test on 2021.3.33f1, 2022.3.17f1 due to project errors after downgrading
Could not test on 2023.3.0b3 due to GPU crashing upon initializing XR in Play Mode
Testing Environment: Windows 11
Not reproducible on: No other environment tested
Notes:
-Project uses HDRP
-Issue reproduces with OpenXR and OculusXR
-Issue reproduces only with SinglePass Instanced
-Issue reproduces in-built Player
-Additionally, Console window is spammed with these exceptions: "Graphics.CopyTexture called with invalid destination element index (got 1, have 1 elements/layers)"
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
There are no fixes planned for this Bug