Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.4.X, 2019.1.X
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.1.0b10
2019.2.0a1
Issue ID
1146482
Regression
No
AssetPostprocessor::GetVersion does not affect AssetDependencyHash on first import
How to reproduce:
1. Make sure Library folder is deleted
2. Open attached project "TestHashProject2019.1.0b10.zip"
3. In the Console window, observe the hash logs of MyModel.fbx
4. In the Project window, reimport MyModel.fbx
5. In the Console window, observe the hash log of MyModel.fbx
Expected result: the dependency hash does not change
Actual result: the dependency hash is changed
Reproducible with: 2017.4.26f1, 2018.3.14f1, 2019.1.0f2, 2019.2.0a8
Not reproducible with: 2019.2.0a9, 2019.2.0a12, 2019.3.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Add comment