Search Issue Tracker
Fixed in 10.1.0-preview.12
Fixed in 7.5.2, 8.3.1
Votes
0
Found in [Package]
7.4.1
Issue ID
1263514
Regression
Yes
[URP] All Pixel lighting variants are stripped in build if at least one URP asset has Additional Lights set to Per Vertex
How to reproduce:
1. Open the project from the attached file "1263514.zip"
2. Open the UniversalRP-MediumQuality asset and set Additional Lights to Per Vertex
3. Open the UniversalRP-HighQuality asset and set the Additional Lights to Per Pixel
4. Go to File > Build And Run
Expected result: The light is rendered
Actual result: The light is not rendered
Reproducible with: 7.4.1(2019.4.7f1), 7.4.3(2019.4.7f1), 8.2.0(2020.1.2f1, 2020.2.0a20), 10.0.0-preview.26(2020.2.0a20)
Not reproducible with: 4.10.0-preview(2018.4.26f1), 7.3.1(2019.4.7f1), 8.1.0(2020.1.0b16, 2020.2.0a20)
Notes:
- In the Player.log of the build the _ADDITIONAL_LIGHTS keyword does not exist
- The quality is set to High
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 (fix version 10.1.0-preview.12):
Fixed in Universal Render Pipeline 10.2.0 (Verified in 2020.2.0b12.3574)
Resolution Note (fix version 7.5.2):
Fixed in Universal Render Pipeline 7.5.3 (verified in 2019.4.19f1 (ca5b14067cec))