Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.1.X, 2022.3.X
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)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment