Search Issue Tracker
Fixed
Fixed in 2022.3.18f1
Votes
1
Found in
2022.3.17f1
Issue ID
UUM-60005
Regression
No
RenderTexture.Create fails when Texture is 2D but Depth is set to a non-default value (default is 1)
How to reproduce:
- Open the project “IN-62910_Bug.RenderTexture.Create”
- Open “Scene”
- Connect any VR/XR device
- Open Project settings → XR Plug-in Management and select your device
- Observe the Console window
Expected result: TextureXR.slices variable is set to 1 (default)
Actual result: TextureXR.slices variable is set to 2
Reproducible with: 2022.3.17f1
Not Reproducible with: 2021.3.34f1, 2023.2.5f1, 2023.3.0b2
Reproducible with devices: HTC Vive
Reproducible on: Windows 11
Notes:
-The reporting user has noted that the issue is reproducible with the Varjo headset and it was possible to reproduce internally with an Oculus Quest headset.
-This is an already known bug and a fix is being done, the ticket is created for the tracking of 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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2022.3.18f1):
On 2022.3 versions, render texture creation was erroneously checking the volumeDepth field even on non-volumetric texture dimensions. Now it is ignored as per the API docs.