Download

.47 Chaos - win 11 - VS 2019 - Constant Crashing

This is probably a ME problem.

Writing this as a tutorial mostly.

REQUIRED STEP FOR CLEAN WINDOWS INSTALL
Enable long file names!
Reg edit. follow this:

Map & Get the engine.
https://github.com/EpicGames/UnrealEngine/tree/4.27-chaos

On a clean install of windows 11 you apparently have to go out of your way to find and install VS2019
https://my.visualstudio.com/Downloads?q=visual%20studio%202019&wt.mc_id=o~msft~vscom~older-downloads

Next, get an incredibuild license and install the VS incredibuild component. Follow this
https://docs.incredibuild.com/win/latest/windows/installation_within_vs_2017_2019.html
The license for a single machine is Free - you do have to sign up.

After you activate the license, clean the build, clean the project files.
To be safe, re-run /Setup.bat - as the build starting/stopping apparently messed with it at least once.

Set up the build correctly.
Development_Editor
X64

Click the UE4 project and make it the startup project.

Click Build, wait the 20m or so.


As of now, things are failing for
Engine\Plugins\MovieScene\MovieRenderPipeline\Source\MovieRenderPipelineCore\Private\MoviePipelineMasterConfig.cpp
For whatever reason, the file was corrupt.
Grab file source from
https://github.com/EpicGames/UnrealEngine/blob/4.27-chaos/Engine/Plugins/MovieScene/MovieRenderPipeline/Source/MovieRenderPipelineCore/Private/MoviePipelineMasterConfig.cpp
and repair.
NOTE: Github desktop Fetch didn’t re-fetch the file on it’s own. This had to be manually pasted in.
The corruption of the file was likely caused by a BSOD while trying to compile the engine via VS 2022. As I said, a “ME” problem…

1 Like

Updated and changed the topic title.
After the process above being repeated a few times - apparently the github files kept coming in corrupt for whatever reason - and finally building.

Now the editor runs, starts, somewhat works as intended, but then crashes out.
Swapping to a debug editor build to see why, as it is a crash without any sort of messaging with the regular build.

Wondering if anyone else is having issues of the sort with the same branch/latest file set.
(I guess this is what I get for doing a clean windows 11 install).