Asset Import Bug

anonymous_user_fff38ccc · February 26, 2015, 4:21pm

I have run into an issue where that when you replace an asset (fbx for my test), sometimes Unreal does not detect it was changed until the next start-up of the project. The few times I did this, the project would also re-import the asset again every time the project was opened. I was able to solve this by deleting the asset while the engine was closed, re-opening the project so Unreal knew it was gone and then re-importing the asset once again.

Repro (Fresh project, default settings, official UE v4.7.0):

placed fbx in a folder inside the content folder
opened the project so unreal would detect it
replaced the fbx with a newer one, unreal re-imported the asset
once the re-import finished, replaced the fbx again, this time with the original fbx, unreal did not detect the change
closed and reopened unreal, asset was re-imported
repeated step 5 over and over, same result
closed unreal, deleted the fbx
re-opened unreal, ignored all errors about the asset being gone, closed unreal without saving
re-added the original fbx and opened unreal, asset was reimported
closed unreal and re-opened, no re-import, everything is fine now
Was also able to reproduce the same issue using a 4096 tga file as well

This can be very annoying if your fbx was importing large textures along with it (4096 for example). I doubt this was intentional but if it is, why was it done this way?

anonymous_user_fff38ccc · February 26, 2015, 6:23pm

this sometimes happens on first import of asset as well

Tim_Hobson · February 26, 2015, 9:19pm

I’ll be investigating this one very soon. I cleaned up the list above to make it easier to read since it clumped all together. Thanks for reporting this.

anonymous_user_fff38ccc · February 27, 2015, 7:39pm

If you need anymore information or a file I was able to replicate with, let me know

Tim_Hobson · March 4, 2015, 4:32pm

Hey eviltenchi,

I’ve been able to reproduce this and have submitted ticket UE-11291 for the issue. This is still a new feature that is being actively developed. There are certainly improvements that are coming to make this work more smoothly. Once a fix has been submitted I’ll update the post here.

Thank you!

Tim

anonymous_user_fff38ccc · April 24, 2015, 3:10pm

Will this be fixed anytime soon? This bug is very annoying and wastes a lot of time to do the workaround.

Tim_Hobson · April 24, 2015, 4:31pm

This should be resolved in 4.8 once that releases. There is new enabled option in the settings for “Detect Changes on Restart.” This is now set to be similar to the current method of reimporting assets and saving them after they are reimported.

The way it will work now is that we save packages after a reimport if the asset was previously not dirty.

If the asset is currently dirty when we reimport, we assume that it’s the users responsibility to save it.