Fatal error: wrong UE4 Engine Path

Development Programming & Scripting C++
, ,
1

Hi,
I’m packaging my development (some kind of simulation using UE4 and Cesium). On the Editor, and while developing, everything works OK. I’m using JetBrains Rider as my main editor without any issue. When compiling the solution as Editor code, the UE editor launches just fine and the code works as expected.

But, when I tried to pack the solution (as a stand alone executable), UE editor packs it OK, but the resulted game crash on runtime.

Using the console to launch it and retrieve some information, I get this trace:

2022-10-11 20:25:03.971 VertiportSimulator-Mac-Shipping[62946:37868562] [UE4] LowLevelFatalError [File:Unknown] [Line: 2380] 
FMacPlatformMisc::GenerateCrashInfoAndLaunchReporter: posix_spawn() failed (13, Permission denied)

No further information is available. In order to understand the issue, I tried to compile the solution directly using Rider, but as a Game and not as an Editor solution. Then, I’m getting these traces:

LogGenericPlatformMisc: Warning: Failed to determine engine directory: Defaulting to

Looks like it is trying to find the engine somewhere else (“/User/build/Build…”) and fails (engine core is not there…)

So, here are my questions:

  1. Is there any way to set UE4 Engine path before compiling the solution? If so, how?
  2. Could it be something else? Launching the game using the editor (Play button), works just fine.

I would like to have this solution as a stand-alone executable, as I need to work with it inside a network setup, and using the whole editor is not practical at all.

I’m working with UE4.27.2 on MacOS, Apple M1 Plus chip.

Thank you very much.

2

This may seem trivial, but seeing how it seems like a file path, have you tried “fixing up redirectors” in your directories in the editor? Could be something simple pointing to a wrong folder?

Or maybe the solution isn’t compiled on the appropriate setting in your compiler? I’ve had solutions build in vs, package in editor, but not run I think it was mostly because I hadn’t properly built the version inside VS despite having the correct cs targets which is why I presume it even allowed it to package in the editor.

Like for example I was packaging a server and had the appropriate targets, but hadn’t built the server in vs, but the editor still allowed it to package because the build targets were in place…

3

Thank you very much.
I spent the whole day tracing the error. I’m using 2 Plug-ins in my project: Cesium for Unreal and SocketIO-Client. Looks like they are not compatible with each other!

When deactivating one of them, the project packs and compiles just fine. But when using both, it runs just OK on the editor, but crash when packaged…

I’ve post on both repositories / forums (SocketIO and Cesium), but I’m not sure if it would be a solution…

1 Like