Palworld (1623730)

[ruineka]

Compatibility Report

• Palworld
• 1623730

System Information

• Steam Deck
• Video driver version: Mesa 23.1.3
• Kernel version: 6.1.52-valve14-1-neptune-61
• Proton version: Experimental Bleeding Edge

I confirm:

• [x ] that I haven't found an existing compatibility report for this game.
• [x ] that I have checked whether there are updates for my system available.

Symptoms

The OSK doesn't grab focus of the text field unless you tap in it first. If you manually invoke the keyboard it'll look like it's in focus and receive inputs, but it doesn't. Instead it'll receive gamepad inputs as you navigate through the OSK.

Reproduction

Go to multiplayer via friend code and attempt to type in a friend code or name your character at the character creation screen.

[StripedMonkey]

I'm going to try and debug it here in the next few days and report back, but the game runs perfectly on my desktop (3090, 7950x), but suffers from frequent freezes and appears to hang my Steam Deck when playing for any extended period of time. Looking at protondb, this seems to be a common theme in reports for the deck, though it's hard to say who played long enough to notice the issues.

From personal experience, the most consistent mechanism to induce a freeze is entering and exiting dungeons or loading new regions on the map. Depending on the situation it can be anywhere from 5 minutes to an hour before the deck freezes. Staying roughly in one location/"at base" seems to work fine, but will still eventually cause a freeze.

[ruineka]

Replying to https://github.com/ValveSoftware/Proton/issues/7448#issuecomment-1962663932

The crashes on the steam deck are a result of the unified memory being maxed out. If you monitor your memory usage you will see the performance drop after 16GB is exceeded and the swapfile is used and once it hits 18GB it will lock the system up. Bosses, dungeons, and frequent fast travels continue to consume more memory and it’s never freed.

[StripedMonkey]

Whilst that theory has merits, the fact is that I played for ~9h straight(? It may have been two sessions) on desktop, speed running dungeons across the entire map without issue. If going in and out of a singular dungeon can cap that 18GB limit in 5 minutes, I nor anyone else could play with even 32GB of memory.

It's possible you're right, but I'm not entirely confident that's all that's going on. Unified GPU/CPU memory or not.

[ruineka]

Whilst that theory has merits, the fact is that I played for ~9h straight(? It may have been two sessions) on desktop, speed running dungeons across the entire map without issue. If going in and out of a singular dungeon can cap that 18GB limit in 5 minutes, I nor anyone else could play with even 32GB of memory.

It's possible you're right, but I'm not entirely confident that's all that's going on. Unified GPU/CPU memory or not.

I have played 200hrs on my Steam Deck exclusively so I know exactly how to crash it and prevent it before it happens. I haven’t played on a desktop, but what I would do is monitor your ram usage on your desktop and see if it goes up over time like you can observe on the Steam Deck. I suspect your desktop would likely drop in performance if the vram is maxed instead of a system lockup like we are seeing with the Steam Deck.

I think windows will automatically continue to increase the swapfile size over time as well which the Steam Deck will not do.

Let me know the findings on the desktop because it has me curious.

[StripedMonkey]

I did not manage to do much in the way of debugging on the SD side of things, but I did spend ~3h this weekend playing Palworld on my desktop. During this session, I fought the penking, chillet, bushi, katress, whatever that lightning horse is, went into 4-5 separate dungeons (with a few dumb deaths that required re-entering the dungeons, this game really needs better armor integrity). Additionally, I found ~30-40 lifmonk statues as a ballpark guesstimate for how much of the map I've covered. The game, by the end of the play session, consumed 14GB of System Memory.

Initially, the game takes 6GB of memory starting at base. Entering the Penking dungeon tips it to 6.3GB of memory Entering the Katress dungeon didn't change the memory usage significantly Entering the Bushi dungeon upped it to 7GB Entering the dungeon by the Syndicate tower upped it to 9GB Exiting the dungeon by the syndicate tower dropped it to 8GB After this point, I mostly stopped paying attention to the numbers.

These numbers are not representative of 1:1 Steam deck settings, as I'm playing with maxed settings, and was doing lots of other things at the same time which could have influenced overall system usage.

tl;dr, while these numbers could to indicate a memory leak, it does not seem dramatic enough for the "enter a dungeon and immediately freeze" that I've experienced on a fresh restart of the entire steam deck. It also seems plausible that it's only an issue with not freeing assets after being loaded from disk, instead of a true "leak". Notably, VRAM usage does not change significantly here at all. It peaks upon loading a new area, but quickly goes down so it's almost certainly not a vram issue itself.

[KrisCris]

The latest Palworld client running under Proton can no longer connect to any dedicated multiplayer server, just timed out.

[Maxence1502]

I confirm it's no longer working since the latest Palworld update

[simifor]

@KrisCris @Maxence1502 I am seeing the same with proton stable, but proton 9.0 beta lets me connect. Have you tried with that version?

[KrisCris]

@KrisCris @Maxence1502 I am seeing the same with proton stable, but proton 9.0 beta lets me connect. Have you tried with that version?

I've tried Proton Experiment, Proton 9.0 (Beta), and Proton GE 9-2, but non of them worked for me.

[simifor]

@KrisCris upon further testing, proton 8 can also connect to servers, but there are some servers that will time out every time in every configuration I tested, including windows. So I think it's likely that, at least the ones I encountered on my testing, are a server side issue and not proton side.

[jbdevic]

@KrisCris upon further testing, proton 8 can also connect to servers, but there are some servers that will time out every time in every configuration I tested, including windows. So I think it's likely that, at least the ones I encountered on my testing, are a server side issue and not proton side.

I had already tried it on Proton 8 (not working) with a new server, I'm surprised it worked for you

[matze19999]

I have two steam decks here, the first one connects to my dedicated server, the second one won't connect. I haven't figured out yet why it is like that

[simifor]

Could you add "PROTON_LOG=1 %command%" to the launch parameter of both steam decks, try to connect to the server, and then upload the resulting file? It'll create a file in your home folder called steam-1623730.log

El lun, 15 abr 2024 a la(s) 3:11 p.m., Matthias Pröll ( @.***) escribió:

I have two steam decks here, the first one connects to my dedicated server, the second one won't connect. I haven't figured out yet why it is like that

— Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/7448#issuecomment-2057622321, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQZQ4EFQ4I6QOQDWYFOEBOTY5QQ7ZAVCNFSM6AAAAABCNL5XLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJXGYZDEMZSGE . You are receiving this because you commented.Message ID: @.***>

[matze19999]

Could you add "PROTON_LOG=1 %command%" to the launch parameter of both steam decks, try to connect to the server, and then upload the resulting file? It'll create a file in your home folder called steam-1623730.log

No problem, here it is:

steam-1623730_connection_successful.log steam-1623730_no_connection.log

[alicx1]

I can confirm that palworld servers dont work when using proton. this is a project that used to work but now no more: https://github.com/Dekita/palhub-server (it may help you to debug)

[TAGamer-Ferreira]

wine without proton works

[simifor]

@matze19999 Sorry to ask for new logs, but could you run the game with these options instead PROTON_LOG=+winhttp,+wininet,+winsock,+secur32,+crypt,+bcrypt,+dnsapi,+steamclient,+cryptnet %command%. Make sure to not cut the log, if it gets too big, just compress it, even zip should greatly reduce its file size.

[alicx1]

wine without proton works

@BG-Ferreira do you have any link to repo of someone who already did this please?

[TAGamer-Ferreira]

@alicx1 I used this one before i made an pyterodacly egg that works docker-palworld-dedicated-server-wine

[matze19999]

@matze19999 Sorry to ask for new logs, but could you run the game with these options instead PROTON_LOG=+winhttp,+wininet,+winsock,+secur32,+crypt,+bcrypt,+dnsapi,+steamclient,+cryptnet %command%. Make sure to not cut the log, if it gets too big, just compress it, even zip should greatly reduce its file size.

Here are the logs:

steam-1623730_working.log steam-1623730-not_working.log

[simifor]

@matze19999 I think in this scenario it would help for me to try and connect directly to yor server to try and see what can be found. If you're ok with it, provide details so that I can find it.

[matze19999]

@matze19999 I think in this scenario it would help for me to try and connect directly to yor server to try and see what can be found. If you're ok with it, provide details so that I can find it.

This is a server in a private lan with no access from outsite. But this happens to all servers, also for public server.