Search Issue Tracker
Fixed
Won't Fix in 2020.3.X
Fixed in 2021.3.24f1
Votes
0
Found in
2020.3.43f1
2021.3.17f1
Issue ID
UUM-25336
Regression
No
Error "RenderTexture.Create failed: 3D textures with depth are not supported" is thrown when changing texture dimension from 2D to 3D
How to reproduce:
1. Create a new project
2. In the “Project” window right-click → “Create” → “Render Texture”
3. Select a newly created texture
4. Change “Dimension” to “3D” in the Inspector window
Expected result: no error in the Console
Actual result: “RenderTexture.Create failed: 3D textures with depth are not supported” error thrown in the Console
Reproducible with: 2020.3.43f1, 2021.3.17f1, 2022.1.0a12
Not reproducible with: 2022.2.4f1, 2023.1.0b1
Fixed in: 2022.1.0a13
Reproducible on: Windows 10 Pro
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (2020.3.X):
2020.3 is reaching end-of-life very soon. The backport for this bug is not straight-forward and most likely won't make the deadline anymore.