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
- Previous model to world matrix is not correctly set for ASW
- More calls are made to GC.Alloc in an HDRP Sample Template when compared to the 2022.3 stream
- Generating Light Probe lighting returns inconsistent results on a specific mesh
- Two Warnings appear for every Soft Delete Operation when Deleting Sub Assets in the Project Browser
- “Item m_LightProbeSystem not found” warning is thrown when pressing the “Open” button multiple times in the Adaptive Probe Volume component warning
Add comment