Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2019.4
2019.4.1f1
2020.1
2020.2
Issue ID
1260054
Regression
No
Sub-Assets of a 3D model are displayed in the Project window when they are deleted via the OnPostprocessModel() method
How to reproduce:
1. Open the attached "1260054 repro" project
2. Open the "FBXCleaner.cs" Script from the Assets > Editor folder
3. Uncomment code from line 30 to line 42 inside the "FBXCleaner.cs"
4. Select the "claw_hand3.fbx" Asset from the Assets folder
5. Right-click it and select Reimport
Expected results: the Project window content is refreshed and updated
Actual results: the Project window doesn't update and shows the deleted Assets
Reproducible with: 2019.4.3f1 (Asset Import Pipeline V2), 2020.1.0b14, 2020.2.0a4
Not reproducible with: 2019.4.3f1 (Asset Import PipelineV1), 2020.2.0a5, 2020.2.0a16
Could not test with: 2018.4.24f1 (Asset Import Pipeline V2 isn't available)
Notes:
-This issue also reproduces with .obj and .dae file formats
-This issue doesn't reproduce with Asset Import Pipeline V1
-Triggering a Domain Reload, restarting the Editor or selecting Reimport All solves the issue
-The issue doesn't reproduce if the Script is fully uncommented when opening the project or importing a new model, it seems to only reproduce when the model is already present in the project at the time of introducing the post-processing
-
Excelscience
Jul 10, 2020 15:53
http://images.google.co.jp/url?q=https://sporthrs.com
http://maps.google.co.jp/url?q=https://sporthrs.com
https://www.google.co.jp/url?q=https://sporthrs.com
http://images.google.es/url?q=https://sporthrs.com
http://maps.google.es/url?q=https://sporthrs.com
https://www.google.es/url?q=https://sporthrs.com
http://images.google.ca/url?q=https://sporthrs.com
http://maps.google.ca/url?q=https://sporthrs.com
https://www.google.ca/url?q=https://sporthrs.com
http://images.google.at/url?q=https://sporthrs.com
http://maps.google.at/url?q=https://sporthrs.com
https://www.google.at/url?q=https://sporthrs.com
http://images.google.dk/url?q=https://sporthrs.com
http://maps.google.dk/url?q=https://sporthrs.com
https://www.google.dk/url?q=https://sporthrs.com
http://images.google.pt/url?q=https://sporthrs.com
http://maps.google.pt/url?q=https://sporthrs.com
https://www.google.pt/url?q=https://sporthrs.com
http://images.google.no/url?q=https://sporthrs.com
http://maps.google.no/url?q=https://sporthrs.com
https://www.google.no/url?q=https://sporthrs.com
http://images.google.com.ph/url?q=https://sporthrs.com
http://maps.google.com.ph/url?q=https://sporthrs.com
https://www.google.com.ph/url?q=https://sporthrs.com
http://images.google.iv/url?q=https://sporthrs.com
http://maps.google.iv/url?q=https://sporthrs.com
https://www.google.iv/url?q=https://sporthrs.com
http://images.google.gr/url?q=https://sporthrs.com
http://maps.google.gr/url?q=https://sporthrs.com
https://www.google.gr/url?q=https://sporthrs.com
http://images.google.ch/url?q=https://sporthrs.com
http://maps.google.ch/url?q=https://sporthrs.com
https://www.google.ch/url?q=https://sporthrs.com
http://images.google.be/url?q=https://sporthrs.com
http://maps.google.be/url?q=https://sporthrs.com
https://www.google.be/url?q=https://sporthrs.com
http://images.google.cl/url?q=https://sporthrs.com
http://maps.google.cl/url?q=https://sporthrs.com
https://www.google.cl/url?q=https://sporthrs.com
http://images.google.bg/url?q=https://sporthrs.com
http://maps.google.bg/url?q=https://sporthrs.com
https://www.google.bg/url?q=https://sporthrs.com -
june1004
Jul 04, 2020 22:05
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
- UI Toolkit 'background-size' property is not fully animatable
- Moving the Scrollbar via clicking no longer works after the first-click when page size is too small
- Elements in UI Builder Viewport are displayed incorrectly when Editor UI Scaling is set to 125%
- Prefab referencing a script is not shown in the Search window's Project tab when using "Find References In Project"
- Scroll view sensitivity remains unchanged when modifying the "--unity-metrics-single_line-height" value
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a5