I had it attached to a kb+mouse and screen and was using it as a PC. I couldn’t be arsed to return back to gaming mode, only to have to then switch back again.
I mean, it kinda is a deck problem, in that it affects the steam deck’s capabilities as a gaming device.Apparently I misunderstood, I thought it was a proton issue where it’s just Palworld leaking memory? If you know what you’re doing you might be able to fix that issue, but for most users it ends on “this game doesn’t work on the steam deck”.
That said, I do believe valve (and all the other contributors to wine, dxvk, etc.) are doing work to make more games work on Linux, and they’ve done an amazing job so far
No. It’s not a Proton issue or a Steam deck issue or a Linux issue. Palworld has a fundamental flaw on how it handling memory and asking for infinite ram. So it doesn’t matter what OS or what manufacturer made because all the devices have finite amount of ram and if you keep asking infinite ram, they will crash when they are out of memory to give.
And I don’t think palworld having memory issue will portray steam deck in negative light when the user comes to know it’s a game bug and not the device or its software bug.
Don’t get me wrong, I know, I might not have been clear enough.
I do not think Palworld reflects negatively on steam deck - I was originally wrong, I didn’t check what I was talking about, and edited my comment after I read your reply.
What I meant is, in cases where proton does fail, it does reflect negatively on the steam deck. It’s not a statement of fact, and no longer relevant to the original message, but I was upholding that opinion from my original comment.
I love my deck. I wish palworld didn’t crash on it but thats not a deck problem.
Does Proton GE help? I played multiple 6-hour sessions through desktop mode and haven’t had a single crash.
I’ve not tried that but I will! Thank you.
Why desktop mode?
I had it attached to a kb+mouse and screen and was using it as a PC. I couldn’t be arsed to return back to gaming mode, only to have to then switch back again.
You’re hosting a multiplayer game?
I wasn’t the host, but it was a multiplayer game
The memory leak only affects the host.
In 10 hours i had not a single crash, i’m on stable with standard Proton
Cool.
I mean, it kinda is a deck problem, in that it affects the steam deck’s capabilities as a gaming device.Apparently I misunderstood, I thought it was a proton issue where it’s just Palworld leaking memory? If you know what you’re doing you might be able to fix that issue, but for most users it ends on “this game doesn’t work on the steam deck”.That said, I do believe valve (and all the other contributors to wine, dxvk, etc.) are doing work to make more games work on Linux, and they’ve done an amazing job so far
It’s not a steam deck problem, if palworld keeps leaking memory. I have seen that issue in my steam deck, laptop and on my friends dedicated server.
Ah, sorry - I saw mentions that Proton-GE fixes it in another reply, thought it was something else.
My statement does stand in general, any issues with Proton will reflect negatively on the deck - but I definitely spoke too soon here
No. It’s not a Proton issue or a Steam deck issue or a Linux issue. Palworld has a fundamental flaw on how it handling memory and asking for infinite ram. So it doesn’t matter what OS or what manufacturer made because all the devices have finite amount of ram and if you keep asking infinite ram, they will crash when they are out of memory to give.
And I don’t think palworld having memory issue will portray steam deck in negative light when the user comes to know it’s a game bug and not the device or its software bug.
Don’t get me wrong, I know, I might not have been clear enough.
I do not think Palworld reflects negatively on steam deck - I was originally wrong, I didn’t check what I was talking about, and edited my comment after I read your reply.
What I meant is, in cases where proton does fail, it does reflect negatively on the steam deck. It’s not a statement of fact, and no longer relevant to the original message, but I was upholding that opinion from my original comment.