Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
Issue ID
1253968
Regression
No
[Shaders][LiveLink] When a variant has an error, nothing is rendered in the player
STR:
1. Create a new project
2. Create a shader that uses shader_feature functionality.
3. Make a compilation error in the shader for a non-default variant of shader_feature
4. Assign this shader to a material, use the material on a cube in an empty scene
5. Make a custom build using C# and make sure to use BuildOptions.ShaderLivelinkSupport (https://docs.unity3d.com/2020.2/Documentation/ScriptReference/BuildOptions.ShaderLivelinkSupport.html)
6. Add a script to switch to a shader_feature with a shader that produces an error
7. Run the player
Expected: when switching to a variant that has compilation errors at runtime, error shader is used
Actual: nothing is rendered
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
- [macOS] There is no way to tell if you are running under Rosetta
- [AssetImport] Changing Graphics APIs in Android platform reimports most of the assets (textures, fonts, ...)
- Stack frames are missing from Console window when in Full Stack trace mode
- An error is returned and no package is listed if an invalid package is hosted on a scoped registry
- Crash with ComputeTileMeshJob when generating Navmesh
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a17