Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
2021.3.30f1
2022.3.8f1
2023.1.10f1
2023.2.0b7
2023.3.0a3
6000.0.0b11
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
7000.0.0a1
Issue ID
UUM-47681
Regression
No
Calculated Mipmap level does not taking XR resolution into account
Steps to reproduce:
1. Open the attached user project "VRMipMaps.zip"
2. Build and run the player on Quest 2
3. Observe the test Texture changing
Expected results: Texture is affected by VR resolution, not by the screen resolution
Actual results: Texture is affected by screen resolution, not VR resolution
Reproducible with: 2021.3.30f1, 2022.3.8f1, 2023.1.10f1, 2023.2.0b7, 2023.3.0a3
Reproducible on: Windows 10 2H22
Not reproducible on: No other environment tested
Notes:
-Tested with both OpenXR and OculusXR plugins
-When deploying to Quest, the 1D backbuffer is still created, but not used. To reduce the impact of this, Screen.SetResolution is used to decrease the size. When setting the Screen resolution to a reduced resolution, the calculated mipmap level is affected, reducing the quality of these Textures.
-Issue is not reproducible on a Non VR Standalone player
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
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
- Flickering bright white dots in the Scene when the Android Platform is selected and DX11 Graphics API is used with Iris(R) Xe Graphics GPU
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
Resolution Note:
Postpone, U7 ports.