Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4.32f1
2020.3.21f1
2021.2.1f1
2022.1.0a14
2023.2.0a1
2023.3.0a3
6000.0.0b11
Issue ID
UUM-7284
Regression
No
[Oculus][XR] VRAM increases significantly when changing XRSettings.eyeTextureResolutionScale at runtime
Reproduction steps:
1. Open the attached “VramBug.zip” project
2. Open the “TestScene” Scene
3. Go to "Edit > Player Settings" and select Plug-in Provider
4. Connect Quest 1/2 and enter Play Mode
5. Enter Play Mode
6. In the Game View use the handle to change the Resolution scale
Expected result: VRAM does not increase significantly when changing XRSettings.eyeTextureResolutionScale at runtime
Actual result: VRAM increases significantly when changing XRSettings.eyeTextureResolutionScale at runtime (See attached Results.png)
Reproduces on: 2019.4.32f1, 2020.3.21f1, 2021.2.1f1, 2022.1.0a14
Notes:
- Issue is not reproducible with MockHMD
- Issue reproduces with all Graphics API's
- Reproduces with both OpenXR and Oculus plugin providers
- According to the user this issue is present in Player and in the Editor
- To observe VRAM usage better open "Task Manager", go to "Details", right-click on the column "Name" then "Select Columns" and tick "Shared GPU Memory". Find Unity and observe VRAM change
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
- Depth of Field doesn't apply correctly to Canvas UI when it is set to World Space Render Mode
- Crash on GetElementMapKey when "None" is assigned to a field with binding path "m_GameObject"
- Stereoscopic skybox renders as monoscopic when using Multi-pass render mode in XR plugin while using URP
- Parameterized Tests with ValueSource fail when supplied parameter is an System.Object
- Error Message "Broken text PPtr in file" is not informative enough to locate the problematic asset
Resolution Note:
There are no fixes planned for this Bug