Search Issue Tracker
Fixed
Fixed in 2021.3.29f1, 2022.3.6f1, 2023.1.5f1, 2023.2.0a16
Votes
3
Found in
2019.4.33f1
2020.3.24f1
2021.2.5f1
2022.1.0b1
2023.1.0a24
2023.2.0a1
Issue ID
UUM-3774
Regression
No
[URP] "RenderTexture.Create failed" thrown with Linear Color Space, DisplayP3 Gamut, Post Processing enabled, HDR disabled
How to reproduce:
1. Open the attached project ("PP Bug Report.zip")
2. Build And Run on an iOS device
Expected result: The Scene is rendered as expected
Actual result: A gray screen is shown, "RenderTexture.Create failed: color format is set to a depth/stencil format - D24 UNorm (91)" error thrown
Reproducible with: 7.3.1, 7.7.1 (2019.4.33f1), 10.7.0 (2020.3.24f1), 12.1.2 (2021.2.5f1), 13.1.3 (2022.1.0b1)
Reproducible on:
iPhone 8 Plus (iOS 14.4.2)
iPhone 13 mini (iOS 15)
Not reproducible on:
Huawei - (ELS-NX9), Android 10, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00264, Samsung Galaxy S10+ (SM-G975F), Android 10, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00078, Motorola Nexus 6 (Nexus 6), Android 7.1.1, CPU: Snapdragon 805 APQ8084AB, GPU: Adreno (TM) 420
Note:
- On macOS, only reproducible when running builds on Apple Silicon
Workarounds:
- Disabling post-processing in the camera properties
- Removing P3 from the list of color gamuts or making sRGB the highest-priority
- Changing from Linear to Gamma Color Space
- Enabling HDR in the Render Pipeline Asset Quality settings
Comments (1)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
zauberzaubar
Jan 05, 2022 20:04
Same issue here and can confirm switching to Gamma space is a workaround.
We don't have HDR or Post-processing enabled though, so those don't seem to be workarounds.