Search Issue Tracker
Fixed in 2018.1.X
Votes
2
Found in
5.6.0a6
Issue ID
856398
Regression
Yes
Modifying texture import settings from script changes 'timeCreated' in the meta-file, even when no changes are made
We have an active problem with importers modifying 'timeCreated' timestamp in asset meta files when called from script, see case 856344. It seems though that the Texture Importer rewrite made the problem even worse for textures alone - the timestamp gets updated even if no actual changes are made to the texture. This is a regression from 5.4.
Repro: The parent case contains menu item scripts to quickly see the behaviour in the editor.
Comments (1)
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
ForceMagic
Dec 18, 2017 14:22
Duplicates of : https://issuetracker.unity3d.com/issues/modifying-texture-import-settings-from-script-changes-timecreated-in-the-meta-file-even-when-no-changes-are-made