Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.64f1
6000.3.0f1
6000.4.0b1
Issue ID
UUM-130621
Regression
No
GameObject with custom shader shows visual corruption due to incorrect previous transform matrix while using Active SpaceWarp
Reproduction steps:
1. Open the attached project “ReproProject“
2. Switch to the Android platform in Build Profiles (File → Build Profiles → Select Android, press “Switch Profile”)
3. Build the Player
4. Launch the Player on the device
5. Observe the result on the device
Actual result: Visual corruption can be seen on child “Line“ GameObject
Expected result: No visual corruption on “Line“ GameObject
Reproducible in (OculusXR): 4.1.1 (6000.0.9f1, 6000.0.64f1, 6000.3.0f1, 6000.4.0b1), 4.5.2 (6000.0.9f1, 6000.0.64f1, 6000.3.0f1, 6000.4.0b1)
Reproducible in (OpenXR): 1.14.3 (6000.1.17f1, 6000.3.0f1, 6000.4.0b1), 1.16.1 (6000.1.17f1, 6000.3.0f1, 6000.4.0b1)
Could not test in:
- Editor: 6000.0.8f1 (no native support for ASW feature in URP), 6000.5.0a3 (unsolvable compilation errors)
- Player OculusXR: 4.0.0 (Player crashes upon launching)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Reproducible on devices:
- Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno (TM) 740
- Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650
Notes:
- The feature in OpenXR was introduced in the 6000.1 stream
- Legacy method (for 6000.0.8f1 and older) of enabling the feature produces compilation errors when trying to test
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
- Text Script Importer Reference button links to a Missing Page when clicking the Reference Button in the Inspector
- FrameTimingManager.GetLatestTimings adds background time to the next focused frame when the Player is unfocused
- PropertyDrawer gets disposed while still being active when adding a secondary component
Add comment