Search Issue Tracker
Fixed in Fixed on the Editor side
Votes
0
Found in [Package]
7.0.0 - 7.4.1
Issue ID
1262921
Regression
No
SRP Batcher compatibility randomly changes after shader is reimported
How to reproduce:
1. Open the attached project
2. Select the "MicroSplat" shader in the MicorSplatData folder and observe that it is SRP batcher compatible in the Inspector window
3. Reimport the shader. You may need several re-imports to trigger the issue
Expected result: Shader retains its SRP batcher compatibility status no matter how many times it is reimported
Actual result: Shader becomes changes its SRP batcher compatibility status randomly
Reproducible with: 2019.4.6f1(7.0.0, 7.4.1), 2020.1.0a13(7.1.8)
Not reproducible with: 2020.1.0a14(7.1.8), 2020.1.1f1(8.2.0), 2020.2.0a20(9.0.0-preview.35)
Could not test with: 2018.4.26f1(URP was not yet available)
Notes:
1. Tested with URP only
2. When reimporting both MicroSplat and MicroSplat1 shaders sometimes shaders randomly become compatible again
3. Issue re-occurs once the Library is cleared
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
Resolution Note (fix version Fixed on the Editor side):
Fixed in - 2020.1.0a14
Resolution Note:
Fixed in - 2019.4.16f1