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
- Crash on ProfilerSymbolsDelayedDeletion::AddCloneObject when deserializing an object-instantiate marker with a dangling/corrupt name string
- Characters overlap preceding text when monospace tags are used on a TMP_Text component set to RTL
- Wrong range is displayed in a 'resolutionPerPatch is clamped to the range of' warning
- Debug mode fails to build in Visual Studio when .csproj file is generated for Built-in packages
- "Too many sprite tiles on Image" error is spammed in the Console when editing Pixels Per Unit Multiplier on a Tiled Image Type for Scroll View
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.