Search Issue Tracker
Fixed
Fixed in 2022.3.21f1, 2023.2.10f1, 2023.3.0a19
Votes
1
Found in
2022.3.13f1
2023.1.20f1
2023.2.0b18
2023.3.0a14
Issue ID
UUM-55999
Regression
Yes
Custom Render Texture Initialization Mode set to Realtime causes Dimensions do not match dimensions of depth surface
Reproduction steps:
1. Open the attached “TestMacOs.zip” project
2. Select the “Assets/Scenes/CustomShaders/RenderTextureWrapper.asset” Custom Render Texture
3. Change the Initialization Mode to “Realtime” in the Inspector window
4. Untick the “Double Buffered” checkbox
5. Observe the Console
Expected result: No errors are present
Actual result: "Dimensions of color surface ("SceneView RT") do not match dimensions of depth surface ("RenderTextureWrapper"): (1101, 514) != (256, 256)" errors are being consistently printed out
Reproducible with: 2022.2.0a11, 2022.1.24f1, 2022.3.13f1, 2023.1.20f1, 2023.2.0b18, 2023.3.0a14
Not reproducible with: 2021.3.32f1, 2022.2.0a10
Reproducible on: Windows 10 Pro (22H2)
Not reproducible on: No other environment tested
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