Search Issue Tracker
By Design
Votes
2
Found in
2020.2
2021.1.0a9
Issue ID
1298014
Regression
No
"Importer(TextScriptImporter) generated inconsistent result" on importing text file with the same timestamp, same length
"Importer(TextScriptImporter) generated inconsistent result" warning appears when importing new text file with the same timestamp, same length, but different content
How can we reproduce it using the example you attached
1 Open attached project
2 Go to main menu->BUG->MakeIndeterministicImport
Actual results: the warning appears in Console: "Importer(TextScriptImporter) generated inconsistent result for asset(guid:f2a18a74460c64e4d8e7b2fbbe06096d) "Assets/X.txt""
Expected results: importing a new text file with the same timestamp, same length, but different content should be identified as a new file (currently AssetPipeline treats it as the same file )
Reproduces on: 2020.2.0f1, 2021.1.0a9
Not reproduces on: 2020.1.6f1, 2019.4.14f1 - might be that consistency check is not present in these versions
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
This problem occurs because file timestamp on the asset is being manipulated. This is not supported. The asset database relies on the asset file timestamps updating when modified. If asset file is updated on a operation system with a low file timestamp resolution, we have protection from this and support multiple file changes to the same asset during current file timestamp tick.