Search Issue Tracker
Won't Fix
Votes
2
Found in
2021.3.14f1
2022.1.23f1
2022.2.0f1
2023.1.0a20
Issue ID
UUM-22523
Regression
No
A built-in sprite material that is incompatible with URP 2D lights is created for Standalone Player when adding a SpriteRenderer to a GameObject
Reproduction steps:
1. Open the project “SpriteRendererBug”
2. Open the Scene “SampleScene”
3. Enter Play Mode
4. Observe GameObjects through Game view and pay attention to the left upper corner where it says “Sprite-Lit-Default”
5. Exit Play mode
6. Build the project
Expected result: In both Play Mode and Standalone Player a default material for the GameObject is used (Sprite-Lit-Default)
Actual result: The default material (Sprite-Lit-Default) for the GameObject is only used in Play Mode, while for Standalone Player - built-in sprite material is used as a default material, which is incompatible with URP 2D Lights
Reproducible with: 2021.3.14f1, 2022.1.23f1, 2022.2.0f1, 2023.1.0a20
Couldn’t test with: 2020.3.42f1 (due to compiler errors)
Reproducible on: macOS Catalina 10.15.7 (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
- Source Generation with GeneratePropertyBag fails when using reserved keywords as variable names with @ prefix
- Prismatic ArticulationBody moves in opposite direction when using targetVelocity
- Shader Graph skybox material is rendered inccorrectly in builds when "Allow Material Override" or "Cast Shadows" are enabled and the "Deferred" Rendering Path is used
- Object motion is affected by incorrectly added rotation motion when importing animations
- Base class's Context Menu method is called when calling it in the Editor from the child class and the child class overrides this method
Resolution Note:
Will fix when Built-in RP is fully deprecated and removed as part of unification efforts. To work around this, you can create a prefab with the correct lit materials, and instantiate it during runtime.