This happens due to https://github.com/ValveSoftware/Proton/issues/1786
Arkham Knight depends on the .Net Framework.

I'm getting the following error, I don't know if it's .net framework, I can't understand.
Here is the full log: https://gist.github.com/sceglimilano/dc104cb62fe8aea00b558b1243cbd3ee

Here is the version cleaned of all the various ERROR: ld.so: object '/home/lvg0/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
https://gist.github.com/sceglimilano/326c7e2f32da9a363230bf59751f81b4
NOTE: I did the clean up as that error is meaningless and unharmful in this case, it has nothing to to with game not launching.

I'm getting the following error, I don't know if it's .net framework, I can't understand.
Here is the full log: https://gist.github.com/sceglimilano/dc104cb62fe8aea00b558b1243cbd3ee

Here is the version cleaned of all the various ERROR: ld.so: object '/home/lvg0/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
https://gist.github.com/sceglimilano/326c7e2f32da9a363230bf59751f81b4
NOTE: I did the clean up as that error is meaningless and unharmful in this case, it has nothing to to with game not launching.

Its #18

Is there a known workaround for this? I'm currently unable to get the game to run using the usual trick of setting the Windows version to XP and even the full install guide for installing .NET makes no difference.

I don't own the game BUT I did get Arkham Asylum working by copying over the prefix from Arkham City, perhaps it would work for Arkham Knight as well? Worth a try at least.

It doesn't work, I tried. I suspect that Arkham Knight needs a newer version of .NET than the one installed by Arkham City.

It doesn't work, I tried. I suspect that Arkham Knight needs a newer version of .NET than the one installed by Arkham City.

I've had some luck with .NET by downloading the 64bit installer for the version I need direct from Microsoft & using Taskmngr through Protontricks/Winetricks to install it. When it starts up choose repair.

It works by using Lutris. I remember I have watched a guy on youtube, he achieved the best performance I have ever seen, even the DXVK developer was shocked by his video (see the comments):
https://www.youtube.com/watch?v=MXoSRF5vny8&index=26&list=PL1WH-YOycYEosvxEQjmHV14lCnh3Klc2N&t=0s

Still doesn't start up with Proton 4.2-3, even it has now Wine-Mono.

Log: steam-208650.log
Sysinfo: https://gist.github.com/NoXPhasma/f842039588ff89403b66abae978a4882

also installing dotnet through proton tricks doesn't do the trick either

Based on the log, whatever's going wrong happens before .NET or Mono starts to get involved.

This game is perfectly playable under wine using the windows steam client. The only notable difference I see is the linux steam client.
Is it possible the game does not like Proton's steam api implementation in some way? Like a missing function implementation or some hacked in copy protection by the game's devs?

@rechapit Wine-Vanilla or Wine-Staging? My impression is that something in Wine-Staging let the game start, though unfortunately no idea what exactly.

You are right. Im sorry. I was confused about the wine build I was running.

@rechapit Wine-Vanilla or Wine-Staging? My impression is that something in Wine-Staging let the game start, though unfortunately no idea what exactly.

There is something to that, as running with wine staging and steam in a prefix it runs, but there is another problem, there is a proton based on a wine staging version that does not work.

@rechapit Wine-Vanilla or Wine-Staging? My impression is that something in Wine-Staging let the game start, though unfortunately no idea what exactly.

There is something to that, as running with wine staging and steam in a prefix it runs, but there is another problem, there is a proton based on a wine staging version that does not work.

Seems there is a regresion introduced in proton. I tried using Proton-4.14-GE-1 as a custom compatibility layer and it didn´t make any difference.
I'll try to upload logs, but I wont be able to until the weekend.

Here is the log file for proton 4.14-GE-1. I created it using WINEDEBUG=+all in the user_settings.py.
I tried to do the same in the official proton 4.11 version but didn't produce any useful results

It doesn't work, I tried. I suspect that Arkham Knight needs a newer version of .NET than the one installed by Arkham City.

I've had some luck with .NET by downloading the 64bit installer for the version I need direct from Microsoft & using Taskmngr through Protontricks/Winetricks to install it. When it starts up choose repair.

I removed mono and installed .NET with

protontricks 208650 uninstaller
protontricks 208650 dotnet48

It didn't have any effect. Proton 4.11-6.

I see that ProtonDB has no good report on this game, except when LUTRIS is involved.

Well, as it's actually not working on Steam at all. A very easy solution that I just learned was to install Lutris, install the Epic Store, and install the Batman Trilogy from there, which at this moment is available for free.

@rechapit Wine-Vanilla or Wine-Staging? My impression is that something in Wine-Staging let the game start, though unfortunately no idea what exactly.

There is something to that, as running with wine staging and steam in a prefix it runs, but there is another problem, there is a proton based on a wine staging version that does not work.

Seems there is a regresion introduced in proton.

Wine-staging patches vary depending on Wine distribution, so maybe, but not necessarily.

An update on this: This indeed appears to be a proton-<>-Steam problem. It isn't a dotnet problem. I downloaded Batman Arkham Knight via Steam (for Linux, via steam play). It does not launch. I then made a Lutris prefix, symlinked the game data to the wine-steam's steamapps/common folder, and it worked fine. Launching wine-steam + wine-tgk 4.4/4.6 or wine-staging, then launching BAK worked fine. No other overrides were required. If I launch it via Proton in steam, it will not launch, regardless of any overrides.
This appears to be a Proton-specific problem, not a wine or dll problem.

Yep, some of Proton's Wine patches is responsible for this mess. And it's not related to Denuvo: I tried cracked binaries and the game still didn't launch in Steam, though it ran fine with generic Wine. Is there any superhero to bisect this patch?

Yep, some of Proton's Wine patches is responsible for this mess. And it's not related to Denuvo: I tried cracked binaries and the game still didn't launch in Steam, though it ran fine with generic Wine. Is there any superhero to bisect this patch?

Does it launch with regular Wine if you use it as a Proton version? (that is, launch Arkham Knight through Linux Steam using plain Wine?)

Does it launch with regular Wine if you use it as a Proton version? (that is, launch Arkham Knight through Linux Steam using plain Wine?)

I don't know how to make Wine available to Steam Play. If you provide a link to HowTo, I can check it out.

@chelobaka might wanna try tkg's/glorious eggroll's custom wine packages, Its running great for me on those versions. No ctd's or anything and stuttering during the driving sections is mostly gone with dxgi.syncInterval

@chelobaka might wanna try tkg's/glorious eggroll's custom wine packages, Its running great for me on those versions. No ctd's or anything and stuttering during the driving sections is mostly gone with dxgi.syncInterval

Which version works for you exactly? I'm using 4.14-GE-1 and I get this upon trying to launch the game:

@Newbytee i run mine on Tk-Glitch's custom wine runner. The latest one ive run it on is 4.20. You have to compile them but its well worth it.

So I managed to run the game with Proton, launching it from Steam (linux) directly.
But I had to replace .exe file of the game with .exe from cracked version of the game (it said that the upload was "DRM-free" and if to believe that, than this is .exe of Epic Games version since that one doesn't have DENUVO). So I guess this might be DRM problem? Game ran perfectly fine with no graphics or sound issues.

Got the idea to try this from here: https://github.com/ValveSoftware/Proton/issues/753#issuecomment-453921043

I also tried dropping the egs exe into a stock steam installation and then everything worked with 4.11-11. The real solution here seems to be Value convincing the publisher to remove dunovo from the steam release.

convincing the publisher to remove dunovo from the steam release

Well, it's either that or just do it yourself. I hope they do something about the whole DRM thing not working properly. https://github.com/ValveSoftware/Proton/issues/753 <- that thread is full of pretty good games that do not launch due to DRM.

BatmanAK.exe from EGS makes the game run just fine, but I didn't find my saved game from Steam cloud. Not sure if the game became totally unaware of Steam or it's the game version difference. Anyway DRM is evil.

Update: savegame files are incompatible between Steam and EGS versions. Their locations are different too. It's possible to convert saves from Steam to EGS [link].

Proton 5.0-1 just got released. In changelog Valve say this:

Improved Steam client integration. This makes more games that use Denuvo playable, including Just Cause 3, Batman: Arkham Knight, Abzu, and more.

Can anyone confirm that the game launches now with Proton 5.0-1?

It now manages to launch, but says 'server is unreachable'. Same thing happens with Steam for Windows through wine so it isn't a Proton specific issue.

This Proton version didn't even show up on my side. Is it beta?

Proton 5.0-1 just got released. In changelog Valve say this:

Improved Steam client integration. This makes more games that use Denuvo playable, including Just Cause 3, Batman: Arkham Knight, Abzu, and more.

Can anyone confirm that the game launches now with Proton 5.0-1?

Batman:Arkham Knight works, but PROTON_NO_ESYNC=1 is needed to be enabled.

This Proton version didn't even show up on my side. Is it beta?

I don't think it is beta.

This Proton version didn't even show up on my side. Is it beta?

It took a couple of minutes for me but eventually it showed up.

Just tried it again and it works. And I don't think Esync was the problem for me as I'm using Fsync, probably just a general server issue.

The game launches and performs well but the grapple doesn't work for me so it's impossible to make any progress, anyone else have this issue?

@poke86 Yep same here grapple doesn't work, it worked in normal wine though.

it seems crouching crashes the game too

Hello @kisak-valve, here's the log :
steam-208650.log.zip
I had to zip it, it's 55MB
I get this popup when the crash occurs:

Same issue here, crouching make a crash, tried in different areas, end game or at the start of the game ... it seems not to depend of any particular scene or context. I hope this is not an unfixable bug that game is pretty buggy .... :/

Hello @kisak-valve, here's the log :
steam-208650.log.zip
I had to zip it, it's 55MB
I get this popup when the crash occurs:

@kisak-valve I get this same error on Proton 5.0-1 as well, with or without PROTON_NO_ESYNC=1. See attached steam-208650.log.

For me the game doesn't even start. I see a similar fatal error message right after the black game window appears after the splash screen: https://i.imgur.com/UmDOgf3.png

I also get this one:

steam-208650.log

The game launches and performs well but the grapple doesn't work for me so it's impossible to make any progress, anyone else have this issue?

The grapple is disabled when the game thinks that it is pirated. Presumably this still needs more work to work properly.

This Proton version didn't even show up on my side. Is it beta?

I don't think it is beta.

OK, it reached my side now.

The game launches and performs well but the grapple doesn't work for me so it's impossible to make any progress, anyone else have this issue?

I have the same problem..
steam-208650.log

Quick update: Steams cloud sync used my old windows settings. Manually editing the configuration file <steamlibrary>/steamapps/compatdata/208650/pfx/drive_c/users/steamuser/My Documents/WB Games/Batman Arkham Knight/GFXSettings.BatmanArkhamKnight.xml to some safe values* got me into the game but with the already mentioned flaws. (crash on crouch, no grappling hook)

*: Everything 0/false and a low resolution. I think the Display_Mode mattered the most, 0 is windowed, 2 is fullscreen, 1 probably borderless

Proton-5.1-GE-1 got released, did nothing (as far as I can see) to B:AK: still launches, but game continues to think that it's pirated with Grapple not working.

EDIT: Leader-board doesn't work. Most likely also related to Denuvo.

Quick update: Steams cloud sync used my old windows settings. Manually editing the configuration file <steamlibrary>/steamapps/compatdata/208650/pfx/drive_c/users/steamuser/My Documents/WB Games/Batman Arkham Knight/GFXSettings.BatmanArkhamKnight.xml to some safe values* got me into the game but with the already mentioned flaws. (crash on crouch, no grappling hook)

*: Everything 0/false and a low resolution. I think the Display_Mode mattered the most, 0 is windowed, 2 is fullscreen, 1 probably borderless

Setting it to 2 (fullscreen) causes it to crash on launch for me, but it's fine set to 1.

By the way, PROTON_NO_ESYNC=1 does NOT seem to be needed on my end. Performance is also significantly better with esync enabled.

Just reporting that I'm not experiencing the same thing.. this is on Ubuntu 19.10. I made a video ... It doesn't crash and I can grapple enemies but when I try to grapple to stuff it won't grab/stick to anything.

https://youtu.be/hy7AVdIC5G0

I can grapple enemies but when I try to grapple to stuff it won't grab/stick to anything

That's the issue we're having, you're supposed to be able to just press F and grapple to high places. The batclaw is not the same as the grapple.

Have you tried crouching? I don't see it in the video, that's what crashes the game for me.

I can grapple enemies but when I try to grapple to stuff it won't grab/stick to anything

That's the issue we're having, you're supposed to be able to just press F and grapple to high places. The batclaw is not the same as the grapple.

Have you tried crouching? I don't see it in the video, that's what crashes the game for me.

if I press F without selecting the batclaw nothing happens, but you are right crouching crashes the game, had to kill the process from console because Xorg freezes, can't see the message.

if I press F without selecting the batclaw nothing happens

Exactly, pressing F should do something.

if I press F without selecting the batclaw nothing happens

Exactly, pressing F should do something.

Excuse for my ignorance, I haven't played this game in a long time. I didn't remember that. sorry for spamming the thread.

BatmanAK.exe from EGS makes the game run just fine, but I didn't find my saved game from Steam cloud. Not sure if the game became totally unaware of Steam or it's the game version difference. Anyway DRM is evil.

Update: savegame files are incompatible between Steam and EGS versions. Their locations are different too. It's possible to convert saves from Steam to EGS [link].

interesting something similar happened with Sherlock Holmes the devil's daughter using the binary from the GOG version that didn't have Denuvo made the game run just fine. But no achievements and no cloud saves, overlay still worked though. Now that with proton 5.0 works with the normal steam binary I fired it up and got all my achievements at once.

With PROTON 5.0-4 the game WORKS PERFECTLY!!!
At least for me...

PROTON 5.0-4

Wait... Where'd you get it?

PROTON 5.0-4

Wait... Where'd you get it?

Weird, the release doesn't appear on github but Steam downloaded it this morning all the same. Now I have to download the game again --'

EDIT : the changelog mentions it -> https://github.com/ValveSoftware/Proton/wiki/Changelog

Steam downloaded it this morning

It didn't do that in my case... I guess, since it is in the changelog, I might get it soon?

Launching the game while in exclusive fullscreen mode still causes it to crash (however setting it to exclusive fullscreen while in-game is fine until you restart), and performance still leaves a lot to be desired. That aside, it seems to be working like it should here.

The hook is available now and crouching won't crash the game anymore. Haven't tried fullscreen again.

While wandering a bit around I noticed a small graphic glitch:

The game runs fine for me with Proton 5.0-4. I also don't have any issues with Fullscreen enabled, the game launches fine with it enabled. Haven't looked for any rendering issues in particular but didn't noticed any, will report back if I find some.

https://gist.github.com/NoXPhasma/35d7ddf3ae948239a6cc179bca4f234e

The game runs fine for me with Proton 5.0-4. I also don't have any issues with Fullscreen enabled, the game launches fine with it enabled.

Is that fullscreen or borderless window?

Fullscreen.

Working good this time with proton 5.0.4 but the perfomance is very bad, you need to downgrade and is not stable, but i can play good

I've also decided to give it a shot on 5.0-4 and so far it works as it did on Windows, except for sharder cache stutter ofc. As a tip: don't even try running it at anything above 30 fps. Even on Windows everything stutters like crazy, textures don't load on time and at fps above 30 Batmobile seems to lag as well. And if you load in your save file - expect a ton of stuttering.

I don't have any of those >30FPS issues you mention.

Interesting... @NoXPhasma. I do get above 70 on high settings while moving on foot, but as soon as I get in the car fps goes down to ~34.
EDIT: On lowest settings with V-Sync turned off fps drops to 50 while driving, fair enough.

I can confirm it starts up on Pop OS 19.10 but I still get quite a lot of stuttering throughout the game. But it could be because I don't have Proton GE. This can probably be fixed in an update too.

Can it be shader compilation that's causing stuttering? Try going through
an area once and if you get stuttering go through that area again, if there
will be no stuttering — that's shaders being compiled.

On Mon, 23 Mar 2020, 6:30 am CSForever07, [email protected] wrote:

I get quite a lot of stuttering throughout the game. But it could be
because I don't have Proton GE. This can probably be fixed in an update too.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/558#issuecomment-602328899,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALUJ6CBBVE3RAEVAPK4S5JTRI3CSXANCNFSM4FRRUZRQ
.

Anyone still experiencing crashes with full screen?
I can't play more than 5m till it crashes

steam-208650.log

Anyone still experiencing crashes with full screen?
I can't play more than 5m till it crashes

It takes longer for me but still crashes pretty frequently in borderless as well.

Ok so i been messing with the settings trying to figure this out and found that if i use the resolution from my screen (1080p) the game dont crash but soon as i put any lower it either crashes right away or takes a bit, i guess this was the problem cause i used to play at 1600x900 resolution on windows so i used the same here as well, my gpu aint that powerfull so at 1080p i drop some frames below 30 but the game doesnt crash, also i tried 4 times to make sure of it and at least on my end it just crashes on anything below 1080p.

I can replicate the above crashing issue after a period of time (usually less than an hour)
As my R9 285 is a bit weak for Arkham Knight at 1080p I've been playing at 1280x720/1600x900 on Low with Proton 5.0-10 RC with the ACO shader compiler (enabled by default in Mesa 20.2)
dmesg reports the following:

[45772.394666] [drm:amdgpu_gem_va_ioctl [amdgpu]] ERROR Couldn't update BO_VA (-16)
[45985.212114] [drm:amdgpu_gem_va_ioctl [amdgpu]] ERROR Couldn't update BO_VA (-16)
[45985.222664] [drm:amdgpu_gem_va_ioctl [amdgpu]] ERROR Couldn't update BO_VA (-16)
[45985.222816] [drm:amdgpu_gem_va_ioctl [amdgpu]] ERROR Couldn't update BO_VA (-16)
....

It looks like it's crashing or otherwise upsetting the kernel driver.
A bit annoying as it's otherwise working rather well; I thought the problem was solved this afternoon as it didn't appear.
glxinfo
steam system info

I've seen people post the same error on Windows so perhaps it's just an unfixed game bug? It had a shoddy initial release and it's still stuck with Denuvo (several other titles have removed it recently)
https://steamcommunity.com/app/208650/discussions/search/?q=build+july+2012&gidforum=540735426802665115&include_deleted=1

Just a quick update:
<> In-game resolution setting has no effect in my testing; I've had the game crash at 1920x1080, 1600x900 or 1280x720.
<> Disabling the DXVK state cache (and removing the cache) has no impact nor does changing to Windows 7 in Winecfg with Protontricks.
<> Both the Denuvo Steam exe (100MB 8c4b954290df8b5b8602e2ce9969e59d) and the DRM-Free Epic exe (50MB 3ddb95c66317c36f7e67bfbca57d02cb) crash so it's probably not the game protection.
<> ACO or LLVM makes no difference i.e. RADV_DEBUG=llvm

I believe I've solved it at last after trying the above steps which didn't help.
I've completed Arkham Knight now after 72 hours (120% completion; excluding the DLC Episodes) and just put up with it crashing every 40 minutes or so. The game otherwise seems to work perfectly #1 #2

I've had OKAMI HD in my Library for a while and thought I'd better play it.
Experienced similar random crashing/hanging as the comments in the topic and at the ProtonDB mention.

Seeing FSYNC mentioned there, I've compiled the latest stable kernel (5.8.5) with the fsync patches #1 #2
i.e:

wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.8.5.tar.xz
tar xvf linux-5.8.5.tar.xz
cd linux-5.8.5/
patch -p1 <../futex-wait-multiple-5.2.1.patch  
make deb-pkg -j 16 

Played for well over an hour and a half across several game modes in Arkham Knight without a single crash.
Haven't tested OKAMI HD yet but soon will.
Hopefully the FSYNC work will eventually find it's way into the kernel just as ACO has in Mesa.

steam-208650-batman-ak.log
steam-587620-okami.log
kernel config.txt

No crashing/hangs when changing area in OKAMI HD after 90 minutes either - FSYNC must be working :+1:
futex_selftests.txt
fsync tag?

System Information

• GPU: GTX 1660 Super 6GB
• Driver/LLVM version: nvidia official driver 460.84 by ppa oficial Graphics
• Kernel version: 5.4.0-74-generic
• Link to full system information: https://gist.github.com/corvusd/38a7dd02e082261ec7379858d6759ce3
• Proton version: proton-experimental / proton 6.3 / proton 5.13 / proton 5.0

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.

MANGOHUD=1 gamemoderun %command%

steam-208650.zip

Symptoms

The game crash after 40min with window message.

Reproduction

Normal playing or running the game.

Research

These to last two weeks I am playing and testing Batman Arkham Knight. Start with proton experimental after with 6.3 with a really great performance. But sadly crash at 40min.

I discover after on prontondb a lot of users have this problem with the most new proton version. I did continue test with more proton version. When arrive to 4.11 the crash disappeared. The performance is little worst. Shuttering mainly. After that I review the protondb report and go to more old. I can saw that all the crash report start with 5.0 version.

Then I thought to update the dxvk from 1.5.1 to more newer version and try. I did choose 1.8.1 the crash appear again. I can't confirm at 100% but look like. Then if with proton 5.0 with 1.7 dxvk have also crash. In some point between dxvk 1.5.1 and maybe 1.7, maybe earlier, I didn't test 1.6, some regression appear here for Batman Arkham Knight.

I start with kernel 4.15. In proton discord recommended try most new. And try with 5.4. Same result. After reread this report https://github.com/ValveSoftware/Proton/issues/558#issuecomment-683154987 and tell in discord. In tried 5.12 liquorix, same result. Try deactivate esync, same result. And deactivate esync and fsync. Same result.

I don't really how or if is possible trace or debug that. Only shared my experience. Because is sad not have this game with a real full compatibility for that game.

I remmeber that with Batman Arkham Origins I had a similar crash https://github.com/ValveSoftware/Proton/issues/1385#issuecomment-590121210

Great job indeed for all you people. Thanks to all for these efforts!

After test most newest dxvk version upper than 1.5.1. I checked that the last dxvk version free of this crash is 1.5.5. The 1.6.0 start to have this crash.

I can't confirm that. Crashes with Proton 4.11 as well. The error is also different at times, like something about xcb_writev() but always "filename not found".

@DanMan how much time until the crash?

About the same as usual - roughly an hour maybe.

Really strange. Now I can play without crash all time. Sessions of 100 or 120 minutes. What are your systems specs? Client version, os, driver, GPU, kernel, gamepad... Etc?
Edit: you take care of use stock dxvk in this proton version. Or not use more than the dxvk that I tried.

Hi @kisak-valve,

I've been unable to reproduce any GPU hangs with an R9 285 as described previously in this comment: https://github.com/ValveSoftware/Proton/issues/558#issuecomment-675755549.

Testing and soaking was performed with Proton 6.3-6 on both your 21.2.1 Mesa release and the latest oibaf (21.3~git2108250600.ad7864~oibaf~f). Although the user reported FSYNC solving his issue (https://github.com/ValveSoftware/Proton/issues/558#issuecomment-683154987), all my testing was done with ESYNC and that didn't seem to cause any issues.

Unless there are still RADV specific issue reports, I think the Mesa / RADV labels can be removed.

Note: All Batman Arkham titles have a similar crash (as seen here: https://github.com/ValveSoftware/Proton/issues/558#issuecomment-864470329) that occur on both AMD and Nvidia.

I'm getting "Fatal error!" messages after about an hour or maybe less of playing.

Proton 6.3-7
Driver:  AMD AMD Radeon RX 5600 XT (NAVI10, DRM 3.42.0, 5.14.9-200.fc34.x86_64, LLVM 12.0.1)
Driver Version:  4.6 (Compatibility Profile) Mesa 21.1.8
GNOME 40.4, Wayland

Is there any way I could help to find the cause of this error? Not sure if it might be related, but I've skipped shaders processing the first time I launched the game (last bit took way too long), let it complete second time though.

I get the same error as @joshas , but I'm on proton-ge-6.18; fairly sure it happened on proton-experimental too.

I'm on an Nvidia 960 (Driver version 470.74); kde plasma (X11).

It happens somewhat randomly from what I can tell, but when it happens it seems to be after 1-2 hours of playtime.

I am also on the Arch zen kernel, so Fsync may be used. I haven't tried disabling Fsync (or esync).

I too am on Arch with Budgie desktop environment and the game runs perfectly for me. However I'm not on a custom kernel
and I use a AMD Radeon RX 580. I can also confirm that it works on elementary OS just as well as I used that before switching to Arch.

I think the "Fatal Error!" crashes are a regression from Vanilla Wine. I was able to complete the main story in vanilla wine by installing Steam in a prefix and installing Arkham Knight from there, while the proton version crashes every 5-10 minutes. The game's engine needs to load areas during gameplay sometimes (or often if you are on a low-spec machine). In vanilla wine, this results in a rotating bat symbol appearing in the bottom right corner while the game loads the area. For some reason, this doesn't happen in Proton, which causes the Fatal Error message.

This runs with Proton experimental and Mesa 22.0-rc1, but loading causes plenty of stuttering. It also uses only low amount of CPU capability during the stuttering (a fraction of what is available) so it's not scaling to multiple cores for some reason? I haven't seen the error message mentioned above when continuing from old save file.

Edit: Mesa 21.3.5 seems to work much better with less stuttering.

Adding update: kernel 5.17 works fine with Mesa 22.0 and Proton 7.0.
Previously with Mesa 22.0 there was severe stuttering in the open roam in the city, particularly when driving Batmobile.
Now, with kernel 5.17 the stuttering is mostly gone: there's brief pause at times when loading something but it isn't constantly there like before.

I'm not sure what might be the reason (there's fscache changes in new kernel? and there's driver changes of course), it is possible some other piece software might have fixed something (but I doubt that due to way Proton works).
Either way, with a faster harddrive the skips might not even be there at all any more?

While browsing the list of AR challenges for vehicle combat game threw this error dialog. This looks similar to what others have been reporting in the past but after a longer gameplay session.

Edit: After restarting the game same thing works normally without errors.

I'm getting a similar error as ipr here, same specs when it comes to mesa, kernel, and proton version. Does so only after about an hour of play. However, still getting "BUILD_JULY_2012" error as others have mentioned.

My specs:

(Using 6900 XT)

I'm also experiencing fatal errors during gameplay with the crash usually happening after ~ 40-60 minutes; error message is always the same with only the address changing:

System specs:

 OS: Arch Linux 
 Kernel: x86_64 Linux 6.1.8-zen1-1-zen
 Uptime: 1h 8m
 Packages: 1728
 Shell: zsh 5.9
 Resolution: 2560x1440
 DE: KDE 5.102.0 / Plasma 5.26.5
 WM: KWin
 GTK Theme: Breeze [GTK3]
 Icon Theme: breeze-dark
 Disk: 3,8T / 5,0T (79%)
 CPU: AMD Ryzen 5 3600 6-Core @ 12x 3.6GHz
 GPU: AMD Radeon RX 580 Series (polaris10, LLVM 15.0.7, DRM 3.49, 6.1.8-zen1-1-zen)
 RAM: 4716MiB / 15916MiB

Full Proton log:

steam-208650.log

I'm experiencing a crash at launch on Fedora 40, Flatpak Steam, Proton Experimental, proprietary 550.78 driver.
It works for my friend who uses the same software stack, and on my PC the EGS version installed via Heroic also works.

Specs:

OS: Fedora Linux 40 (Workstation Edition) x86_64 
Host: MS-7C02 1.0 
Kernel: 6.8.9-300.fc40.x86_64 
Resolution: 1920x1080, 1920x1080 
DE: GNOME 46.1 
CPU: AMD Ryzen 5 3600 (12) @ 3.600GHz 
GPU: NVIDIA GeForce GTX 1050 Ti 
Memory: 8322MiB / 15902MiB 

Things I've tried:

• Verifying and reinstalling the game.
• Disabling all the DLC.
• Deleting all configs and cloud saves.
• Proton versions from 7 to Experimental, including GE.
• Every launch parameter I could find on ProtonDB.
• Manually (re)installing pre-requisites using protontricks.

Screenshot of the error, Proton log and game crash dump:
BatmanAK.zip

EDIT:
The problem turned out to be incorrect working directory.
I'm not sure how it happened, and why it didn't affect all games, but doing a clean reinstall of Steam fixed it.

Hi. I'm trying to enable Gameworks options on a nvidia hw but no NVAPI option is doing anything. Is something missing or broken? ProtonDB have some feedback saying it was working at some point.

I tested with proton experimental, 9, 8 and 7. No version works with Gameworks.
Using the nvidia driver 560.35 and a RTX 3070.

Game works fine here, clean prefix, GE-Proton10-4, Nobara 42, no launch options, AMD gpu. Maybe nvidia specific driver bug?

Game works fine here, clean prefix, GE-Proton10-4, Nobara 42, no launch options, AMD gpu. Maybe nvidia specific driver bug?

I'll revert to an earlier NVIDIA driver and try again then. Here's hoping.

If you look a few posts above you’ll see I had this exact same issue. The fix was doing a clean reinstall of Steam in my case, as it was setting the game’s working directory incorrectly for some reason. After that, the game just worked out of the box, as it should.

If you look a few posts above you’ll see I had this exact same issue. The fix was doing a clean reinstall of Steam in my case, as it was setting the game’s working directory incorrectly for some reason. After that, the game just worked out of the box, as it should.

I'll try this first and then if it doesn't work revert my NVIDIA driver. Thanks for the heads up.

If you look a few posts above you’ll see I had this exact same issue. The fix was doing a clean reinstall of Steam in my case, as it was setting the game’s working directory incorrectly for some reason. After that, the game just worked out of the box, as it should.

Update: Cleanly reinstalled Steam, and still no change. Same error message. Going to try reverting NVIDIA drivers next.

Generated a fresh log file just in case there's any differences. If someone wants to have a look, there it is.

steam-208650.log

Replying to https://github.com/ValveSoftware/Proton/issues/558#issuecomment-2968700349

Update: I decided to just stop running up against a wall and go with a solution I know works. I reinstalled Windows 10 on a new partition, and I'm now dual booting it alongside CachyOS. Not what I wanted, but I was getting very burnt out trying to fix this. So we can call this issue closed. Thanks for the help regardless, anyone who did so.

Arkham Knight launches fine for me on Steam Deck OLED and Bazzite however I've noticed some regressions with proton 11 compared to proton 10. First (minor) issue is now when launching the game it flashes a solid full screen white image for 5-10 seconds which is a little unpleasant and does not happen on proton 10. The second issue is performance seems a lot more stuttery with proton 11 compared to 10. Both runs had the compiling vulkan shaders step completed prior to them but proton 11 has far more frame time drops and stutters. Happens both on Mesa 25 on the steam deck and Mesa 26 on a PC with bazzite (7600x3d + 9060XT)

@kisak-valve I added the logs. I did a run with each Proton 10 and 11
steam-208650.log

proton11-steam-208650.log