I just downloaded UE for the first time. After installation, when I launch the program, during the initialization (every time around 75%) it crashes and gives me this message :
I am uncertain as of what is causing this issue but I did notice some things from your logs which you may want to consider.
Unreal as far as I know does not come with PythonScriptPlugin out of the box so I am unsure as of why that file would be missing. Perhaps your download was corrupted and you could try redownloading the Engine.
If you decide to redownload, I would suggest that you install it on internal storage, you can migrate it later if everything works by renaming the file, starting another installation on desired drive, stopping that and deleting a version file and then copying the first file there after which you resume download.
Another thing you could try is making sure your graphic drivers are up to date.
I have the same error.
Mac Air m1 16gb. Ventura 13.4.1
I install UE 5.3.1 on external disk (Kingston XS2000), and Xcode 14.3.1
Second try was with 5.2.1 and Xcode 14.3.1 - same error.
On youtube I saw there was UE 5.2.0 + Xcode 13.4.1, and everything worked. I dont see 5.2.0, only 5.2.1, so now I’m trying to set 13.4.1, but it didnt work with Ventura 13.4.1 ((
@gooddimmi Do you install into the standard Epic Games directory or a custom one, and/or on external drive? I’m want to rule out the internal vs external drive causing the issue.
All 3 versions UE 5.1.1 / 5.2.1 / 5.3.1 were installed on an external drive since the MacBook’s drive was already filled with other software.
Epic Games launcher and Xcode installed on MacBook’s drive.
In essence, whether internal or external drive that should not have an impact since for the filesystem and the environment it is one filesystem whatever kind of drives are mounted.
I mounted the external drive to the default Epic Games path, that didn’t resolve the issue. So it is not default vs custom path.
UE has something screwed badly.
This part is the key:
FPythonScriptPlugin::InitializePython() Address = 0x18e82bd54 (filename not found) [in UnrealEditor-PythonScriptPlugin.dylib]
FPythonScriptPlugin::StartupModule() Address = 0x18e82b4a0 (filename not found) [in UnrealEditor-PythonScriptPlugin.dylib]
Looking into their code there is just path setting going on in FPythonScriptPlugin::InitializePython() before reaching the
crash line Py_InitializeEx(),
// Set-up the correct program name
{
FString ProgramName = FPlatformProcess::GetCurrentWorkingDirectory() / FPlatformProcess::ExecutableName(false);
FPaths::NormalizeFilename(ProgramName);
PyProgramName = PyUtil::TCHARToPyApiBuffer(*ProgramName);
}
and,
// Set-up the correct home path
{
// Build the full Python directory (UE_PYTHON_DIR may be relative to the engine directory for portability)
FString PythonDir = UTF8_TO_TCHAR(UE_PYTHON_DIR);
PythonDir.ReplaceInline(TEXT("{ENGINE_DIR}"), *FPaths::EngineDir(), ESearchCase::CaseSensitive);
FPaths::NormalizeDirectoryName(PythonDir);
FPaths::RemoveDuplicateSlashes(PythonDir);
PyHomePath = PyUtil::TCHARToPyApiBuffer(*PythonDir);
}
If it is humanly possible to compile the code I will add prints of the values to see if they get screwed in anyway.
UE has Python packaged inside. It uses the Python it comes with. The code that sets folders starts from UE installation folder. External installation does not help you.
I have experimented with getting the UE’s Python run, just need more time to understand the issues they have in their distribution.
Thanks for the information, I’ll still try to free up space on the MacBook’s disk and transfer the UE there since the external drive, when formatted in APFS, will not be visible to Windows, but for me this is important.
I also tried running it through the terminal using the command:
You were absolutely right. The external drive was exFAT, apparently for this reason there was an error. I freed up some space on the internal drive and installed 5.3.1 and now everything works. Thank you!
