Lots of errors Loading Engine files when trying to migrate my project from 5.0 - 5.4

LaniganDev · June 17, 2024, 11:06pm

Hi, I am trying to migrate my project over to 5.4 from 5.0 and running into issues I am quite new to unreal so any help would be appreicated.

The first log after trying to migrate by opening up UE5.4 and opening the 5.0 project.

Running E:/Unreal Engine/UE_5.4/Engine/Build/BatchFiles/Build.bat Development Win64 -Project="E:/LaniganDEV/Projects/AwakenShooter _backup 5.4/Awaken.uproject" -TargetType=Editor -Progress -NoEngineChanges -NoHotReloadFromIDE
Using bundled DotNet SDK version: 6.0.302
Running UnrealBuildTool: dotnet "..\..\Engine\Binaries\DotNET\UnrealBuildTool\UnrealBuildTool.dll" Development Win64 -Project="E:/LaniganDEV/Projects/AwakenShooter _backup 5.4/Awaken.uproject" -TargetType=Editor -Progress -NoEngineChanges -NoHotReloadFromIDE
Log file: C:\Users\lanii\AppData\Local\UnrealBuildTool\Log.txt
Creating makefile for AwakenEditor (no existing makefile)
Warning: [Upgrade]
Warning: [Upgrade] Using backward-compatible build settings. The latest version of UE sets the following values by default, which may require code changes:
Warning: [Upgrade]     bLegacyParentIncludePaths = false               => Omits module parent folders from include paths to reduce compiler command line length. (Previously: true).
Warning: [Upgrade]     CppStandard = CppStandardVersion.Default        => Updates C++ Standard to C++20 (Previously: CppStandardVersion.Cpp17).
Warning: [Upgrade]     WindowsPlatform.bStrictConformanceMode = true   => Updates MSVC strict conformance mode to true (Previously: false).
Warning: [Upgrade]     bValidateFormatStrings = true                   => Enables compile-time validation of strings+args passed to UE_LOG. (Previously: false).
Warning: [Upgrade] Suppress this message by setting 'DefaultBuildSettings = BuildSettingsVersion.V5;' in AwakenEditor.Target.cs, and explicitly overriding settings that differ from the new defaults.
Warning: [Upgrade]
Warning: [Upgrade]
Warning: [Upgrade] Using backward-compatible include order. The latest version of UE has changed the order of includes, which may require code changes. The current setting is:
Warning: [Upgrade]     IncludeOrderVersion = EngineIncludeOrderVersion.Oldest
Warning: [Upgrade] Suppress this message by setting 'IncludeOrderVersion = EngineIncludeOrderVersion.Latest;' in AwakenEditor.Target.cs.
Warning: [Upgrade] Alternatively you can set this to 'EngineIncludeOrderVersion.Latest' to always use the latest include order. This will potentially cause compile errors when integrating new versions of the engine.
Warning: [Upgrade]
Total execution time: 1.28 seconds
AwakenEditor modifies the values of properties: [ bStrictConformanceMode ]. This is not allowed, as AwakenEditor has build products in common with UnrealEditor.
Remove the modified setting, change AwakenEditor to use a unique build environment by setting 'BuildEnvironment = TargetBuildEnvironment.Unique;' in the AwakenEditorTarget constructor, or set bOverrideBuildEnvironment = true to force this setting on.

Now when it asks me to open the project for build issues, All projects under the SLN related to unreal don’t load

all with the same error:

[MSB4236] The SDK 'Microsoft.NET.SDK.WorkloadAutoImportPropsLocator' specified could not be found. C:\Program Files\dotnet\sdk\7.0.410\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.ImportWorkloads.props at (14:38)

I have tried reinstalling my dotNet SDKS
I have tried regenerating the project code.

Please if anyone could point me in the right direction I would be grateful

LaniganDev · June 20, 2024, 1:30pm

Bump!

Still trying to sort this out

MeddleGearSalad · September 11, 2024, 2:47am

Bump

Doctor_Kannon · September 11, 2024, 4:03am

Also seeing these warnings. I am trying to upgrade a project from 5.3.2 to 5.4.4.

However, the error in particular is a problem:

MyProjectEditor modifies the values of properties: [ bStrictConformanceMode ]. This is not allowed, as MyProjectEditor has build products in common with UnrealEditor.
Remove the modified setting, change MyProjectEditor to use a unique build environment by setting 'BuildEnvironment = TargetBuildEnvironment.Unique;' in the MyProjectEditorTarget constructor, or set bOverrideBuildEnvironment = true to force this setting on.

I’m searching both the project directory and the Build Solution and I can’t find any of these settings.

EDIT
In the MyProjectEditorTarget file, I added line 13:

public MyProjectEditorTarget( TargetInfo Target) : base(Target)
{
	Type = TargetType.Editor;
	DefaultBuildSettings = BuildSettingsVersion.V2;
	ExtraModuleNames.AddRange( new string[] { "MyProject" } );
	BuildEnvironment = TargetBuildEnvironment.Unique;
}

But this gives me a new error:

Targets with a unique build environment cannot be built with an installed engine

This only occurs during an update. A new 5.4.4 project is created without any problems.

dorusoftware · September 11, 2024, 10:07am

in general for unreal, the second number after the unreal version so 5.1, 5.2, 5.3, 5.4, indicates major changes and potential compatibility issues when changing versions.

In general one should not have issues for the third number so 5.1.0, 5.1.1, 5.1.2 etc as those represent patches to that version not major changes.

I’m saying the above to make you understand that if one have issues when upgrading finding what those issues are may not be a simple task because you need to know the differences between those versions and what unreal changed/upgraded under the hood.

A solution you could try, Make sure you have a backup!!, just to be safe pack all the project files in a zip/rar archive or multiple archives if the project is very big, so in case something goes wrong you delete the broken project and replace it with the one that worked

I would start by checking on this forum or youtube what files and folders can be deleted, those files that unreal can recreate. Basically you remove all files/folders like you are preparing the project to be delivered online on some marketplace. You get rid of those several GB of files that unreal uses to make the project work. MAYBE between those files there is one that has those export rules you can’t find so when 5.4.4 version will try open the cleaned project will recreate them correctly for that version

Doctor_Kannon · September 12, 2024, 3:08pm

The third number shouldn’t matter as you say. I’m providing specific info that might be useful to someone with specialized knowledge of the version changes.

Generally, the upgrade should work, no matter what. This upgrade process should have been tested before release. Why it doesn’t work is beyond me. I’m here for help.

Maybe I can get that help from someone who has knowledge of the issue.

Backups are useful. Thanks.

dorusoftware · September 12, 2024, 5:33pm

5.3 to 5.4 is not a guaranteed update, that is what I’m trying to explain. those are two different unreal versions and if you don’t need something from 5.4 that you absolutely need then there is nothing wrong in using 5.3