Editor keeps reimporting assets without changes

I’m posting this here to see if anyone has the same problem, since I’ve already sent a bug report.

When I make a change on a script, after saving, the Editor insists in reimporting all the Sprites assets. Even if I didn’t touch the Sprites folder or anything like that.

Sometimes even after saving the script and reimporting, the Editor reimports all over again when I click to run the project.

I’ve already force the “Reimport All”, cleared the cache and so on, Editor is still reimporting.

I’m using the Collab, on Unity 2019.3.0f1.

There’s a log or something that I can look to find out why is the Editor judging necessary to reimport this assets?

Thank you.

Edit: I’m using Kaspersky as the antivirus, already tried to pause the file checks, but this problem still happens.

Edit 2: Case 1208671

3 Likes

Just upgraded to 2019.3.0f5 today, also having a similar issue - it tries to reimport all my sprites (albeit only in the Resources folder as far as I can tell) every time I compile scripts, enter playmode, or even change some editor settings, like the font. I couldn’t reproduce it in a new project, however :\

Didn’t have this problem in earlier versions of Unity

Update: I noticed its only reimporting the sprites I use for Anima2d’s meshes, so I’m assuming the bug is to do with Anima2d for the time being

1 Like

If you’re able to reproduce this, a bug report with a reproduction project would be much appreciated.

upgrade from 2019.2.16f1 to 2019.3.0f5;
It keeps importing my psd files everytime I hit play in editor;
really really anoying…
I am using 2d sprite animation;

// update:
problem fixed by updating my anima2D to new version;

Please submit a bug-report as described in this document:

It’s important that you report these issues together with a reproduction project if you want them to get fixed. If you don’t do it, it might be a long time until someone else reports them or until Unity Technologies find them.

After you submitted the bug-report, you receive a confirmation email with a bug-report Case number. Please post the Case number (number only, not the link) in this forum thread for Unity staff to pick up.

thanks, i found the problem;
it’s because i used older version of anima2d, I updated my anima2d, the problem gone;
thanks any way!

1 Like

In my case Anima2d already was at the latest version, deleting it fixed the issue, but reimporting it brought it up again; I tried reproducing this in a new project so I could send a bug report with a example project, but wasn’t able to repro it in a new project :frowning: using Unity 2019.3.0f5 as well.

1 Like

Not using Anima2D but I have the same issue

1 Like

I have the same issue as you. I have an up to date Anima2D and it keeps reimporting assets related to Anima2D when I change a script or test the game. Makes testing much more time-consuming. Has anyone figured out how to fix this?

Hi! I’ve resolved by changing the Asset Pipeline Mode to Version 1 in the editor project settings (using Unity 2019.3.0f6)

6 Likes

Thank you so much for sharing your solution! This fixed it for me.

Considering version 1 is marked as deprecated already, thus being removed eventually, I’m not sure that using v1 is a long-term solution to the problem. :wink:

1 Like

The tilemap system heavily relies on version 1 as well. On 2019.3 it’s barely impossible to paint tiles in a prefab when version 2 is activated. It’s worrying since 2019.3 is the best they could come up with so far and it really looks like some kind of tinkering (at least for the tilemap system).

Using version 1 was the “official” solution we sere given to “solve” our tilemap painting problem.

In Unity speak, “deprecated” often means “stable”.

6 Likes

The team was able to reproduce this. I’ve reached out to them for a follow up statement.

2 Likes

The bug has been fixed internally and the fix will be backported to one of the next patch releases for 2019.3.

I too am experiencing the same happening.

Experiencing the same. Thanks for fixing the bug!

This should be fixed in 2019.3.4f1.

I’m using unity 2019.3.5 still this issue exists. This issue is heavily affecting my productivity.

5 Likes