Search Issue Tracker
Fixed in 2018.2.X
Won't Fix in 2018.1.X
Votes
0
Found in
2018.1.0a1
2018.1.0b2
Issue ID
992989
Regression
Yes
Using 'Forward Add' shadow rendering mode produces irrelevant syntax error
How to reproduce:
1. Open Unity
2. Create a new project
3. Import tester-submitted shader (Test.shader)
4. Inspect shader syntax error pointing at line 102 (unexpected ';')
5. Switch to alternative shadow rendering mode at line 74
6. Notice shader syntax error disappear at line 102
Expected result: Unity compiles both shadow rendering modes correctly.
Actual result: Unity does not compile 'Forward Add' shadow rendering mode and complains about syntax errors
Reproducible with - 2018.1.0a1, 2018.1.0b6
Not reproducible with - 5.6.5p1, 2017.1.3p1, 2017.2.1p3, 2017.3.1p1
Verified in: 2018.2.0a5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- When a Rigidbody2D is inactive GetPoint/GetVector/GetRelativePoint/GetRelativeVector fallbacks to returning (0, 0)
- Light brightness gets intense until the 'Lightmap Encoding' quality is changed when baking Lightmap
- Crash on LinearCollectionField::LinearCollectionField after a 'm_ArrayField != SCRIPTING_NULL' assertion when opening a project
- Import Activity Window takes long time to open
- Child Canvas' Sorting Layer is changed to the same value as the parent Canvas after interacting with Dropdown UI object
Add comment