Search Issue Tracker
By Design
Votes
0
Found in
2021.3.18f1
2022.2.8f1
2023.1.0b5
2023.2.0a4
Issue ID
UUM-28713
Regression
Yes
Render Texture Depth Stencil Format displays enum values instead of human readable values
Reproduction steps:
1. Open the attached project “IN-31025”
2. Select “New Render Texture” in the Project window
Expected result: The Depth Stencil Format is “At least 24 bits depth (with stencil)”
Actual result: The Depth Stencil Format is “D32_SFLOAT_S8_UINT”
Reproducible with: 2021.2.0a19, 2021.3.18f1
Not reproducible with: 2021.2.0a18, 2020.3.45f1
Reproducible on: macOS 12.4 (Intel), Windows 10 (user’s)
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
- Progress indicator in Meta Quest Build Profile configuration is barely visible
- Slightly transparent objects disappear completely in Web Player when using RenderGraph
- Visual Scripting Components are hidden behind a throbber when Multiplayer Play Mode is running with at least one local instance
- Video Player does not throw an error when playing a video with unsupported encoding settings
- Errors indicating that TMP Extras were not Imported logged when opening the Render Pipeline Converter Window while in Play Mode
Resolution Note:
This is in fact not a regression, but "As Designed".
The affected versions received upgrades related to depth-stencil in RenderTextures. The "At least XYZ bits of depth" messaging is not always accurate for those anymore because the "At least" portion is wrapped into the "Enable Compatible Format" checkbox.
For example, if I use "D24_UNORM" + enable "Enable Compatible Format", then we are indeed talking about "At least 24 bits of depth, no stencil". When "Enable Compatible Format" is disabled, then the human reading is: "Exactly 24 bits of depth, no stencil".
For consistency, the naming scheme now matches the scheme used for the color formats as well. However: we are considering revisiting this in the future by offering more easily readable values somewhere next to the precise format name, as the latter can be used to look up information in the API docs while the former would help with readability "on the spot".