4.7 Projects No Longer Self-Contained

Hello!

I’ve noticed that when creating a new project in 4.7 (working with the source version), my projects are no longer self contained; game project files are being dumped in the engine’s intermediate project directory (http://snag.gy/XLuIR.jpg), the engine solution is having game projects appended to it, but the game project itself is no longer aware of the engine solution.

This is a bit of a mess, since it now means I’m going to have to use one install for each game project, no matter how small they are - otherwise managing source control becomes a nightmare. Surely this is not intentional?

Edit: As a result of the change in structure, the Launcher still recognises projects from the source compiled build, but you can no longer add marketplace content to them through it.

Hi ambershee,

What you are describing sounds somewhat like what happens when a project is created in the root folder of the Engine. Is this where you are creating it?

Hi ,

It’s being created at the top-level directory where I would expect to find it (i.e alongside the Engine directory, not within it. In 4.6, game directories were entirely self contained, but in 4.7 project files and other files are finding their way into the Engine directory.

Sorry, I was out sick for a few days. I just wanted to double-check and make sure I am looking at the same project setup as you are. Are you seeing something similar to this:

\Project Folder\
\Unreal Engine 4.7\
..\Engine\
..\FeaturePacks\
..\Templates\

or does it look like this:

\Unreal Engine 4.7\
..\Project Folder\
..\Engine\
..\FeaturePacks\
..\Templates\

The latter is the only way I can see something similar to what you described. I haven’t yet run any tests on previous versions of the Engine (still trying to get caught up).

The latter is correct.

For the record, I have a source code compiled install, but use the launcher to create new projects and add content (e.g. from featurepacks) to them. I would create the project under the UE 4.7 directory.

In 4.7, the project file for the game is ending up somewhere underneath Engine / Intermediates, which is obviously undesirable.

In 4.7.2 this issue does seem to have been resolved and the project file is being created underneath the game directory,

Hi ambershee,

With some additional testing, I was able to see some definite differences in how project creation worked when a project was created in the root Engine folder (the folder where the Engine folder and .uprojectdirs file is located).

In version 4.5.1:
The new game project solution is included in the UE4 solution after running GenerateProjectFiles.bat. The project solution is still present in the project folder. All project .vcxproj files are contained in both the project’s Intermediate folder and the Engine’s Intermediate folder.

In version 4.6.1:
The new game project solution is included in the UE4 solution after running GenerateProjectFiles.bat. The project solution is still present in the project folder. All project .vcxproj files are contained in both the project’s Intermediate folder and the Engine’s Intermediate folder.

In version 4.7.3:
The new game project solution is included in the UE4 solution without needing to run GenerateProjectFiles.bat. The project solution is NOT present in the project folder. All project .vcxproj files are contained only in the Engine’s Intermediate folder.

This behavior seems mostly unchanged in 4.7 when creating a project in this location and making use of the .uprojectdirs file. When creating projects in this location, it is assumed that the project code is intended to be integrated with the Engine. If this is not desired, you can remove the UE4Games.uprojectdirs file from the root Engine directory, regenerate project files for both the Engine and the game project, and then the game’s solution will no longer be included in the UE4 solution and (for new projects) .vcxproj files from the project will not be placed in the Engine’s Intermediate folder.

I was also able to add a Marketplace pack to a project in each version directly from the Launcher. Where are you running into trouble here?

Hi ambershee,

Was the information I provided above helpful? Do you have any additional questions? I did want to get some clarification on something that you had mentioned previously. You said that you are using the launcher to create new projects. Did you mean that you are launching the binary version of the Engine and then creating a project where the Engine source code is located? If that is the case, are you also switching the project to use the Engine that was built from source code?