Search Issue Tracker
Feature Request
Feature Request in 6000.1.X
Votes
0
Found in
2021.3.45f1
2022.3.52f1
6000.0.26f1
6000.1.0a7
Issue ID
UUM-87040
Regression
No
[XR] LODs switch between high and low poly when Objects are near the center of the screen and switch when near the periphery vision
Steps to reproduce:
1. Open the attached user's project "1978190.7z"
2. Enable Meta link on your Quest 2/3 device
3. Open "SampleScene.unity" and enter Play Mode
4. Move the HMD up and down and observe the chair model LOD switching between low and high poly
Expected results: LOD does no switch no matter where the object is located on the HMD screen
Actual results: The high LOD pops in when the object is near the center of the screen but pops out when the object is near the periphery of the screen (See attached repro.mp4)
Reproducible with: 2021.3.45f1, 2022.3.52f1, 6000.0.26f1, 6000.1.0a3
Testing Environment: Windows 11 23H2
Not reproducible on: no other environment tested
Notes:
-Issue reproduces with OculusXR and OpenXR plugins
-Increasing the "LOD Bias" doesn't eliminate the issue
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
Resolution Note:
This behavior is as designed. The comments include additional recommendations on how to address this issue, including an example script for optimized custom LOD selection.
Resolution Note (6000.1.X):
This behavior is as designed. The comments include additional recommendations on how to address this issue, including an example script for optimized custom LOD selection.