Search Issue Tracker
By Design
Votes
2
Found in [Package]
7.1.2 release
Issue ID
1188029
Regression
No
Keywords _ADDITIONAL_LIGHT_SHADOWS and _SHADOWS_SOFT get turned off in build even if they're on in edit and play mode
Repro steps:
1. Download example project
2. Open Samplescene
3. Press play and take a look at what the scene looks like
4. Build the project
5. Look at what the scene looks like in the build
Expected result: the scene should look the same
Actual result: the main light is no longer soft, the spotlight no longer has a shadow, and the colors, representing both the _ADDITIONAL_LIGHT_SHADOWS and _SHADOWS_SOFT keywords, are changed. Take a look at CustomLightingShadows.shadergraph to see how this is set up.
Note: if _MAIN_LIGHT_SHADOWS keyword bug is fixed so that the shadergraph will compile once it is added, there is a high probability that that keyword will suffer the same problem.
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
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
- EnterPlayModeOptions doesn't take effect if user manually modifies m_EnterPlayModeOptionsEnabled to 0
Resolution Note:
This is by design as we strip all variants that have _ADDITIONAL_LIGHT_SHADOWS, but not _ADDITIONAL_LIGHTS. Simply add an _ADDITIONAL_LIGHTS keyword (global and multi-compile) into your shadergraph shader. This fixes _SHADOWS_SOFT as well.