PlayableShow Details
Unknown
I followed the advice of valkyrie.sys and added VCRUN2022 and d3dcompiler_47 to Palia's Proton prefix. Without this, the game would not start.
Game repeatedly crashes to desktop
unable to start
Set graphics to low and reduced render distance
Controller is not supported (yet) and sometimes buttons did not work correctly
The game is very enjoyable and I am exicted it is finally in open beta on steam. If you liked Free Realms back in the day, play this!
gamemoderun %command% -dx11
Add VCRUN2022 & d3dcompiler_47 to palia's protontricks prefix; If unstable on linux-xanmod kernel, switch to linux-zen kernel
Assets sometimes fail to display when loading new area
Occasional Unreal Engine Crashing
NPCs will sometimes break the overworld textrures and assets; some NPCs will rubbeband across the map or have no animations. Occasionally NPCs will face the wrong direction when the player chats with them. Ocassionally unable to plant or harvest crops.
Game crashes on load if tinkering steps are not completed; at best players are able to access the launcher & login menu. Upon attempting to log in, the game will crash unless tinker steps are followed. The game is still in beta, so it might be bugs on the developers part that they have not entirely smoothed out yet. VCRUN2022, d3dcompiler_47 (added to game's prefix in protontricks) and last 3 latest proton-ge (protonup-qt) are required for launch.
set launch options: gamemoderun %command% -dx11 (game will crash more frequently on dx12, or refuse to launch passed login)
Unable to connect to login servers
Can get to the login screen (past the launcher) just fine, but whenever I try to login with my account credentials, it eventually returns back with a red box above the input fields that say "Unable to connect to login servers". Compatibility settings have nothing checked -- which to me is kind've odd, because it's not listed anywhere (that I can recall) as having Linux native status. I also tried this using Heroic Game Launcher and installing the Epic games store version, and that also yields the same error. However using that launcher and looking at the logs, I see lots of errors stating the following (just a very VERY tiny snippet but the log is kind've flooded with the Failed to read DnsConfig lines):
[1026/132238.951:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. [1026/132242.659:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. LogOnline: Warning: OSS: Async task has hit the limit of attempts [1/1], aborting! LogOnline: Warning: OSS: Async task 'FOnlineAsyncTaskLoginPlatform LocalUserNum: 0 bWasSuccessful: 0' failed in 3.101161 seconds LogHttp: Warning: 000000006ED4CBB0: request was cancelled LogS6Core: Warning: Malformed JWT: Did not contain 3 parts separated by periods [1026/132243.951:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. [1026/132247.659:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. [1026/132248.954:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. [1026/132252.660:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. [1026/132253.956:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. [1026/132257.661:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. [1026/132258.958:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. LogStreaming: Display: 0.001 ms for processing 2 objects in RemoveUnreachableObjects(Queued=0, Async=0). Removed 0 (21033->21033) packages and 0 (32943->32943) public exports. [1026/132302.662:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. [1026/132303.960:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig.
It could be a red-herring but I don't think it is given how many of those errors are present in the log, combined with the JWT error. I did try linking my Steam account (using the Steam version) with the account that my Epic version is using since the Steam version kept warning me that if I skip that step it won't let me do it later. So perhaps this is the issue? I'm pretty sure I have ran Palia before on Linux and perfectly. There was a recent large update, and then a small bug-fix (I think it was a bug-fix) patch like the day after; maybe that was it?
I've seen some places reference checking your DNS settings. I say these "things" because it wasn't clear to me, when reading the posts, whether it was a tool the OP was referring to or a game; I saw posts referencing the Unreal Engine (which I believe that's what Palia is using), but I also saw posts on Microsoft's site which didn't make a lot of sense to me -- unless the assertion yielding the bit: "dns_config_service_win.cc(712)" is referencing line 712 in either the game's source-code or the Unreal Engine. I had assumed the error was from Wine kicking that error out. However, maybe not and instead the reference was the game kicking the error back as a reference to its own source code (like an assertion) or it wsa coming from the Unreal engine?...
It should be noted, I'm using 8.8.8.8 (Google's DNS). As a result, I don't think it's a DNS setting, on my end, that's the issue. If I had to make a very VERY cursory guess (going based on so far what I've seen in the log), my guess would be the DNS error is the ripple affect of the JWT token failing for authentication. Perhaps upon successful authentication, the Palia login server returns back a hostname (as part a DnsConfig package) of the game server and because the authentication is failing, the game client tried to look up the hostname, but because the hostname is never replied back (due to the faulty authentication and never being sent a DnsConfig package), the code that attempts to open the returned data (that would then go on to resolve the hostname) fails and so the error is not necessarily in error (in that it IS true that it would have failed to read the package, but only because it doesn't exist because it was never sent because the auth failed) but it's not detailed enough. I'll probably look through my logs and do some deeper analysis since my friends play and I'd like to play with them but so far I don't have any other information.
Certain actions like sprinting, jumping or chopping wood cause the audio to crackle and stutter.
Certain actions like sprinting, jumping or chopping wood cause the game to stutter around 10 fps for about a second until it's fine again.
Depending on what's up with Proton Experimental and the current game version, I have to switch around the Proton versions until I find one where the menu doesn't freeze and only seems to react when I tab out. But once I find a fitting version, it works just fine.
Runs better than on Windows. Less heat generated, no stutter, no lag, no FPS drop. Works flawlessly even at 144hz
gamemoderun %command%
Running on latest GE Proton improves FPS and allows 144hz
__GL_SHARPEN_ENABLE=1 __GL_SHARPEN_AMOUNT=0.7 mangohud %command%
With Antialiasing Off or FXAA the textures flicker and look kinda bad.
If you have an Nvidia GPU I recommend using TAA (this makes the game look way too blurry imo).
Using Nvidia sharpening counter balances this.
Makes the game look perfect in my opinion.
mangohud gamemoderun %command%
works fine online, no latency problems or anything like that.
The game runs very well, without any performance problems, it looks like a native port :)
Luego de probar algunas cosillas, pude jugarlo (Y va sin problemas desde steam). SI experimentas errores con "c++". usa "protontricks "
Used this script with wine GE 8-13 specifically as that's what the script was made for - other versions did NOT work. https://lutris.net/games/install/37660/view
I could not get the steam version to work with multiple version of proton, ge proton, etc. I also tried lutris with multiple versions of runners and it didn't work except for the script linked with wine ge 8-13. Works great then though!
gamemoderun %command%
Had to install vcrun2022
Flickering and weird UI behavior in launcher
Need to add
[/script/engine.renderersettings]
r.GraphicsAdapter=0
to (prefix location)/home/gnare/Games/Heroic/Prefixes/Palia/pfx/drive_c/users/steamuser/AppData/Local/Palia/Saved/Config/WindowsClient/Engine.ini in order to get the game to run on multi-GPU systems.
Flickering in launcher
Need to add
[/script/engine.renderersettings]
r.GraphicsAdapter=0
to
//home/gnare/Games/Heroic/Prefixes/Palia/pfx/drive_c/users/steamuser/AppData/Local/Palia/Saved/Config/WindowsClient/Engine.ini in order to get the game to run on multi-GPU systems.
Game selects wrong GPU on multi-GPU (PRIME) system.
Changed the following configuration file: pfx/drive_c/users/steamuser/AppData/Local/Palia/Saved/Config/WindowsClient/Engine.ini
Added the following lines at the end:
[/script/engine.renderersettings]
r.GraphicsAdapter=0
Game selected integrated GPU by default, solved by modifying game configs manually.
One day I was unable to find any stone... stone was there and I could mine it but I was unable to see the stone. It is a known bug for the steam deck.
small
controller sipport not finished
None
Controller in beta not screens work yet
60fps med settings
Runs great!
No problems here
mangohud %command%
Game is locked at 60 FPS, mangohud reports VKD3D instead of DXVK Black screen at startup. FIX: change FOV to >60, switch to DirectX 11.
At a minimum a new player needs to adjust the in-game settings for FOV and DirectX.
Have not experience any issues at all, running it with Proton experimental
600Mhz GPU frequency and TDP 5W
the game sometimes makes it necessary to use the SteamDeck touchscreen due to the controller not working in certain menus
Black screen instead of rendered game
I'm getting black screen, but in kind of uniuqe way. The game renders character customization and cutscene in the beginning totally fine, but right after this cutscene I only get black screen and UI on it. I've tested it on Arch (with hyprland) and on Mint and It doesn't work on both. And, not surprisingly, it works on Windows.
Gamepad works, Mouse+Keyboard unusable in current state
Mouse hits screen borders in both windowed and fullscreen on KDE Plasma Wayland, worked fine in the past.
