Search Issue Tracker
By Design
Votes
1
Found in [Package]
10.1.0
Issue ID
1324554
Regression
No
Emission Shader variants are not included in Build when it's referenced in Preloaded Shaders
How to reproduce:
1. Open the user's attached "To Delete.zip" project
2. Open the "SampleScene" Scene
3. Go to File -> Build And Run
4. Observe the text on the left in the Player
Expected result: Emission Shader variant is included in the Build (Text on the left is emissive)
Actual result: Emission Shader variant is not included in the Build (Text on the left is not emissive)
Reproducible with: 10.1.0 (2020.2.0b8), 10.4.0 (2020.3.2f1), 11.0.0 (2021.1.0f1), 12.0.0 (2021.2.0a11)
Not reproducible with: 7.5.3 (2019.4.23f1), 8.3.1 (2020.1.17f1), 10.0.0-preview.26 (2020.2.0b8)
Note:
- In 10.0.0-preview.26 the Shader is not visible in Play Mode at all
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
The shader inspector shows that there is a name collision for the keyword _EMISSION. Is also says the keyword will be treated as local.
Shader.EnableKeyword does not affect local keywords.