Why is Unreal 5.3.2 Source - Now only working as project specific engine installations, rather than engine installation specific projects?

IntXThOrn
Sat, 20 Jan 2024 14:44:17 +0000
Programming & Scripting

When installing 5.3.2 from GitHub release source using the latest VS 22 with the latest updates these engine builds become project specific engine installations, rather than engine specific projects. An example of this.

Install Source Engine 5.3.2 - Setup - Gen files - Build Succeeded
Associate a 5.3.2 Project “TestProj” with that new engine. Generating project files. Open the solution, select project and Build Project Only. Now the entire engine rebuilds including the project.

Now the engine has made itself project specific!

So now we right click our “OtherProject” also a 5.3.2 source project. We associate to the same engine, generating project files. Open the solution, select the project, Build - Project Only. Entire Engine rebuilds.

Now we open the first project.

Message box comes up to tell us the project requires itself to be rebuilt in the IDE. So we load up project one and Build - Project Only. The Entire engine is rebuilt

So we load up project two now and that tells us, rebuild in your IDE.

And so on…

This only started happening recently, confirmed with another remote developer using independent systems.

Both of us have been working with UE since UE4, in source, as C++ devs, never seen this behaviour before.

Can only describe as : 1. Project specific engine installations, rather than engine installation specific projects

Impact of this is now having to have a source engine for every project that we need to load each day.

Thoughts or information welcome…

5 posts - 3 participants