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
- Console shows Exception: {"error":"not found","detail":["not found"]} after opening Build History window
- [HDRP] Volumetric cloud shadows disappear when there is no directional light shadows
- “Selector” column names in the Search window are lowercase when added
- Install List Project Counter Panel can be right clicked through and Install Context Menu can be opened disabling Project Counter Panel's buttons
- [MacOS] Scene is marked/flickering as dirty (with asterisk) when dragging a Material on a GameObject in Scene view
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