Core Keeper

Core Keeper

Vis statistikk:
GnoarnPlays 5. mai 2022 kl. 22.24
Ubuntu 21.10 Unable to init server
This is the error im getting.

# Option “-x” is deprecated and might be removed in a later version of gnome-terminal.
# Use “-- ” to terminate the options and put the command line to execute after it.
Unable to init server: Could not connect: Connection refused
# Failed to parse arguments: Cannot open display:

which a display is really not needed to run a server. Installed Gnome and still this is a no go with the linux Server Launch script.
< >
Viser 115 av 17 kommentarer
petersm8 6. mai 2022 kl. 12.23 
I solved this problem by using vncviewer and remoting in to the server and starting it that way. I agree though, would like a non-display version.
Sist redigert av petersm8; 6. mai 2022 kl. 12.24
GnoarnPlays 7. mai 2022 kl. 21.34 
Will give that a shot. It won’t launch it via cron job that’s for sure
max  [utvikler] 10. mai 2022 kl. 1.43 
If you look in the Server directory then there is a _launch.sh file you can use instead which is what is called via launch.sh.

When we move from experimental and put it on a separate app then having it call the graphical terminal is needed to make it launch via Steam properly, but that is the only reason. We still need the GPU to do some of the procedural generation, but the _launch.sh script works around that by launching via a software renderer.
GnoarnPlays 11. mai 2022 kl. 19.23 
sadly that did not work either. will try it again. i explored all visible options before making a post.
GnoarnPlays 12. mai 2022 kl. 7.15 
Opprinnelig skrevet av max:
If you look in the Server directory then there is a _launch.sh file you can use instead which is what is called via launch.sh.

When we move from experimental and put it on a separate app then having it call the graphical terminal is needed to make it launch via Steam properly, but that is the only reason. We still need the GPU to do some of the procedural generation, but the _launch.sh script works around that by launching via a software renderer.

Updated to the most current with the dedicated server and the is what i get off the _launch.sh

./_launch.sh: line 44: 29699 Segmentation fault (core dumped) DISPLAY=:99 L D_LIBRARY_PATH="$LD_LIBRARY_PATH:../Steamworks SDK Redist/linux64/" ./CoreKeeper Server -batchmode -logfile CoreKeeperServerLog.txt
petersm8 12. mai 2022 kl. 7.39 
I got to this point as well. But I gave up. I believe it has something to do with box64 on my end. You should also post the ServerLog.txt. It's in the Server folder. I posted something on the box64 github but haven't gotten a response.
Saiz 12. mai 2022 kl. 9.39 
Opprinnelig skrevet av GnoarnPlays:

Updated to the most current with the dedicated server and the is what i get off the _launch.sh

./_launch.sh: line 44: 29699 Segmentation fault (core dumped) DISPLAY=:99 L D_LIBRARY_PATH="$LD_LIBRARY_PATH:../Steamworks SDK Redist/linux64/" ./CoreKeeper Server -batchmode -logfile CoreKeeperServerLog.txt


This error is from it looking in a directory above core keeper for the Steamworks SDK Redist. My solution would be to have you go edit the _launch.sh (line 35) and set the location of this on your server if you are installing in a forced path (Normally its in the user's home directory ie: ~/.steam/steamapps/common/Steamworks SDK Redist/). Or if you are using default paths make sure you have the steamworks sdk installed as well as core keeper.

Use this command to install both apps to default locations
steamcmd +login anonymous +app_update 1007 +app_update 1963720 +quit

After this try to run the game from ~/.steam/steamapps/common/Core Keeper Dedicated Server/ and run _launch.sh
Sist redigert av Saiz; 12. mai 2022 kl. 9.44
GnoarnPlays 12. mai 2022 kl. 13.14 
Opprinnelig skrevet av petersm8:
I got to this point as well. But I gave up. I believe it has something to do with box64 on my end. You should also post the ServerLog.txt. It's in the Server folder. I posted something on the box64 github but haven't gotten a response.
are you getting an elf error too? if so i believe that is a x86/x64 issue.
steamclient.so: wrong ELF class: ELFCLASS32
that error is because its looking for ELFCLASS64
Man of God 12. mai 2022 kl. 13.32 
Opprinnelig skrevet av max:
If you look in the Server directory then there is a _launch.sh file you can use instead which is what is called via launch.sh.

When we move from experimental and put it on a separate app then having it call the graphical terminal is needed to make it launch via Steam properly, but that is the only reason. We still need the GPU to do some of the procedural generation, but the _launch.sh script works around that by launching via a software renderer.

Is it possible to get the CPU to do this at all? I'm lucky enough to have a discrete GPU on my home server to do this, but I would really like to run multiple instances headless on systems without a graphics card. I guess you are working on this right?

I'm thinking about getting around this by having the map generated on one machine with a GPU and then moving it over to another. But I haven't tested that.
Sist redigert av Man of God; 12. mai 2022 kl. 13.33
Saiz 12. mai 2022 kl. 14.23 
The _launch.sh does use a software based renderer to generate the map. I am running this on a headless server with out a gpu with out issue.
Sist redigert av Saiz; 12. mai 2022 kl. 14.28
max  [utvikler] 12. mai 2022 kl. 22.43 
Opprinnelig skrevet av Saiz:
Opprinnelig skrevet av GnoarnPlays:

Updated to the most current with the dedicated server and the is what i get off the _launch.sh

./_launch.sh: line 44: 29699 Segmentation fault (core dumped) DISPLAY=:99 L D_LIBRARY_PATH="$LD_LIBRARY_PATH:../Steamworks SDK Redist/linux64/" ./CoreKeeper Server -batchmode -logfile CoreKeeperServerLog.txt


This error is from it looking in a directory above core keeper for the Steamworks SDK Redist. My solution would be to have you go edit the _launch.sh (line 35) and set the location of this on your server if you are installing in a forced path (Normally its in the user's home directory ie: ~/.steam/steamapps/common/Steamworks SDK Redist/). Or if you are using default paths make sure you have the steamworks sdk installed as well as core keeper.

Use this command to install both apps to default locations
steamcmd +login anonymous +app_update 1007 +app_update 1963720 +quit

After this try to run the game from ~/.steam/steamapps/common/Core Keeper Dedicated Server/ and run _launch.sh

Yeah, it assumes it is run from the server directory currently. I'll make a note to improve that.
max  [utvikler] 12. mai 2022 kl. 22.50 
Opprinnelig skrevet av petersm8:
I got to this point as well. But I gave up. I believe it has something to do with box64 on my end. You should also post the ServerLog.txt. It's in the Server folder. I posted something on the box64 github but haven't gotten a response.

We haven't tested box64 at all. I'm not that familiar with it, but also not too surprised it doesn't work. On the chance the problem is related to xvfb, then maybe it actually works better without that if you just run the CoreKeeperServer command directly?
GnoarnPlays 13. mai 2022 kl. 7.28 
Opprinnelig skrevet av max:
Yeah, it assumes it is run from the server directory currently. I'll make a note to improve that.

i figured out where i inadvertently installed the steam client to. sadly even with the 64 sdk it installed nothing under .steam and keeps looking for info there even with stating where the 64bit steam client is located. keeps throwing a steamclient.so: wrong ELF class: ELFCLASS32 error. and fails to open .steam/sdk64/steamclient.so just for the fact it does not exist. right now im removing all traces of steam and trying to get it installed.
GnoarnPlays 14. mai 2022 kl. 7.56 
UPDATE:
After installing the SDK with steamcmd +login anonymous +app_update 1007 +quit
i had to
mkdir ~/.steam/sdk64
cp ~/.local/share/Steam/steamcmd/linix64/steamclient.so ~/.steam/sdk64/steamclient.so

then it would run as expected under linux with the _launch.sh

what this does is make the directory and copy the 64 bit steam client to the directory where its looking for it. for those wondering will provide a Tutorial of what i did to achieve this. mind you i had to install ubuntu-desktop to make this work. it will work headless it just needs the ability to open a screen location. now this does not guarantee that it will run smooth because many servers have a video card just the specs are generally crappy since all its function is to run command line.

Note this is aslo considered a patch to get it working not a real fix. the real fix would be getting the program to actually use the path given to it for the LD_LIBRARY path. i would also recommend adding steamcmd +login anonymous +app_update 1007 +app_update 1963720 +quit to the top of you _launch.sh where it updates the game. might also add the cp to the top to or make a link from ~/.steam/sdk64/steamclient.so to point to the local share version so it keeps everything updated to latest. every time you launch the game server.
< >
Viser 115 av 17 kommentarer
Per side: 1530 50

Dato lagt ut: 5. mai 2022 kl. 22.24
Innlegg: 17