Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
3
Found in
2019.3.16f1
2019.4.1f1
2020.1.0b10
2020.2.0a12
Issue ID
1259778
Regression
Yes
Crash on ShaderLab::IntShader::CreateLocalKeywordRemap when loading custom shaders on standalone build
Reproduction steps:
1. Download and open the user-submitted project
2. Build and run for Windows
-- Observe the crash
Reproducible with: 2019.3.16f1, 2019.4.3f1, 2020.1.0b10, 2020.1.0b14, 2020.2.0a12, 2020.2.0a17
Not reproducible with: 2018.4.24f1, 2019.3.15f1, 2020.1.0b9, 2020.2.0a11
Notes:
The issue is caused by DebugAlbedo.shader which is added to the "Always complied shader" list.
Comments (2)
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
- 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
Alina80
Feb 10, 2024 16:45
Experiencing issues with ShaderLab? Ensure your custom shaders are compatible with the standalone build environment. Debug by reviewing syntax, compatibility, and any potential conflicts. Engage with the shader development community for insights. Precision in coding and collaboration often unveils solutions to intricate issues.