Search Issue Tracker
Fixed
Fixed in 2022.2.2f1, 2023.1.0a20
Votes
0
Found in
2022.1.18f1
2022.2.0b13
2023.1.0a16
Issue ID
UUM-15576
Regression
Yes
CameraDepthTexture's TexelSize is unexplainably set to (1,1,1,1) when the actual values is not supposed to be at (1,1,1,1)
Reproduction steps:
# Open the attached project
# Observe the CameraDepthTexture TexelSize at the top-left corner of the Game View
Expected result: The TexelSize is at (0.00, 0.00, 849.00, 478.00)
Actual result: The TexelSize is at (1,1,1,1)
Reproducible with: 2022.1.0b1, 2022.1.18f1,
Not reproducible with: 2020.3.40f1, 2021.3.11f1, 2022.1.0a16, 2022.2.0b9, 2023.1.0a12
Reproducible on: Windows 10 (21H2)
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
Add comment