Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
1
Found in
2023.2.0b3
2023.3.0a3
Issue ID
UUM-45631
Regression
No
[Quest 3][Vulkan][URP] - Some assets render incorrectly on quest 3 hmd
Description
When testing the functionality of Quest 3 in ARFoundation samples, I encountered an issue where URP builds across 2022.3, 2023.1, and 2023.2 Unity Editor versions failed to work properly. Specifically, the left eye displayed plane meshes that overlapped in a grid pattern, which remained fixed to the user's view. On the other hand, the right eye rendered the planes correctly.
In built-in the planes in the project rendered as expected in both eyes. This did not repro on Quest 2 or Quest pro.
This does not repro using GLES only Vulkan graphics API
Repro Steps:
- Open the provided project
- Build and run the project.
- Observe the behavior.
Observed Behavior:
- The plane meshes rendered differently in each eye.
- The overlapping of plane meshes in the left eye resulted in an unusable experience.
Expected Behavior:
- Plane meshes should render the same way in both eyes.
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
The issue is closed for the time being as the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Resolution Note (2023.3.X):
The issue is closed for the time being as the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.