Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
2019.3.0b1
2019.3.14f1
2019.4
2020.1
2020.2
Issue ID
1251168
Regression
Yes
[URP] Imported model objects don't have the correct shader set during the initial launch of the project
How to reproduce:
1. Open the attached project named "Case_1251168"
2. Select the "africanAmerican_f_01.glb" object in the Project window
3. Observe the Preview window of the model
Expected result: Model has the correct shader set on the first project launch
Actual result: Model does not have the correct shader set
Reproducible with: 2019.3.0b1(7.0.1), 2019.4.0f1(7.4.1), 2020.1.0b13(8.1.0), 2020.2.0a15(9.0.0-preview.14)
Not reproducible with: 2018.4.23f1(4.10.0), 2019.3.0a11(7.0.1)
Workaround: Re-importing the object fixes the issue, however, this must be done every time Library is deleted
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
- The Player hangs when activating another maximized application
- [XR] Input is not registered and headset view is headlocked after entering Play Mode with Meta XR SDK on 6000.0.0b16 and higher
- Crash on RtlLookupFunctionEntry when using 10 or more GameObjects with Articulation Body component in the scene
- Polygons are created on the opposite side of the Sprite when the Sprite boundaries are above the edge of the Texture
- Render Graph Viewer Resource list becomes shrunk after using a filter that yields no results
This is a duplicate of issue #1126940