Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2019.4
2019.4.0f1
2020.2
Issue ID
1259980
Regression
No
Shader error undeclared identifier "UNITY_TRANSFER_LIGHTING" when building project for the first time after project launch
To reproduce:
1. Open user's attached project
2. Build the project (File -> Build And Run)
Expected result: Project builds successfully
Actual result: Project fails to build with an undeclared identifier "UNITY_TRANSFER_LIGHTING" error
Reproduced in: 2019.4.0f1, 2019.4.2f1, 2020.1.0b14, 2020.2.0a10
Not reproducible with: 2020.2.0a11, 2020.2.0a16
Could not test with: 2018.4.23f1 (console errors after downgrading)
Notes:
-Second consecutive build is always successful (apart 2019.4.0f1 & 2019.4.1f1 in which results seemed to be unstable, sometimes it would build after the second iteration, and other times, it would not)
-If it doesn't reproduce in the same manner, delete the folder "Library"
-Main error message: Error building Player: Shader error in 'Nature Shaders/Tree Billboard': undeclared identifier 'UNITY_TRANSFER_LIGHTING' at line 139 (on d3d11)
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
- Tilemap Tiles do not get lit up unless the Light Range is greater than the distance between the position of the Tile before the transformation and the Light Source when the Tile is transformed with Tilemap.SetTransformMatrix method
- The Editor and "Reloading Domain" windows are frozen when entering Play Mode
- Crash when attempting to create a custom FMOD DSP unit
- [Linux] Floating windows do not keep their size after restarting the Editor
- .framework plugin is mistakenly treated as a directory when building for Universal Windows Platform
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a11. In 2020.1 you can fix this by manually enabling the Caching Preprocessor