The first thing you could try to do to see what’s happening is to get the logs from the client to see what happens before it crashes. Last I checked, you should be able to find your crash logs through this path: c:\Program Files\Unreal Engine\4.0\Engine\Programs\CrashReportClient\Saved\
Once you find out the errors that make your client crash, it should be easier to narrow down the cause of the issue.
There’s someone else who had the exact same error, and they solved it by replacing the PIEInstanceID != INDEX_NONE statement to:
if(PIEInstanceID == INDEX_NONE) {
PIEInstanceID = 1;
};
Like they said in the thread, it’s a temporary solution, but it seems that creating an empty map solves the problem as well. Not sure if that solution would work for you, but it’s worth giving the if statement a try.
Yeah I saw that post but it’s not really a fix it’s just over-riding the issue and I don’t know what it would break down the line. I talked to someone who said they could use a World Partition map with a dedicated server and connect via PIE so I’m truly confused by it. For now I have been using a temporary non-WP map and when I need to test it properly I can use a packaged game build to connect, which works because it’s not PIE mode. However this seems like a bug as it’s out of the box.
I think this is a serious bug that Epic team has to consider first, I posted the same bug serval months ago and find where is the bug in the source. World partition is import for future open-world online games and I’m porting my Unity online game project to UE5 currently, this bug makes the progress stops so far.
Im 100% sure I was setting that. However I will double-check it later today. It might also be that things have changed since 5.1 and 5.1.1 but thanks for coming to post a solution.
My server default map is set and I’m still getting the crash. If my map is an “Empty Level” or a “Basic” level there are no problems. It’s only when using an open world (empty or not) that the crash occurs.
I imagine it’s some obscure setting that isn’t on by default but I’ve yet to find it. I’m using 5.1.1 btw. My only way around it so far is to package both the client and server when testing, which is annoying to say the least.