search

TeamHypersomnia / Hypersomnia

Multiplayer top-down shooter made from scratch in C++. Play in your Browser! https://hypersomnia.io Made in 🇵🇱
https://hypersomnia.io/
GNU Affero General Public License v3.0
1.17k stars 52 forks source link

Game Crashes on Startup with various issues - suggestion to create readme #267

Closed werzum closed 1 year ago

werzum commented 1 year ago

Hey,

I am a Pop OS user and had various problems trying to get the game to run on Pop OS (22.10). Maybe a short readme for the installation would be helpful, despite the argument that Linux users should be tech-savy enough to find out on their own). I had the issue that I chown +Xed only the Hypersomnia executable, which lead to various errors (either the application to not be able to establish an audio context or crashing with an unspecified error with an unspecified iostream_category_error).

I finally figured out I had to sudo chown -R user:user hypersomnia/ to own the entire folder, and then start the executable without sudo. This will probably seem trivial to some, but I still think that could be mentioned somewhere.

Hope this helps and of course thanks for your effort to create such a cool game!

geneotech commented 1 year ago

Hey there! I admit I've never seen this problem on either Arch Linux or Ubuntu - if I unpack Hypersomnia-for-Linux.tar.gz the Hypersomnia file already has the executable bit set and can be called from the command line out-of-the-box. The whole directory is automatically owned by the user's account as well.

Are you sure this is not a problem specific to Pop OS or how you extract the .tar.gz file? I haven't yet tried to launch the game there at all - first time I'm hearing about Pop OS actually! :grin:

geneotech commented 1 year ago

In case you're trying to build it yourself - I just found out there's a little problem with the run target - it's supposed to set the working directory automatically, I'm going to take a look.

geneotech commented 1 year ago

Yep, I found the issue, the run target didn't correctly set the current working directory (it does set it but the executable was overwriting it - it's meant to do it only for production so that the end-user could launch the binary from any working directory), the One-shot launch script in README should now work flawlessly.

Thanks for reporting!

werzum commented 1 year ago

hey, thanks for the quick reply - I actually wasnt trying to build it, just run the regular build. Maybe its PopOS specific? But glad it helped you fix another bug :+1: Ill close this issue