Editor saving and recompiling unchanged resources

Hi,

For the last few days I’m having a really annoying problem: Sometimes - and the strange thing is that I can’t really reproduce this - when I change only a value in a graph node of a blueprint and hit ctrl+s, the editor also saves ~10 other blueprints because they supposedly have been changed. Which was not the case. And when I want to play the level in the editor, because it recompiles all “changed” blueprints, it takes 5-10 secs instead of 1 sec to start playing.

For example, when this bug occurs, my custom HUD blueprint is always one of these blueprints that needs to be recompiled before playing, even if I’ve just changed a value in a completely unrelated blueprint. When I restart the editor, everything is back to normal again.

Is this a known issue? Is there a solution? My current workaround is to disable the auto-compile feature, always manually compile my changed blueprint and hit “NO!” when I get asked if I want to recompile blueprints X Y Z, because they “have been modified without being recompiled”.

Thanks!

Any ideas?

I’m still having this problem. Just running the game in PIE und stopping it sometimes sets a dozen assets back to unsaved state. 90% of each commit I do (using Git) consists of files I didn’t even change since the last commit…

That’s because your blueprints somehow depends on first one. Calling it’s function or connected through interface, or something else.

Hmm, I don’t think so. The HUD BP constantly gets recompiled even if I only change a number und an actor BP that has nothing to do with the HUD. And the problem occurs only since around June…

The real problem isn’t even the recompiling, but that the BP file also gets changed and needs to be recommitted to git. Therefore I can’t see on which blueprints I really worked in the git history, because nearly all are committed.

Hi Anteevy,

Apologies for this one getting overlooked. We are going back through a lot of these bug reports now in order to resolve them.

Are you still experiencing this crash or did it get resolved for you in a newer release of the editor?

If it’s still an issue, please let me know and I can look into this further.

Thank you!

Tim

Hi anteevy,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.

Thank you.