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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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.