Jump to content

Recommended Posts

Posted

I have VS on Linux Mint 22. Flatpack on an NTFS drive (primary linux drive is questionable)

I can run an executable in that folder once. Once that's been done, none of the executables will run. 
e.g.: If I run the game, it will run once. If I close it and try running it again, nothing happens, and no other executables will run either. Not VS, not the dedicated server, none of the .sh files - nothing.

The same thing happens if I run any of the other executables. 

Any idea what I've got wrong? 

I'd also like to move the VintageStoryData folder off that drive. It needs to be replaced, but that's not something I can do ATM.

Posted
9 minutes ago, SlateSlavens said:

I have VS on Linux Mint 22. Flatpack on an NTFS drive (primary linux drive is questionable)

I can run an executable in that folder once. Once that's been done, none of the executables will run. 
e.g.: If I run the game, it will run once. If I close it and try running it again, nothing happens, and no other executables will run either. Not VS, not the dedicated server, none of the .sh files - nothing.

The same thing happens if I run any of the other executables. 

Any idea what I've got wrong? 

I'd also like to move the VintageStoryData folder off that drive. It needs to be replaced, but that's not something I can do ATM.

What happens if you drag and drop one of the executables into a terminal and try to run it from there?

Posted
1 minute ago, Diff said:

What happens if you drag and drop one of the executables into a terminal and try to run it from there?

lol, odd things (server.sh):

Fatal! I require screen but it's not installed.  Aborting.

but double clicking server.sh does nothing, same for VintagestoryServer

okay. dropping VintagestoryServer in a terminal worked...  I'm just getting back into linux after being gone since the Athlon 900 was new...

 

Posted (edited)
8 minutes ago, SlateSlavens said:

 

Fatal! I require screen but it's not installed.  Aborting.

 

If that's one of the errors, then that should be pretty straightforward. That one is exactly what it says on the tin, the server.sh script requires screen (which is the name of a command line program that lets things keep running even after the terminal is closed), pgrep, and the dotnet CLI to be installed. Double clicking on it won't do anything because they'll still emit the same error messages, just without any way to communicate them to you. I'd stick with the terminal and keep running it and fixing the issues it communicates to you through the error messages.

 

And on the migration, there'll probably be a few issues there, too. For the client, too, for mods. I got bit by that one myself, so make sure all the paths in your clientsettings.json are updated for being on Linux.

Edited by Diff
  • Thanks 1
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.