mordentral
commented
1 week ago Yeah that doesn't have to do with AS, 5.5 has some engine issues still
Open zeroy99 opened 1 week ago
mordentral
commented
1 week ago Yeah that doesn't have to do with AS, 5.5 has some engine issues still
zeroy99
commented
1 week ago 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!
mordentral
commented
1 week ago 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
zeroy99
commented
1 week ago Ok thanks, I will try narrow down the crash further in that case!
MarkoDev5
commented
1 week ago 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)
zeroy99
commented
1 week ago 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!
MarkoDev5
commented
1 day ago 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
zeroy99
commented
1 day ago 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...
mordentral
commented
1 day ago 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
zeroy99
commented
1 day ago 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!
MarkoDev5
commented
1 day ago 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
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?
zeroy99
commented
1 day ago 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.
mordentral
commented
7 hours ago 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.
zeroy99
commented
3 hours ago 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.
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
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