Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
2
Found in
2021.3.12f1
2022.1.21f1
2022.2.0b13
2023.1.0a16
2023.2.0a1
Issue ID
UUM-17757
Regression
No
[URP] GameObjects become unlit when Rendering Path is set to Forward and or Forward+
How to reproduce:
1. Open the user-attached project
2. Open the “TestLevelMorgan” Scene
3. Select “UniversalRenderer” settings, via the Project window Search Bar
4. Change the Rendering Path setting to “Forward”
5. Note the Lighting on Pipes in front of the “MainCharacter” GameObject
6. Switch to Forward+ rendering
7. Note the Lighting on Pipes in front of the “MainCharacter” GameObject
Expected result: Lighting is consistent and GameObject is always lit regardless of the Rendering Path
Actual result: Rendering Path - “Forward+” and “Forward” causes Lighting to disappear and GameObjects to become unlit
Reproducible with: 12.1.7 (2021.3.12f1), 13.1.8 (2022.1.21f1), 14.0.3 (2022.2.0b13), 15.0.1 (2023.1.0a16)
Couldn’t test with: 10.10.1 (2020.3.41f1) - Pink Shaders
Reproducible on: macOS Monterey 12.6 (Intel)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This issue seems to be related to better lit not supporting Forward+ light data which are different from deferred and forward.
Resolution Note (2023.2.X):
This issue seems to be related to better lit not supporting Forward+ light data which are different from deferred and forward.