Search Issue Tracker
Fixed in 2020.2.X
Won't Fix in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3
2019.3.9f1
2020.1
2020.2
Issue ID
1248272
Regression
Yes
[AssetPipelineV2] Reimporting all assets breaks material previews if the Scene, in which the materials are used, is reloaded
How to reproduce:
1. Open user-submitted project(ImportPP.zip)
2. Open the test scene
3. Select all Assets via CTRL+A/CMD+A and select 'Reimport'
4. See the Material previews
Expected result: Material previews are displayed correctly
Actual result: Material previews are broken and display in pink
Reproducible with: 2019.2.0a5, 2019.3.13f1, 2020.1.0b9, 2020.2.0a12
Could not test with: 2017.4.40f1, 2018.4.23f1(ADBV2 not yet implemented)
Notes:
Could not reproduce with Asset Pipeline V1
Reimporting Materials one by one or without having the prompt to reload the Scene does not break previews
Creating a new Scene and reimporting all assets from there does not cause the broken previews
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
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a18
Resolution Note (2020.1.X):
The original issue was fixed for Unity 2020.2 by the feature which ensured Asset Preview Generation was done by a worker process (i.e. not on the main Editor).
It would not be trivial to backport that feature, and attempts to fix this specific issue have resulted in other regressions being introduced into the codebase.
As such, we recommend that users upgrade to Unity 2020.2 depending on the importance of this bug to their workflow.
Resolution Note (2019.4.X):
The original issue was fixed for Unity 2020.2 by the feature which ensured Asset Preview Generation was done by a worker process (i.e. not on the main Editor).
It would not be trivial to backport that feature, and attempts to fix this specific issue have resulted in other regressions being introduced into the codebase.
As such, we recommend that users upgrade to Unity 2020.2 depending on the importance of this bug to their workflow.