Fatal Crash on Packaged game UE5.5 #98
Comments
|
Yeah that doesn't have to do with AS, 5.5 has some engine issues still |
|
Hi, so I wasnt expecting quite this answer! Having AS plugin generate this issue, not to say it is the issue but its linked at a minimum. Anyway, for something maybe more appropriate to ask, can you confirm you can use AS on a packaged Game with UE5.5 and using SpaceWar? Thanks for your time! |
|
I literally just packaged to shipping with AS and steam to test something else, and it works just fine. There are multiple issues with loading packages in engine currently that are reported. This might have been a source based build but if the engine is failing to load the pre-built binaries that isn't something I can fix and others aren't all having that issue. Here, you can test for yourself, this is a 5.5 shipping build with steam enabled, you can check that the overlay appears. Its running fine for me. Its a VR example project but you can move around in 2D in it as well. https://drive.google.com/file/d/1qajgQ0lujRlL0GMJUk5H1gdpm0XSmmRT/view?usp=sharing |
|
Ok thanks, I will try narrow down the crash further in that case! |
|
I also had fatal crash on packaged build when adding advanced sessions and steam advanced sessions. Packaged build worked fine before adding them. Might be some coincidence, i noticed that Unreal 5.5 has been acting weird when doing builds (RAM goes to 100% usage every time, didnt have that issue on 5.4.4) |
Thanks for sharing, I will dig more myself, please post if you do find something also! |
Any luck? I still get fatal crash when enabling adv sessions and steamadv sessions |
Nope - still the same, my only progress is that I narrowed it down to the AdvancedStemSession causing the fatal crash, game loads when just AdvancedSession is loaded - Again not sure where the fault lies... |
|
You can package development and check the saves/logs for the crash reason, though usually that is related to the steam sdk not being written out to the directory |
After adding some missing lines in the DefaultEngine.ini The example 5.5 Project with both AS and ASS is ok and starts - but not my actual game, something else then causing this, I need to dig some more I guess. Can you explain what you mean by "steam sdk not being written out to the directory" ? Thanks for your time! |
I did package dev, and i get fatal error with no additional logs or any cpp error lines, i had to use Rider debugger to read out the error... can you see my screenshot?
|
You can just create a shortcut on your EXE and add -log on the end, it will produce better logging for you.
|
|
That is that issue with the engine not correctly packaging / referencing the steam dlls in the package directory. You can manually copy the dll into it. The very latest 5.5 repo has it trying to force the dlls to be packaged but I cant test if it fixes this because I have never had the issue (most don't). They broke this sometime in UE5, unsure which patch off the top of my head. If you want to pull the latest 5.5 repository source (not precompiled) and try again? It used to always package out the steamdlls up until some of their EOS changes where it doesn't anymore. They haven't been testing many of their EOS changes against the raw steam subsystem. |
Sorry to keep going on with this one but what DLLs are expected to be seen in packaged project and where should they resides? Binaries\Win64 ? Thanks again for your time |
Yh UE 5.5 is a bit weird, Ultra Dynamic Sky also had some issues ... i will test with latest from your repo, i havent had time to get to it :) |
Steam_api.dll, you can place it in the .exe directory to automatically be picked up |
A bit confused more than i should now because on 5.4 Packaged - which works fine - the only Steam DLL I see in the packaged version is this one and I also see it on the 5.5 Packaged
|
Just tried this with a fresh install of UE 5.5.1, redownloaded latest Adv session and steam adv session, placing steam api dll in exe directory, and still no luck, fatal crash on startup always! Any more ideas? |
|
Try latest version / binaries, I changed the steam event causing the issue to a manual bind instead of epics auto bind variable. |
Success!!! No fatal crash now! Game started up fine! Thank you, gonna test joining with a friend but that always works. |
|
seems to work with new updates |
|
indeed it does now, thank you! |
Hi, how do you managed working this on 5.5.1 in shipping build? Tried the plugin version from official site and version from master (don't know if it is identical). In any cases is crash. Yes, I moved the steam_api64.dll to executable game path. |
|
what is your crash log? it may be unrelated to this fix. Package to development and open the log after it crashes |
I am sorry, the problem is that I have the crash on shipping build but not in development build, so I can't reproduce the crash on the development. |
Even on Shipped Build packaged you will have a crash dump log in the Saved folder I think |
|
First I copied the binary file 5.5.2 into the plugin folder and packed the game as a shipping version. When I create a session I get a fatal error. That's actually logical, because the Steam API doesn't work. No overlay. Then I compiled the source and got the same error. I can't show a log because I don't get one with the shipping version. |
|
Creating a session should never cause a fatal error, steam api or not, the engine falls back to its stock subsystem if the steam subsystem can't load. Unlink everything from the create session node (extra settings) and see if it still does that, if it does, its more likely you are trying to sample something from the async nodes without waiting around for the result and using invalid data or something (ie, its likely in your project code). The only crash I am aware of (there may be more) in Epics current steam subsystem is querying the OnlineStatusString generates the string incorrectly causing a malformed string that buffer overflows. I just don't let people call that function in the plugin anymore until they fix it. They ported to a new api for the steam stuff and they broke a lot of their own code doing so. |
Hi!
We use your AdvancedSessionsPlugin on UE5.4.1 with no issues (other than Receive/Delegate Events) but when Testing a migration over to UE5.5 we are seeing a Fatal Crash on Packaged (Debug) game - This is using your 5.5 Binaries or a recompile of plugin from 5.4.1 (must be v5.4) ; The Game works PIE and also standalone including Steam friend, this is only on Packaged build.
Crashed Module is FAsyncLoadingThread
The Fatal Crash, if its any use
The text was updated successfully, but these errors were encountered: