Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.3.1f1
2020.1
Issue ID
1222368
Regression
No
[UIR] Importing Built-in shaders breaks PackageManager GUI rendering when using RP
Steps to reproduce:
1. Open a new project with any RP installed
2. Import user-supplied built-in shaders
3. Open Package Manager
Expected: GUI is rendered
Actual: GUI is not rendered
Reproduced in: 2019.3.3f1, 2020.1.0a25
Not reproduced in: 2019.2.21f1 (no URP), 2018.4( no URP)
Note: no repro with LWRP
URP versions: 7.1.8, 7.2.0
HDRP versions: 7.2.0
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
- 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
Resolution Note (2020.2.X):
The version of the built-in shaders must correspond to the version of Unity in use. In this case, the built-in shaders of 2019.2.10f1 are being imported in a project opened with 2019.3.1f1. This is not supported nor recommended. This causes UIToolkit to use an older incompatible version of Internal-UIRAtlasBlitCopy.shader. Deleting the shader from the Assets directory works around this specific issue, but there may be other lingering issues.