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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
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.