Why my plugin is being recompiled on each live coding compilation?

[Herobrine20XX]

Hey everyone,

I’ve been having a weird issue with live coding. Each time a recompile is triggered, even without touching a single file, it ALWAYS recompile my marketplace plugin.

For example, it displays that Module.ElectronicNodes.cpp.obj was modified or is new but the file was always there, is not new, nor it is modified…

• Do you know why? (The plugin does not modify itself)
• If not, do you know if there’s a way to disable the live coding for my plugin?

(The problem, obviously, is that’s a fairly slow operation and kinda break the purpose of fast live coding update)

[RecourseDesign]

I’ve had similar issues in the past - and sometimes it’s been because the files have a later modified date than the current date - I’ve had to go through and re-save them. Not sure if that will be your issue here though.

[Herobrine20XX]

Thanks a ton for you for your response!

Sadly, the files are automatically compiled at the launch of the editor (don’t really know why tbh, since it’s a marketplace plugin that should already be compiled), so their last modification is at the start of the engine.

After some more investigation, someone pointed to me that it was a known issue that impacted all marketplace plugins:

Why does UE5 compile every module every time?

After upgrading my 4.27.2 project to 5.0, every time I make even a tiny change in one of my game’s source files the build tool seems to recompile a whole bunch of modules (seems to be all my plugins), so my build times went from < 10s to over a minute. The link steps take the longest. I’m not building the engine from source BTW. I looked through the migration guide and couldn’t find any obvious reason it would be doing this. Can anyone help me please? I’ve attached my build log. ue5_build_…

For anyone finding this, you can fix temporary this bug by adding bUsePrecompiled = true to the .Build.cs file of the impacted plugins (don’t submit a marketplace update with this, though)

[neofuturelabs]

Had the same issue when I updated to 5.0.0

Another way to resolve it is by moving the plugin’s project folder from the engine folder into your project/Plugins folder so that it builds alongside your project. This makes your project more portable too, so I think I’m going to be doing this for any plugins I acquire from now on