I just tried loading in using AMDVLK instead of libvulkan_radeon. That fixes the water but causes the shadows in game to become blocky and also comes with a big performance hit. I also tried the AMDGPU-PRO-Vulkan and so far that was the worst out of them all.

llvm and aco both have the same issue. llvm just seems to add stutter.

Can you upload a screenshot of the problem? Can you also record a capture with renderdoc please?

Did you do anything to avoid the "DX11 feature level 10.0 is required to run the engine" popup message?

I never got a error message or did any workarounds. The game just works, apart from battleye.

DXVK with Mesa

Windows 10

renderdoc
https://mega.nz/#!eBxUSA4L!ZMDxaSINTSSbKX9p5Wys-hWVrjytyuXZne8lUeMASGE

Can you upload your savegame please?

Heres my entire Save Directory containing my Settings and a fresh valguero map (mods / workshop content was disabled) with it saved at that location. I play on unofficial servers.
Saved.tar.gz

Where should I put this Saved directory ?

Everything is functional at gold level (minor graphic artifacts) except BattlEye (which is a separate bug). Should we link the BattlEye bug?

I've noticed some blockey artifacts on distant objects. It seems related to truesky as when I turn the sky quality to off it goes away. Should I file a separate bug report for this?

Here is my system info.

https://gist.github.com/Ruedii/79c6e6b7b668bbf598b1b8b8e69483f0

As a note, cloning over the Linux quirks profile for ARK in .drirc drastically reduced the artifacts in question from substantial artifacts all along the edges of objects to tiny artifacts on a very small number of object edges.

The quirk in question is "Clear DB Cache before fast depth clear"

They are definitely truesky related as they don't occur at all with truesky off. I am suspecting the particle cloud effects between depth layers. (That effect is so pretty too.)

@hakzsam, It goes in the ARK ShooterGame Folder eg. steamapps/common/ARK/ShooterGame/Saved/

I haven't personally noticed any artifacts on my particular setup using the Proton version, The linux version however is full of them along with random texture loss, random crashes, and Graphics that haven't been updated since early access.

Yes. I think I could tell. The Linux version has barely functioning
graphics.

I have not experienced the water bug myself. Do people know what map it is
on?

Valguero has missing water in some places, The custom map olympus has no water. Water issue occurs using RADV and seems to be the only issue, AMDVLK the water is present but there is blocky lighting and shadows. AMDVLK also has constant stuttering and FPS drops along with its blocky shadows and lighting.

I see protondb reports for ARK with people using other AMD Cards without issues, my issue may be related to NAVI.

@Nayr438 Can you please pull your Mesa repo? I wonder if https://gitlab.freedesktop.org/mesa/mesa/commit/f3cccd05d9f6e9d05c18d1a3a5f9eb863e4f264b fixes the water issue for you.

@hakzsam The water issue is fixed.

What driver version and proton version are you using?

Also what card?

I have experienced no such issues and I am using RADV under latest Mesa
version with an Rx480. I have used both Proton 4.9 and 4.11.

Keep in mind this game defaults to a very broken Linux port. That sounds
like an issue more typical of that Linux port, or an old Mesa version. (There was a mesa version that fixed this issue.)

Valguero has missing water in some places, The custom map olympus has no
water. Water issue occurs using RADV and seems to be the only issue, AMDVLK
the water is present but there is blocky lighting and shadows. AMDVLK also
has constant stuttering and FPS drops along with its blocky shadows and
lighting.

GPU: AMD Radeon 5700 XT (NAVI10)
Driver/LLVM version: 4.5 Mesa 20.0.0-devel (git-525cbe85ef) LLVM 10.0.0
Kernel version: 5.4.6-15linux-tkg-pds-zen2
System Information Gist: https://gist.github.com/Nayr438/7edd0775c30dc932ed0e6bb8a31259d6
Proton version: 4.11-11
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.6 GiB of RAM

If I use the standard kernels available in Manjaro or Arch 5.3 - 5.5 ARK gives a out of memory error. I thought it was a hardware error since memtest detected a fault. I have since fixed this and the error still occurs. The error does seem to go away when using this custom build of the kernel I found in the Chaotic-AUR linux-tkg-pds-zen2 5.4.6-15 ( https://github.com/Tk-Glitch/PKGBUILDS/tree/master/linux54-tkg ). Using latest Mesa-Git and llvm-git from the Chaotic-AUR, it gets updated like twice a day so I assume its recent. When using linux-tkg-pds-zen2, I do occasionally get a random drop in frames, and it seems to stay low for a couple minutes, then fixes itself. The highest ARK has reached on System memory is 10GB out of 16GB. The crash happens randomly. Sometimes as soon as i load into the main menu, join a server, or start moving around in a map. switching between ACO and LLVM makes no difference and switching proton versions make no difference. I can reproduce this result on Ubuntu, Arch, and Manjaro. This also occurs on both mesa-git with llvm-git, and the standard mesa with llvm that is shipped in the distributions packages.

steam-346110.log

Ran out of memory allocating 1736704 bytes with alignment 0

Anyone else having a problem where the first time you hit Alt, it shows up as NumLock in the game? Numlock on the keyboard isn't actually triggered, the game just interprets it as such the first time. Subsequent presses work. However, if you alt-tab out of the game and come back you have to hit alt twice for it to work. It's slightly annoying since i use it for orbiting the camera and the first time doesn't work.

EDIT: After testing some more, it appears the problem only happens when numlock is turned on.

To test, load up the game, go to the keyboard rebind options menu, click any action then hit alt (left or right). The first time it detects it as NumLock. If you do it again it'll show up correctly as alt.

System info:
Arch w/ XFCE 4.14.
https://gist.github.com/jazztickets/f07f40cf0896a257b911325fc21f5e1a

I don't have Alt set for any special function in the desktop, and it was working fine in the native linux version of ARK.

Already Mentioned - Mesa. :) (git master with commit hash with ACO enabled - but amdvlk has the same result).

Do you still experiment issues with RADV?

Do you still experiment issues with RADV?

No, everything has been working wonderfully going on several months. Both the original texture issue and memory issues have been resolved and any patches that it depended on in the past have landed into stable. The only issue remaining with the game is it's use of Battleye, which is only a concern if you want to join any Official Servers.

yes. still doesn't work for some bizarre reason when connecting to a server - but local single player works. it's something in the load sequence that ends up with things falling over. it's a pain to debug without source and with a complex launching scenario of emulated windows binaries... :(

What's the Battleye issue?

What's the Battleye issue?

For the Windows build of the game, Battleye AntiCheat is still unsupported, it just fails to load.

Ah ok, so this is totally unrelated the driver, thanks!

yes. still doesn't work for some bizarre reason when connecting to a server - but local single player works. it's something in the load sequence that ends up with things falling over. it's a pain to debug without source and with a complex launching scenario of emulated windows binaries... :(

I haven't experienced this issue. All maps going up through Genesis load in fine for both Single Player and Server Instances. I recently just played on a Server using the Crystal Isles Map along with a couple dozen mods.

Spun Ark up on proton in my ubuntu 20.04 setup, and noticed trying to load my own single player map with primitive+ will result in the game crashing when the map is about to finish loading. Tried this with both Ragnorak map and "the Center" map. running steam in the foreground of the terminal isnt showing any unique errors at time of failure.

Spun Ark up on proton in my ubuntu 20.04 setup, and noticed trying to load my own single player map with primitive+ will result in the game crashing when the map is about to finish loading. Tried this with both Ragnorak map and "the Center" map. running steam in the foreground of the terminal isnt showing any unique errors at time of failure.

I would try verifying your files as I can't reproduce this. Primitive+ Loads fine on my end.

@Nayr438 yeah I had uninstalled and reinstalled to get the game to work. However, its happening again, so I am going forward with the verifying files as you suggested.

I did find an error log that coincides repeatedly with the failure, was googling around to see if the internet knows how to resolve it but most of the top results are showing the error for trying to connect to multiplayer servers.

ark_error.txt

If this has already been resolved, I'd love a link outlining the solution ;)

I'm not sure that verifying will help. I've verified so many times it's not amusing anymore and never once was the game corrupt. I'm sure I have eaten up terabytes of bandwidth uninstalling and re-installing. It just has bugs - and definitely under proton. :( The hard bit is trying to debug it.

So setup a dedicated server for some friends and I to play on. We've noticed that every time we play the game, the next time we try to jump on we have to verify our entire ark game on our clients and there are always two files corrupted consistently.

does anyone know how to get steam verify to output the files it found corrupted? because backing them up myself would be faster than an hour long verify.

So being in the Steam's Ark directory I can run this, to output the 5 most recently modified files. So hopefully after Steam Verify it will clearly show which files were modified.

$ find . -type f -printf '%T@ %p\n' | sort -k1,1nr | head -5
./ShooterGame/Saved/Config/WindowsNoEditor/Engine.ini
./ShooterGame/Saved/Logs/Dump1112821648.dmp
./ShooterGame/Binaries/Win64/officialserverstatus.ini
./ShooterGame/Binaries/Win64/officialservers.ini
./ShooterGame/Saved/Config/WindowsNoEditor/GameUserSettings.ini

If that works then I would like to write a small script to backup and replace those files. Obviously, the .dmp file can be ignored but the engine and binary files strike me as what could be getting corrupted?

I can't even get the game to launch past the mini splash screen after asking to install battle-eye. Getting a crash error like the image below.

steam-346110.log

oh god no.. don't use battleye!!! avoid it. it's broken on linux+proton. the game will work without it BUT you cannot join official servers. you have to use unofficial ones that have disabled battleye. I run one of these just for this reason. :) I do wish battleye would work and wine/proton would somehow fake/emulate enough to allow it. :) But that's a different problem.

Just FYI - I am using proton + ark on a 6800xt and it actually all works fine now... except battleye.

oh god no.. don't use battleye!!! avoid it. it's broken on linux+proton. the game will work without it BUT you cannot join official servers. you have to use unofficial ones that have disabled battleye. I run one of these just for this reason. :) I do wish battleye would work and wine/proton would somehow fake/emulate enough to allow it. :) But that's a different problem.

Just FYI - I am using proton + ark on a 6800xt and it actually all works fine now... except battleye.

Oh I hit uninstall battle-eye it didn't fix it. Should I reinstall?

Maybe... :)

with the new update I can no longer move. Character isn't stuck just doesnt attempt to move also using proton 6.3-4
steam-346110.log

I can't reproduce that issue on the Proton Experimental that you are using.
I also can't reproduce it on Proton 6.3-5 or Proton-GE(Latest)

Have you tried verifying your Game Files from within Steam?

Replying to https://github.com/ValveSoftware/Proton/issues/3218#issuecomment-887478194

Yes multiple times, I've also tried to call reinstall it.
Do you have an Nvidia card as well?

Replying to https://github.com/ValveSoftware/Proton/issues/3218#issuecomment-887543197

Unfortunately I do not, so it's possible that it's NVIDIA Driver related.

Replying to https://github.com/ValveSoftware/Proton/issues/3218#issuecomment-887548676

Yes that's what I think it is, however it's somewhat the games fault as older driver versions don't fix the problem

I could play the game fine yesterday (after doing nothing).
Since then I left everything unchanged and it crashes again (only thing I did was reboot, no packages were updated or modified), since then I tried reinstalling the game, switch proton versions (tried experimental, 6.3-5, most GE versions) and nothing worked.

This is really weird, I'm not sure if the issue is on my end, can someone with an nvidia card try the game and share their system information?

Replying to https://github.com/ValveSoftware/Proton/issues/3218#issuecomment-888237981

Okay I could make this pretty reproducible now, installing the game on linux yields said problem, if you however install the game on windows or only Verify the Game files from windows the problem is solved. However it seems to come back after a reboot.

Useful to note may be that I have the game on an ntfs drive, I will install it on an ext4 drive later and check if the issue persits then (I doubt that ntfs is the culprit here though)

Using a NTFS partition is known to be problematic with Wine/Proton as well as other various Linux Software, so that could very well be your issue.

Using a NTFS partition is known to be problematic with Wine/Proton as well as other various Linux Software, so that could very well be your issue.

I know that it's a little problematic sometimes but it works on the NTFS drive after verifying the game files from windows, so I'm a little sceptical if it's related to NTFS

forgot to post the log here it is.
steam-346110.log

Hello @blastermaster77, your Proton log has lines similar to [#5238 (comment)](https://github.com/ValveSoftware/Proton/issues/5238#issuecomment-948850346). Like that comment, can you completely close Steam, then run steam-runtime from a terminal and check if Proton gives a hint when running the game?

here is the output of the terminal by running steam-runtime and launching ark.
https://gist.github.com/blastermaster77/46858ea57cc671241e10c512b4c83dc6

Thanks for checking. I suspect that the game's wineprefix (~/.local/share/Steam/steamapps/compatdata/346110) is damaged or incomplete, but your terminal log looks healthy, so it's not clear why that has happened.

UPDATE: I installed steam from flatpak and now it works, with steam-manjaro it does not, I dont know why. Any ideas?

runs with proton 6.21-GE-1, but i feel like it runs slow.

I seem to be having the same issue as blastermaster77, using proton experimental to run ark
here are relevant logs:
https://gist.github.com/Trinsdar/6dabe6729ca85c0e5ba5176bcb35a11b
https://gist.github.com/Trinsdar/8f57fe672f15a316247ccf355504716b

I fixed it by deleting the compatdata folder for the game and now it works.

On Fri, Dec 24, 2021, 6:30 PM Trinsdar @.***> wrote:

I seem to be having the same issue as blastermaster77, using proton
experimental to run ark
here are relevant logs:
https://gist.github.com/Trinsdar/6dabe6729ca85c0e5ba5176bcb35a11b
https://gist.github.com/Trinsdar/8f57fe672f15a316247ccf355504716b

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3218#issuecomment-1000941513,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACHAHPUUBKEG3I7IBGQ5OIDUSTYB5ANCNFSM4JMWQLCQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID:
@.***>

ARK: Survival Evolved is for linux. No proton required anymore.

unless something has changed we still use proton for Ark despite it being "native" to Linux because the proton version performs better.

@debian-user-france1 Yes - there is a native Linux ARK port. It has problems. Using the Proton one is just better.

1. Wildcard will update the Windows client, update official servers then lock out Linux and Mac users for hours, days or even weeks. Since the clients on these platforms sometimes take that long to update... it becomes impossible to play. You are locked out for weeks - your dinos on the server end up starving or Your generators run out of Gas if you did not have them 100% stocked up etc.
2. Ground clutter is broken on Linux - the map is much more bare without it and the whole look suffers. With Proton ground clutter works and things like much better.

Yes, these are 2 bad things. But since I have my own dedicated server this isn't a problem and the ground bug isn't that annoying. I didn't know that people use proton anyways because I have bad experiences (instability) with wine. I guess my dedicated server that runs without wine will be behind too? So the epic Games version will get updates faster (I don't have Windows anymore so no epic games ARK anymore)?

Not sure when it happened but BattlEye works now, which leaves no remaining issues for the game.

Whitelist Request

• Name of the game to be whitelisted: ARK: Survival Evolved
• Steam AppID of the game: 346110

System Information

• GPU: AMD Radeon 5700 XT (NAVI10)
• Driver/LLVM version: 4.6 (Compatibility Profile) Mesa 22.0.0-devel (git-84b21fea46) LLVM 13.0.0-6
• Distro version: Arch Linux
• Link to full system information report: https://gist.github.com/Nayr438/c8944c703b86ac2e3b5527c914b91db7
• Proton version: 6.3-8

I confirm:

that pressing the Play button in the Steam client is sufficient.

Issues

I haven't experienced any issues.

@debian-user-france1 Yes - there is a native Linux ARK port. It has problems. Using the Proton one is just better.

1. Wildcard will update the Windows client, update official servers then lock out Linux and Mac users for hours, days or even weeks. Since the clients on these platforms sometimes take that long to update... it becomes impossible to play. You are locked out for weeks - your dinos on the server end up starving or Your generators run out of Gas if you did not have them 100% stocked up etc.
2. Ground clutter is broken on Linux - the map is much more bare without it and the whole look suffers. With Proton ground clutter works and things like much better.

Oh may I ask this last question in this issue?

Well. I went to the north (at a hill with snow) and the hill had many places without snow and a texture-not-found texture like the developers forgot to ads some snow textues. Also happens when looking from far away: the mountains has places that aren't white and if you look from like the mountain next to a snow Mountain on The Island.

I'm trying it with proton now. Scared that I've lost everything but made a backup of game.
Can this issue be related to the issues that come with the Linux Build?

Can this issue be related to the issues that come with the Linux Build?

The Linux Build of the Game is minimally maintained and is fairly unstable. The Linux Build still uses the old Render, if you take the Windows build of Ark and set it to the old renderer and put it on the lowest possible settings, that's basically the Linux Build at Max settings. The Rain, if it's working, often causes a rainbow artifact effect on everything. Textures are often missing. Game usually crashes after a few hours. During updates it tends to be left in the dark, where you end up waiting hours to months for a update to bring it back up to date, which I have seen on several occasions just leave Ark in a completely unplayable state until the next update. If you plan to use workshop content, that's also a whole other mess of compatibility issues.

The recommended way to play Ark on Linux is through Proton and if you want to host a server use a Windows Machine or start up a Virtualized Windows Instance. If you decide to switch to the Windows build be sure to completely uninstall it and remove its game folder (Example Dir: "~/.steam/steam/steamapps/common/ARK/" ) from the steamapps directory, anyone who I have seen switch from the Linux build to the Windows build has had problems when this wasn't done.

Thank you so much for that! I always thought that these idk white glowy things that open appear near water are because of christmas or so but it seems to be a render-bug. Maybe I can afford enough money to get a better processor, but buying server already. Thank you! I'll take a look at the performance of Proton with ARK - Satusfactory worked pretty well but since U5 it's laggy (not sure why but prob. because it wont switch to vulcan shader or so). Since ARK has a Vulcan shader I have hope of a lag-free Gaming experience. The Linux Files are 88GB and the Windows ones 125GB...

Oh Primal Game Data needed litteraly 15mins to load on Linux Version. Seems to be faster now with Proton.

Can I let my dedicated Server run with Proton? How can I?

@debian-user-france1 yes - that lack of snow is also a ground clutter problem. happens in the desert on ragnarok too - its all brown rock rather than yellow sand etc. - all in all the linux port has broken rendering/features where windows version running with proton is fully functional in these areas. there is also the "wildcard doesn't update the linux port" problem too to just make it so much worse.

I run a dedicated linux vm with steam + ark on it (i disabled battleye requirements because of proton + battleye) 51.15.11.63 is the server address (add it manually in steam's servers gui dialog then you can join it). it seems the linux SERVER doesn't have issues and gets updated reasonably and works. i've been running this for about a year now. it's running lost island now. it's set to pvp + orp so it's hopefully less toxic. :)

Yes, Linux Dedicated Servers seem to work. The devs only made some exception handling to the protocol and don't add any texture anymore. That's why also the Christmas thing that hits the ground all the time doesn't appear anymore client sided but the server knows that it exists and spawns it. But how can I use proton with my dedicated server? Do I have to launch the Windows start file with wine?

i have no idea how you use proton for the dedicated server... but the linux native ark works fine on the server-side - its just client-side where you probably want to use proton.

Thats correct. You can use Linux side server + mods, and then on the client side you use proton. Proton's main benefit is graphical stability. The server isn't responsible for graphics rendering, so no need to invent a proton headless mode.

Just switched to window native run through proton on client side after discovering Linux native is terrible. Using NVIDIA from nvidia-driver-510 on Ubuntu Jammy Jellyfish release. Proton Experimental.

Game works great on medium graphic settings, especially with no camera shake or bob. One issue: Ark seems to be launching in No Sky launch setting regardless of which launch setting I choose. Wondering if there's a specific launch option in properties I should be using or something going on with the graphics driver. The sky is completely black.

EDIT: Found a thread on the steam community from 2015 discussing a similar problem on Windows 10 OS:
https://steamcommunity.com/app/346110/discussions/0/615086038661431873/?ctp=2

It sounds like a VCredist issue, which makes sense because each time I launch, I get a popup saying "Installing Microsoft VC redist [etc]"

GE-Proton7-19 resolves the issue and the sky appears normally. I'm not sure what changes between experimental and GE but it seemed to fix whatever was wrong with those files.

Hello, I just today installed Ark and wanted to play with my friend. However, I can somehow not connect to the server he is playing on. The progress bar in the loading screen keeps resetting itself, tho I don't know if that is related. I am using Proton Next, I have the AntiCheat Proton Version installed and my system information: https://gist.github.com/Windgott1910/d1baca0948fbd2bc0379406ae64b6232 The system keeps saying that there is already a player with my account connected (1 Player on the server, my friend) or that the game is already authenticating.

hello, nothing works, the game don't launch with all other proton 7, experimental or GE

Experiencing issues with starting ark.

Compatibility Report

• Name of the game with compatibility issues:
• Steam AppID of the game:

System Information

• GPU: AMD Radeon RX 7900 XT (gfx1100, LLVM 15.0.7, DRM 3.51, 5.15.0-91-generic)
• Video driver version: Mesa 23.1.0-devel
• Kernel version: 5.15.0-91-generic
• Link to full system information report as Gist:
• Proton version: 8.0 and experimental

Adding PROTON_LOG=1 %command% does not generate a log file.

Symptoms

States that ark is "Launching" or "Running" but nothing is shown. Sometimes audio starts.

https://gist.github.com/schrummy14/17cbafcedbcba9e8feebbfccbd7d4dd0

@kisak-valve , would you be able to tell me how to force mesa/radv?

@kisak-valve
Found the flag: AMD_VULKAN_ICD=RADV

Game never launches. Steam client says launching.

stdout from running the steam command:

steam.sh[4322]: Running Steam on ubuntu 20.04 64-bit
steam.sh[4322]: STEAM_RUNTIME is enabled automatically
setup.sh[5068]: Steam runtime environment up-to-date!
steam.sh[4322]: Steam client's requirements are satisfied
[2023-12-13 16:55:07] Startup - updater built Dec  8 2023 00:32:59
[2023-12-13 16:55:07] Startup - Steam Client launched with: '/home/mschramm/.local/share/Steam/ubuntu12_32/steam'
12/13 16:55:07 Init: Installing breakpad exception handler for appid(steam)/version(1702079146)/tid(5320)
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[2023-12-13 16:55:07] Loading cached metrics from disk (/home/mschramm/.local/share/Steam/package/steam_client_metrics.bin)
[2023-12-13 16:55:07] Using the following download hosts for Public, Realm steamglobal
[2023-12-13 16:55:07] 1. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 1000, source = 'update_hosts_cached.vdf'
[2023-12-13 16:55:07] 2. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'update_hosts_cached.vdf'
[2023-12-13 16:55:07] 3. https://cdn.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2023-12-13 16:55:07] Checking for update on startup
[2023-12-13 16:55:07] Checking for available updates...
[2023-12-13 16:55:07] Downloading manifest: https://client-update.akamai.steamstatic.com/steam_client_ubuntu12
[2023-12-13 16:55:07] Manifest download: send request
[2023-12-13 16:55:07] Manifest download: waiting for download to finish
[2023-12-13 16:55:08] Manifest download: finished
[2023-12-13 16:55:08] Download skipped: /steam_client_ubuntu12 version 1702079146, installed version 1702079146, existing pending version 0
[2023-12-13 16:55:08] Nothing to do
[2023-12-13 16:55:08] Verifying installation...
[2023-12-13 16:55:08] Performing checksum verification of executable files
[2023-12-13 16:55:08] Verification complete

Steam logging initialized: directory: /home/mschramm/.local/share/Steam/logs

XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xee81b910
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xee81a140
/usr/share/themes/Yaru-dark/gtk-2.0/main.rc:775: error: unexpected identifier 'direction', expected character '}'
/usr/share/themes/Yaru-dark/gtk-2.0/hacks.rc:28: error: invalid string constant "normal_entry", expected valid string constant
steamwebhelper.sh[5480]: Runtime for steamwebhelper: defaulting to /home/mschramm/.local/share/Steam/ubuntu12_64/steam-runtime-heavy
steamwebhelper.sh[5480]: Using CEF sandbox (try with -no-cef-sandbox if this fails)
CAppInfoCacheReadFromDiskThread took 23 milliseconds to initialize
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 5660
bus_name=com.steampowered.PressureVessel.LaunchAlongsideSteam
ac_compute_device_uuid's output is based on invalid pci bus info.
BRefreshApplicationsInLibrary 1: 1ms
BuildCompleteAppOverviewChange: 236 apps
RegisterForAppOverview 1: 9ms
RegisterForAppOverview 2: 9ms
pressure-vessel-wrap[5871]: W: "opt/amdgpu/share/libdrm" is unlikely to appear in "/run/host"
pressure-vessel-wrap[5871]: W: "opt/amdgpu/share/libdrm" is unlikely to appear in "/run/host"
pressure-vessel-wrap[5871]: W: "opt/amdgpu/share/drirc.d" is unlikely to appear in "/run/host"
Proton: Upgrading prefix from 8.0-104 to 8.0-103 (/media/mschramm/SSD/SteamLibrary/steamapps/compatdata/346110/)
Proton: Removing stale builtin /media/mschramm/SSD/SteamLibrary/steamapps/compatdata/346110/pfx//drive_c/windows/system32/ir50_32.dll
Proton: Removing stale builtin /media/mschramm/SSD/SteamLibrary/steamapps/compatdata/346110/pfx//drive_c/windows/syswow64/ir50_32.dll
esync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
ac_compute_device_uuid's output is based on invalid pci bus info.
ac_compute_device_uuid's output is based on invalid pci bus info.
ac_compute_device_uuid's output is based on invalid pci bus info.
ac_compute_device_uuid's output is based on invalid pci bus info.
ac_compute_device_uuid's output is based on invalid pci bus info.
ac_compute_device_uuid's output is based on invalid pci bus info.
ac_compute_device_uuid's output is based on invalid pci bus info.
ac_compute_device_uuid's output is based on invalid pci bus info.
ac_compute_device_uuid's output is based on invalid pci bus info.
ac_compute_device_uuid's output is based on invalid pci bus info.
ac_compute_device_uuid's output is based on invalid pci bus info.
ac_compute_device_uuid's output is based on invalid pci bus info.
ac_compute_device_uuid's output is based on invalid pci bus info.
ac_compute_device_uuid's output is based on invalid pci bus info.
ac_compute_device_uuid's output is based on invalid pci bus info.
ac_compute_device_uuid's output is based on invalid pci bus info.
[2023-12-13 16:57:09] Background update loop checking for update. . .
[2023-12-13 16:57:09] Checking for available updates...
[2023-12-13 16:57:09] Downloading manifest: https://client-update.akamai.steamstatic.com/steam_client_ubuntu12?t=506735928
[2023-12-13 16:57:09] Manifest download: send request
[2023-12-13 16:57:10] Manifest download: waiting for download to finish
[2023-12-13 16:57:10] Manifest download: finished
[2023-12-13 16:57:10] Download skipped by HTTP 304 Not Modified
[2023-12-13 16:57:10] Nothing to do
ac_compute_device_uuid's output is based on invalid pci bus info.
ac_compute_device_uuid's output is based on invalid pci bus info.

I switched over to fedora 39 and things are running much better.
This probably is an issue with the AMD 7900 xt GPU and Ubuntu 20.04 still using kernel 5.x.x.

Hello,

Someone told me that this game 'Ark Survival Evolved' stopped working after the update introducing 'Aquatica DLC'.
So I loaded this game from my library and indeed it is broken. Not only it lags in the menu and it takes ages to load the local solo world, but it simply crashes while doing so.

20250815 - Proton Experimental log - Ark Survival Evolved - Crash on loading local solo world after Aquatica update.

Regards.

Hello,

There is still a bit of lag in the main menu, but the slow loading/crash has been fixed with today (19 Aug) game update to 360.13, for me and the other person.

Regards.

Thank you @kisak-valve

Compatibility Report

• Name of the game with compatibility issues:
  Ark Survival Evolved

• Steam AppID of the game:
  346110

System Information

• GPU: RTX 3080 Ti
• Video driver version: 595.58.03
• Kernel version: 6.19.11-201.nobara.fc43.x86_64
• Link to full system information report as Gist: https://gist.github.com/xIceFox/8b65d15ccf4f6754d4309c13cc663ec6
• Proton version: Tried with Proton 10, Proton-Experimental and Proton-GE

I confirm:

• [ ] 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.

https://gist.github.com/xIceFox/9d790d9aadb92967e46f7d7c85afbca4

Symptoms

When using the radial menu in the game I can't select the buttons. Neither hover over the buttons or clicking does anything. The rest of the game is working flawlessly.
Hovering and using buttons in the normal menu works fine.
The bug makes this game unplayable for me.
I searched the internet already for similar issues, I only found one entry in reddit, but nobody ever answered:
https://www.reddit.com/r/ARK/comments/1nsaj9m/asa_linux_proton_cant_use_radial_menu/ (This was the same bug in Ark Survival Ascended)
I would appreciate support or tips how to debug this, I'm on linux since 2 days and never used proton before.

Reproduction

Start the game, use the radial menu.
Honestly, since I didn't find many people with the problem, this seems to be a very rare edge case.

Update, It is working with proton version <= 9, does somebody know where I can report the bug so it can get fixed in proton?
@kisak-valve

Im trying different versions now to repro the bug:

• Proton 8 works
• Proton 9 works
• Proton 10 breaks
• Proton Experimental breaks
• Proton GE breaks