Search Issue Tracker
By Design
By Design in 2023.2.X
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
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".
Resolution Note (2023.2.X):
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".