Most games are borked when launched through `steamcmd` or directly - consider launching games using `steam -silent -applaunch <id>` by default

[zeerooth]

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:

• Terraria - doesn't launch, steamcmd reports 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 anyway Exception: 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.
• missed messages - steamcmd reports that ERROR! AppId 812810 launch failed (Update required) but when I run app_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.
• War Thunder - steamcmd reports ERROR! AppId 236390 launch failed (Missing executable). Works if launched directly either from steam or command line, but steam-tui reports that it can't find the executable anyway (because of steamcmd) or gets stuck on launching... if steam is running in the background.
• You Have to Win the Game - basically the same as missed messages, but when run directly this one can't even load steam api by default error while loading shared libraries: libsteam_api.so: cannot open shared object file: No such file or directory. Again, steam-tui gets stuck in launching... 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.