Search Issue Tracker

By Design

Votes

0

Found in

2022.3.63f1

6000.0.51f1

6000.1.7f1

6000.2.0b5

6000.3.0a1

Issue ID

UUM-110443

Regression

No

Rendering Path Forward/Forward+ causes Lighting to not affect SpriteRenderer

-

How to reproduce:

1) Open project “IN-105168”
2) Find the "Environment/Ground" GameObject in the Hierarchy
3) Notice how the ground is darkened in Game view
4) Move the camera around and zoom out
5) Notice how lighting now affects the ground in the Game view

Expected result: The GameObject with SpriteRenderer is not lit (See internal notes)
Actual result: The GameObject with SpriteRenderer is lit (See internal notes)

Reproducible with: 2022.3.63f1, 6000.0.51f1, 6000.1.7f1, 6000.2.0b5, 6000.3.0a1
Could not test with: 2021.3.52f1 (All objects in the scene are rendered pink)

Reproducible on: Windows 11 Enterprise
Not reproducible on: No other environments tested

Workaround:
- Use “Deferred” Rendering Path
- Limit the number of Light components in a scene

Notes:
- The issue seems to depend on the number of Light components
- The issue seems consistently present with more than 3 Light components enabled
- Disabling the Light components located in each “ToonFireTorchIntenseRed (2)” until there is less than 3 of them resolves the issue

  1. Resolution Note:

    The issue seems to stem from "Per Object Limit" in the URP Asset config being configured to an unideal number. Increasing it resolves the issue

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.