1zc / CS2-Pterodactyl

Docker image and Pterodactyl eggs to support CS2 and CS:GO (after archival), based on SteamRT3.
GNU General Public License v3.0
76 stars 24 forks source link

steamclient.so doesn't get automatically updated #44

Closed Vauff closed 2 months ago

Vauff commented 2 months ago

/.steam/sdk64/steamclient.so seems to never get automatically updated (see modification date). image

However /steamcmd/linux64/steamclient.so does. image (1)

This has caused issues after todays CS2 update, because Valve seems to now be compiling against a newer steamclient.so.

[S_API] SteamAPI_Init(): Loaded '/home/container/.steam/sdk64/steamclient.so' OK.  (First tried local 'steamclient.so')
[S_API] SteamAPI_Init(): No SteamClient021
Failed to initialize Steamworks SDK for gameserver.  No SteamClient021
 0 Failed to initialize Steamworks SDK for gameserver.  No SteamClient021

Manually copying the updated lib from /steamcmd/linux64/ to /.steam/sdk64/ can solve the issue in the short term.

LukasW1337 commented 2 months ago

It does update if you run the install script, so hitting 'reinstall' under settings fixes the server.

But for the future. Would this be solved with a symlink?

1zc commented 2 months ago

But for the future. Would this be solved with a symlink?

Maybe, maybe not - I'll take a look as soon as I can

1zc commented 2 months ago

I've updated the docker image's entry point to ensure the steamclient.so binaries for sdk32/64 are updated after SteamCMD is done doing whatever it needs to do

I tried using a symlink, but it looks like this doesn't behave as expected - found my servers just failing to find the file at all.

This is now live on the dev Docker images: image

I'll push to the main Docker image soon and close this issue when I do. No action should be required for any server using this egg, it should automatically pick up the new Docker image on start. Thanks for the report

Truyn commented 2 months ago

Big LIKE!!!