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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #1126940