Search Issue Tracker
Fixed
Fixed in 2023.3.0a12
Votes
0
Found in
2023.3.0a11
Issue ID
UUM-56884
Regression
Yes
Crash on ShaderLab::FloatVal::ToFloat when switching Scene view shading mode to wireframe
Reproduction steps:
1. Create a new 3D project
2. Add a Sphere in the Hierarchy window (Right-click > 3D Object > Sphere)
3. Set Scene view Shading mode to Shaded Wireframe in the Scene view View Options toolbar
Expected result: Scene view shading mode is set to Wireframe
Actual result: Editor crashes
Reproducible with: 2023.3.0a11
Not reproducible with: 2021.3.32f1, 2022.3.14f1, 2023.2.2f1, 2023.3.0a10
Fixed in: 2023.3.0a12
Reproducible on: Windows 10
Not reproducible on: No other environment tested
First few lines of stack trace:
{noformat}0x00007FFB5A87A7E4 (Unity) ShaderLab::FloatVal::ToFloat
0x00007FFB5A876802 (Unity) ShaderLab::ShaderState::ApplyShaderState
0x00007FFB5A866A27 (Unity) ShaderLab::Pass::ApplyPass
0x00007FFB5A7C3831 (Unity) ApplyMaterialPass
0x00007FFB5A4CCE17 (Unity) BatchRenderer::ApplyShaderPass{noformat}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- [Linux] AutoLocale log is logged when opening a project
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Add comment