-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Most games are borked when launched through steamcmd
or directly - consider launching games using steam -silent -applaunch <id>
by default
#51
Comments
so executing I see 2 major ways to address this.
Let me know if you think this would address your issues |
Yes, I think that'd work great! I think that that It's because I found out why my games are stuck on the
However, if there is an error reported by steamcmd itself, it'll correctly return an error exit code, see:
|
Dun dun duuuuuuun! The Maybe out of the question, but under The final part is to link these two binaries used by Steam to launch games to the working directory of SteamCMD:
|
Copy steamconsole.so into your Steam install's ubuntu12_32 folder and run This console seems to be able to open games in the proper Ubuntu environment, but the Steam auth service isn't running so most games will refuse to start. I think that to have proper control over things you end up needing to play the role of the steam executable (or steamclient.so???). |
Here's what I learned so far through my own research, testing and asking around. Running SteamCMD (or, rather, Steam with
TL;DR: The original proposal in this issue is indeed the optimal solution. |
I have this as a fallback if the script doesn't work |
Hi!
I've tried to use
steam-tui
for a fair while now and unfortunately it seems like most often than not games are borked and refuse to launch.For example, lately I've tried to make 4 linux native games work with different launch scripts, both on NixOS and Ubuntu and this is the result:
CHIDDeviceListSDL(): Couldn't load libSDL2-2.0.so.0, not enumerating devices
I managed to get around that by preloading the SDL2 library packaged by steam and running the binary directly with
LD_LIBRARY_PATH=~/.steam/bin32/:$LD_LIBRARY_PATH ~/.local/share/Steam/steamapps/common/Terraria/Terraria
but it threw an exception anywayException: System.TypeInitializationException: The type initializer for 'Microsoft.Xna.Framework.FNAPlatform' threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object
. On Ubuntu it terminates with[S_API FAIL] SteamAPI_Init() failed; create pipe failed.
. I gave up on that one. Works on steam GUI.ERROR! AppId 812810 launch failed (Update required)
but when I runapp_update 812810
there's nothing to update. Running the binary directly runs the game in 0x0 window which well, makes it pretty unplayable. Works on steam GUI.launching...
if steam is running in the background.error while loading shared libraries: libsteam_api.so: cannot open shared object file: No such file or directory
. Again, steam-tui gets stuck inlaunching...
phase. And again, works through steam GUI.All in all, I don't know if it's only happening to me, but based on my experience and the discussions I've read online it seems like
steamcmd
is pretty ill-equipped for launching games beside simple servers, as it doesn't manage the libraries correctly and probably isn't even properly maintained (looking at the tiny documentation and non-existent support). To make user experience better, I'd simply offload the game launch phase straight to steam GUI and with-silent -nobrowser
which seems to work, at least for me, 100% of the time (and this should also auto detect and start games with steam proton).However, that's just my opinion for now - I'd like to hear if anyone else encountered such errors and if you were able to solve it, if it's possible at all.
The text was updated successfully, but these errors were encountered: