Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a1
2019.3.0a3
Issue ID
1167616
Regression
Yes
"Reimport All" is broken in 2019.3 (in Asset Pipeline v2)
Reimport All" option of Context menu in Project View is broken in 2019.3 (in Asset Pipeline v2). Reproduced in 2019.3.0a3
How we can reproduce it:
- you need any "big" project (100-200 Mb) for testing it
Correct behavior:
1 when I open project in e.g. 2019.2.0b5 it imports my project for around 2 minutes, then in Project View I select "Reimport All" from Context menu and it reopens Unity Editor and imports project for the same (or almost the same) 2 minutes
Incorrect behavior:
2 when I open project in e.g. 2019.3.0a3(or any oher 2019.3 build up to a9 - latest for today) it imports my project for around 2 minutes, BUT then in Project View I select "Reimport All" from Context menu and it reopens Unity Editor and imports project for less than a minute
Actual results: 2019.3 uses Asset Pipeline v2 by default and "Reimport All" feature is broken there. That is regression!
Expected results: there are many changes in Asset Pipeline v2 and we need to decide if we need "Reimport All" feature at all. My opinion is that we still need to have it and so we need to fix it.
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
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
Resolution Note (fix version 2019.3):
Verified fixed in 2019.3.0a12