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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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