Search Issue Tracker
Fixed in 2022.3.5f1
Fixed in 2022.2.X, 2022.3.X
Votes
0
Found in
2022.2.16f1
Issue ID
UUM-33863
Regression
Yes
App startup fails with the error "Texture creation failed. 'R32_SFloat' is not supported" when building for WebGL 1.0
How to reproduce:
1. Open the user-attached project “Texture creation failed (WebGL1)”
2. Click Build And Run
3. Observe the built app
Expected result: The app is launched
Actual result: The app is not launched and there is a "Texture creation failed. 'R32_SFloat' is not supported" error in the browser Console
Reproducible with: 2022.2.0a1, 2022.2.16f1
Not reproducible with: 2020.3.47f1, 2021.3.23f1, 2022.1.0a16
Couldn’t test with: 2023.1.0b13, 2023.2.0a11 (There is no WebGL 1.0 support)
Reproducible on: Windows 11 Pro with Google Chrome
Note: The bug is reproducible in the newly created projects
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment