Search Issue Tracker
Duplicate
Votes
0
Found in
2019.2
2019.3
2019.3.0b6
2020.1
Issue ID
1194180
Regression
Yes
Project's Asset folder "Refresh" is much slower on Asset Pipeline Mode "Version 2" than "Version 1"
How to reproduce:
1. Open attached project "ADBV2SlowRefresh.zip"
2. Edit -> Project Settings -> Editor -> "Asset Pipeline Mode" -> "Version 2"
3. In Hierarchy window, right-click on Assets folder -> Refresh (observe the times it takes for the assets to refresh)
4. Edit -> Project Settings -> Editor -> "Asset Pipeline Mode" -> "Version 1"
5. Restart the Editor and the project
6. In Hierarchy window, right-click on Assets folder -> Refresh (observe the times it takes for the assets to refresh)
6. Compare the time it takes to refresh the assets (for more details you can check Editor.log)
Expected result: the time it takes for the assets to refresh on "Version 2" is similar or faster than "Version 1"
Actual result: "Version 2" is ~2 times slower
Reproducible with: 2019.2.10f1, 2019.3.0b9, 2020.1.0a11
Could not test with: 2017.4, 2018.4 due to Asset Pipeline V2 was not yet introduced
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
This is a duplicate of issue #1171344