Steamworks: [Ubuntu] Latest extension with API 1.55 seems to no longer be initialising correctly
Opened this issue · 3 comments
Description
I've been working on an update to my game Juan Sin Miedo during the last few weeks and now than it's all ready I found that the game no longer runs correctly on Ubuntu with either the YYC or VM compiler, the game still seems to work fine on Windows but when I test the game on Linux now Steam does not initialise while I'm running my game correctly and seems to cause the game to crash randomly. I'm using the new Steamworks extension realeased by and the correct Steamworks API specified (1.55), since this is happening with the newest version of the engine I'm not sure if it's already been reported yet and besides this post about someone else having a similar issue I'm not sure what to do to fix this problem, I've made sure my Visual Studio is setup correctly and even a few months ago everything was working just fine which makes me think the issue is coming from this new Steamworks extension as that's the only major difference in Game Maker since I last updated my game.
Steps To Reproduce
All I have to do is run the game on Linux and within 10 minutes or less the game crashes regardless of compiler, no error message is given but it seems related to Steamworks API.
Which version of GameMaker are you reporting this issue for?
IDE v2024.4.1.152 Runtime v2024.4.1.201
Which operating system(s) are you seeing the problem on?
Windows 10.0.19045.0
Which platform(s) are you seeing the problem on?
Ubuntu
Hi, can you confirm that steam_initialised() returns true while your game is running? There are known cases where calling a Steam function without an initialized Steam API may hard crash the game.
My project fails to complete the post_build_step for this extension when building through an ubuntu VM with Igor and my Jenkins setup.
Building it through the same ubuntu VM manually using gamemaker IDE on Windows 11 works perfectly fine.
@Prazon, Is this still a problem? Last time I checked the user was using an old version of the extension, and updating it solved the post_build_step issue.