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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.