Toribash
Originally Posted by sir View Post
Hi, what's the error you're getting and what Linux distro are you on?

Im on ubuntu. Im not getting any error. Game not starting.
I went to settings to the betas (I wasnt on beta) and selected previous stable version and it worked. So its clearly update problem

Can you please try doing the following and paste the output here:

- Launch Steam
- In terminal, navigate to Toribash installation folder (here it's ~/.local/share/Steam/steamapps/common/Toribash, you can check by choosing "Browse local files" option when right-clicking Toribash in Steam Library)
- Run ./toribash_steam
Now I rolled back to 5.53 and playing so I update and try later.
Also my .local/share/ folder not have Steam/steamapps/common/Toribash folder it have just Steam/steamapps/common/Toribash folder

and the toribash_steam file i have only in~/.steam/debian-installation/steamapps/common/Toribash/ folder
-----
updated to 5.54
tb not started again
went to ~/.steam/debian-installation/steamapps/common/Toribash/
did in terminal ./toribash_steam

got this

./toribash_steam: error while loading shared libraries: libGLEW.so.2.1: cannot open shared object file: No such file or directory

------

Rolled back to 5.53 again
did in terminal ./toribash_steam
tb working

and in terminal now I see the

Setting breakpad minidump AppID = ******
Steam_SetMinidumpSteamID: Caching Steam ID: ******************* [API loaded no]
Steam Username: xbcz Userid ************************
Initiated with OpenGL version: 4.6 (Compatibility Profile) Mesa 21.2.6
fragment program: sh_raytracespheres
0:196(85): warning: `raypos' used uninitialized
0:196(94): warning: `raydir' used uninitialized
0:199(32): warning: `raypos' used uninitialized
0:199(41): warning: `raydir' used uninitialized
0:200(27): warning: `mindist' used uninitialized
0:203(26): warning: `raypos' used uninitialized
0:203(35): warning: `raydir' used uninitialized

Ambient Occlusion + Bumpmapping supported (level 12 of 12)
Depth of field supported!
Last edited by xbcz; Mar 14, 2022 at 12:27 PM. Reason: went to 5.54 and back to 5.53
Originally Posted by sir View Post
Pushed a fix, should be working now

Yes, now 5.54 working

thank you