Batman: Arkham Asylum Game of the Year Edition (35140)

[tr37ion]

Arch Linux
Kernel 4.18.3
Proton 3.7
Nvidia GTX 1070 - nvidia-beta 396.54
KDE Plasma 5.13.4
KDE Framework 5.49.0
Qt 5.11.1

The game doesn't even launch. The preparing to launch... dialogue pops up for some seconds then exits without starting the game at all.

[d10sfan]

Seeing the same result on Xubuntu 18.04. Interestingly, Arkham Origins seems to work fine.

[miguev]

Same on Ubuntu 18.04.1 LTS x86_64 / 4.15.0-33-lowlatency / Ryzen 5 1600X / NVIDIA GeForce GTX 1070 / NVIDIA 396.54

Steps to reproduce:

• Install game (35140)
• Exit Steam.
• Open terminal and run: steam steam://rungameid/35140
• Exit Steam (after waiting for 10+ minutes).

Full output: 35140.txt

Arkham Origins runs well, better than with PlayOnLinux & wine 3.12-staging.

[miguev]

Tried again after adding PROTON_NO_ESYNC=1 PROTON_LOG=1 %command% to launch options.
steam-35140.log

[ghost]

steam-35140.log

Another log if it'll help

Distro: Ubuntu 18.04.1
GPU: Intel Iris Pro 580
Resolution: 1280x720
RAM: 32GB
Controller: DS4
Proton 3.7-5 Beta

https://gist.github.com/daasuharo/cb605b8cd50227982a9bfa4dfcb1f635

[kisak-valve]

Compatibility Report: Batman: Arkham Asylum Game of the Year Edition (appID: 35140)

Issue transferred from #1311.
@furai posted on 2018-09-08T09:35:23:

Compatibility Report

• Name of the game with compatibility issues: Batman: Arkham Asylum Game of the Year Edition
• Steam AppID of the game: 35140

System Information

• GPU: NVIDIA Corporation GeForce GTX 970M/PCIe/SSE2
• Driver/LLVM version: NVIDIA 396.54
• Kernel version: 4.18.6
• Link to full system information report as Gist: https://gist.github.com/furai/c8ce8a1c183c5ed769f72aefba0513dd
• Proton version: 3.7-6 Beta

I confirm:

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

steam-35140.log

Symptoms

Game won't even start.

Reproduction

Install the game on Ubuntu 18.04 via Steam and try to launch it.

---

@whizse commented on 2018-09-08T10:00:59

Tracked in #421

---

@furai commented on 2018-09-08T10:06:32

Uhm, what? This is weird, I've searched for issues before posting this, made sure it's not there. I have no idea how I missed that report. Should I post there instead?

[pchome]

Hm, maybe there is a specific way Steam or Proton runs executables?

err:module:LdrInitializeThunk Main exe initialization for L"Z:\\.....\\BmLauncher.exe" failed, status c0000017

Meanwhile the game can be launched directly, using Proton and it's prefix.

Using q4wine I set up :

• Proton as custom wine version
• new prefix pointing to Proton's prefix
• using builtin tools installed mono, mdx, physx, d3dcompiler_43 (according to AppDB)
• "icon" for BmLauncher.exe

Launcher started, the game runs fine with all setting to HIGH (except MSAA:2x).

Here is a "beautified" (as an script) console command used by q4wine:

#!/bin/sh

steam_library="/media/Games/SteamLibrary-Wine/SteamApps"

 WINEPREFIX="${steam_library}/compatdata/35140/pfx"

       WINE="${steam_library}/common/Proton 3.7 Beta/dist/bin/wine"
 WINESERVER="${steam_library}/common/Proton 3.7 Beta/dist/bin/wineserver"
 WINELOADER="${steam_library}/common/Proton 3.7 Beta/dist/bin/wine"
WINEDLLPATH="${steam_library}/common/Proton 3.7 Beta/dist/lib64/wine"


cd "${steam_library}/common/Batman Arkham Asylum GOTY/Binaries/" || exit


${HOME}/.steam/steam/ubuntu12_32/steam-runtime/run.sh "${WINE}" BmLauncher.exe  2>&1

NOTE:

• steam-runtime/run.sh - to suppress missing libraries warnings, also I have working controller with it
• you may need nvapi for GPU PhysX support
• you need Steam launched

[pchome]

@pchome

Hm, maybe there is a specific way Steam or Proton runs executables?

https://github.com/ValveSoftware/Proton/blob/proton_3.7/proton.in#L91

...
wine_path = bindir + "/wine64"
...

Changing this to wine_path = bindir + "/wine" allows run game from Steam by pressing Play button.

Just noticed there is PR #1087 supposed to fix this issue.

[tuxtergames]

trying to play in playonlinux I figure it out thats after install physx and dotnet 3.5 the game runs great, but in x32 prefix with steam, but we can't install dotnet 3.5 in proton cause the prefix is x64, anybody know how is it possible to install dotnet in x64 prefix?

[philipl]

I was able to get this running by first getting Arkham City GOTY working based on the discussion in #309 (setting the windows version to XP and then letting the first-run install .NET), and then copying the wine prefix from City to Asylum's location.

[lucifertdark]

I was able to get this running by first getting Arkham City GOTY working based on the discussion in #309 (setting the windows version to XP and then letting the first-run install .NET), and then copying the wine prefix from City to Asylum's location.

I can confirm copying the pfx folder from Arkham City to Arkham Asylum works perfectly, it even picks up my save from the last time I played it in Windows 3 years ago. 👍

[miguev]

Tried the same workaround without having Arkham City GOTY in my library, but didn't work.

System.NotImplementedException: The method or operation is not implemented.
at System.Management.ManagementObjectSearcher.Get () [0x00000] in <...>:0
at (wrapper remoting-invoke-with-check) System.Management.ManagementObjectSearcher.Get ()
at BmLauncher.SystemInfo.GetInfo (System.String query Object, System.Int32 &count) [0x0001c] in <...>:0

EDIT: I posted too soon. After clicking the "OK" button in the window with the above error message, and the same again once or twice more, I got the game's start menu. Then when I click on PLAY the game crashes for good, with an entirely different error pop-up:

steam-35140.log

[lucifertdark]

Do you mean you don't have Arkham City at all? It's possible Arkham City is the only game you can use to make it work.

[miguev]

The workaround did work when copying the pfx files from Arkham City GOTY.
Just purchased that other game, applied the workaround in #309 and then copied the pfx directory.
Now I can play both games, for well over 30 min without much of a glitch.
The first warning pop-up (attached now) did still show up and I had to click OK 3 times before getting to the game's main menu, but after it's being a very smooth ride.

[miguev]

@lucifertdark indeed I did not have Arkham City. Some time ago I got these 2 and Origin and they all run with PlayOnLinux but City would freeze and crash every single time at the very first autosave, before you get to do anything at all, so back then I refunded it and kept only Asylum and Origins. Now, with the prospect of getting Asylum to work and several reports confirming the workaround for City was good, I tried it again and this time it worked. All of this on Debian buster with NVidia 390.87 so not even the latest drivers!

[lucifertdark]

@miguev Glad you got it working. 👍

[tuxtergames]

Tried the same workaround without having Arkham City GOTY in my library, but didn't work.

System.NotImplementedException: The method or operation is not implemented.
at System.Management.ManagementObjectSearcher.Get () [0x00000] in <...>:0
at (wrapper remoting-invoke-with-check) System.Management.ManagementObjectSearcher.Get ()
at BmLauncher.SystemInfo.GetInfo (System.String query Object, System.Int32 &count) [0x0001c] in <...>:0

EDIT: I posted too soon. After clicking the "OK" button in the window with the above error message, and the same again once or twice more, I got the game's start menu. Then when I click on PLAY the game crashes for good, with an entirely different error pop-up:

steam-35140.log

Flollow @philipl tip above, works fine here, and to run City game you need to do this #309

[zimudec]

How can I make it work without having batman arkham city?

Or else, can someone share the "pfx" folder of arkham city to test the solution?

[d10sfan]

I was able to get it to work and run by doing the following:

• Set the prefix to winxp
• Install d3dx9_43 and d3dcompiler_43 using winetricks
• Download the latest version of wine-mono from http://dl.winehq.org/wine/wine-mono/
• Install the wine-mono msi using the wine uninstaller (can be run using winetricks). It may not show anything changing, but I was able to reload the uninstaller and it showed.
• Run the game. It'll show three error popups, but after that the launcher will appear and the game can be played.

It seems like wine does not exit cleanly after closing the launcher or the game. I had to manually kill wineserver, and the proton execution script

[mwprado]

It works with protontricks to download dotnet framework. The steps are described on site prótondb. (I've played using steam on fedora)

[andrew-mcmahon]

Grabbed the Arkham Collection recently.
Working after some tweaks with protontricks; I used the following command from the latest report:

protontricks 35140 dotnet20 d3dx9 d3dcompiler_43

DX9 performance isn't equal to Windows nor is as good as newer titles which can use DXVK (i.e. Metal Gear Solid V, Max Payne 3, Dark Souls 3, etc)
Wide open areas particularly struggle.
Those of you with modern CPU's probably won't even notice - my machine is a bit of a dinosaur now.
XBOX360 controller works.
Took a few screenshots.
No major gameplay/graphical issues - very playable overall. Managed to 100% the game with most steam achievements so it can't be that bad =)

[RiantAnda]

Proton 4.2-3 improved the situation a bit:
On launch there are three "System.NotImplementedExeception" popups, then the launcher is shown. Clicking play gives me a "Failed to compile global shader FGFxPixelShader <GFx_PS_CxformMultiply2Texture>" message, then the game crashes.

I'm using a GTX970 card with nvidia blob
steam-35140.log

[nsivov]

That's likely about missing Mono functionality [1]:

[00000028:] EXCEPTION handling: System.NotImplementedException: The method or operation is not implemented.

"<unnamed thread>" tid=00000028 this=02550120 , thread handle : 00D44520, state : not waiting
  at System.Management.ManagementObjectSearcher.Get () [0x00000] in <ac811348b1c347198048a5db4fe5e69a>:0
  at (wrapper remoting-invoke-with-check) System.Management.ManagementObjectSearcher.Get () [0x00031] in <ac811348b1c347198048a5db4fe5e69a>:0
  at BmLauncher.Program.GetProcessOwner (int) [0x00018] in <96984e55025348f1980e12aaf1d28209>:0
  at BmLauncher.Program.GetPrevInstance () [0x0000c] in <96984e55025348f1980e12aaf1d28209>:0
  at BmLauncher.Program.Main () [0x00032] in <96984e55025348f1980e12aaf1d28209>:0
  at (wrapper runtime-invoke) object.runtime_invoke_void (object,intptr,intptr,intptr) [0x00027] in <72b294be54bc4854bce603b664bafd63>:0

[1] https://github.com/mono/mono/blob/master/mcs/class/System.Management/System.Management/ManagementObjectSearcher.cs

[kisak-valve]

Batman: Arham Asylum no sound on 4.11-1

Issue transferred from #2942.
@jefferyrlc posted on 2019-08-02T18:39:44:

Compatibility Report

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

System Information

• GPU: GTX 960
• Driver/LLVM version: 430.26
• Kernel version: 4.19
• Link to full system information report as Gist:https://gist.github.com/jefferyrlc/8d5e28d888756608d05168437bb5aac0
• Proton version: 4.11-1

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.

steam-35140.log

Symptoms

There is no audio output, audio worked in 4.2 but upon cleaning the pfx and setting the game up to use 4.11-1 there is no audio output

Reproduction

install the game, winetricks, and protontricks
run protontricks 35140 mdx d3dx9 d3dcompiler_43 win10
change the launch options to
PROTON_USE_D9VK=1 %command%
run the game
have no sound

---

@LeJimster commented on 2019-08-03T23:16:40:

Just tried deleting my working prefix, letting steam create a fresh 4.11-1 prefix and running the same commands.. Everything works fine for me, including sound...

My system

---

@aeikum commented on 2019-08-05T14:56:39:

Can you check your volume mixer (e.g. pavucontrol) to verify that the game's audio output isn't muted or directed to some other audio device?

[ThisNekoGuy]

@ipr
My every attempt used a clean prefix; aside from protontricks, I didn't modify the prefix in any of the attempts in any way
Any references to wine-mono are thereby what come with Proton 6.3-8 by default

[ipr]

@ipr My every attempt used a clean prefix; aside from protontricks, I didn't modify the prefix in any of the attempts in any way Any references to wine-mono are thereby what come with Proton 6.3-8 by default

Then don't use protontricks.
That is opposite to having clean install.

If you can't get into launcher something is already broken in your install and if you are using protontricks then that is breaking it. Process of elimination to likely suspect.

[smintman]

Looks like it’s having trouble loading dlls from your big storage drive? Permissions issue? Or NTFS issue?

[ipr]

Looks like it’s having trouble loading dlls from your big storage drive? Permissions issue? Or NTFS issue?

They are supposed to be symlinks to Proton directory from per-game compatdata so that is a possibility.
Or the first-time installation has failed for some reason. Or there is some override in place that should not be there.

[ThisNekoGuy]

@ipr I said multiple times that I both did and did not use protontricks; I don't know how I can be any more clear about the methodologies used besides what I already said.

@smintman I don't use NTFS (I use BTRFS) and it isn't a permissions issue, at least not caused by myself; Proton versions past 5.0 are known to have permissions issues regarding symlinks they make but, considering how I can't seem to find anyone else having this specific issue, I find this less likely.

I don't have issues with other games running on BTRFS, so I don't expect that to be the reason either.

[SeongGino]

It seems like Arkham Asylum's PhysX (only covers interactive paper here?) takes a big dump on the framerate. A GTX 1060 6GB goes all the way down to ~30fps/20fps in the simplest prison challenge map, while Arkham City has similar issues but is much more reasonable a relative drop. And this is with PROTON_ENABLE_NVAPI=1 and PROTON_HIDE_NVIDIA_GPU=0, as redundant as it is, both in use in command line options.

I can understand that some PhysX games are using CPU fallback, but I didn't think the first of the series would have the most severe overhead over the others.

(Also, PhysX only works with main Proton and Experimental; GloriousEggroll seems to not use it at all)

[CSahajdacny]

Have you tried with a dxvk.conf file with the text dxgi.nvapiHack = False in the same folder of the game's executable?

[SeongGino]

Have you tried with a dxvk.conf file with the text dxgi.nvapiHack = False in the same folder of the game's executable?

Well PROTON_ENABLE_NVAPI is supposed to do something similar without needing a neighboring file, no?

Regardless, same result.

[Blisto91]

@SeongGino Yes on proton experimental PROTON_ENABLE_NVAPI=1 should be enough (See here if it is of interest to anyone). For 7.0-1 and below you still need the seperate conf file.

I can try to check the physx issue when i have time.

[jp7677]

About PhysX, see https://github.com/jp7677/dxvk-nvapi/wiki/Tips-and-tricks-for-usage-with-DXVK-NVAPI#physx
In a nutshell, The nvcuda.dll library in regular/experimental Proton needs to be replaced with a suitable version and likely the PhysX runtime needs to be updated for that game/prefix. That said, this procedure works for Arkham Knight, dunno for this game.

[SeongGino]

About PhysX, see https://github.com/jp7677/dxvk-nvapi/wiki/Tips-and-tricks-for-usage-with-DXVK-NVAPI#physx In a nutshell, The nvcuda.dll library in regular/experimental Proton needs to be replaced with a suitable version and likely the PhysX runtime needs to be updated for that game/prefix. That said, this procedure works for Arkham Knight, dunno for this game.

Well, not to digress, but I use (mainly) Proton-GE, so that already fulfills the library requirement.
For whatever reason, prefixes made with GE have nvcuda's override set to ?? which presumably disables it, so I changed that in all three of my Batman prefixes (so City and Origins in addition to Asylum) as well as the one I use for Arkham Knight from EGS using Wine-GE.
And after installing the PhysX verb, Origins and Knight expose the full PhysX-exclusive settings and the significant drops I get when using effects in City are more or less resolved. So I at least know it's working on this system.

But unfortunately, no change in Asylum. The launcher still doesn't recognize a compatible card when toggling PhysX, and the performance is still garbo even compared to AK at full whack, 1080p... just for paper at that. So I think there's definitely something wrong with this game specifically that needs addressing.

[pchome]

Different PhysX versions have different HW support detection. Newer versions likely supported by dxvk-nvapi, older likely not. Moreover in newer PhysX installers some old versions support was dropped, moved to separate installer and forced to SW-only (IIRC).

There is one trick which sometimes helps: you can install PhysX via winetricks (or alternative) and then rename PhysXDevice.dll (if any) in game's directory (backup it). Game will use PhysXDevice.dll from installed PhysX and will detect HW support (if you lucky enough).

Also you can try to replace that dll with an "verified" version (just remember about 32 and 64 bit).

[SeongGino]

Different PhysX versions have different HW support detection. Newer versions likely supported by dxvk-nvapi, older likely not. Moreover in newer PhysX installers some old versions support was dropped, moved to separate installer and forced to SW-only (IIRC).

There is one trick which sometimes helps: you can install PhysX via winetricks (or alternative) and then rename PhysXDevice.dll (if any) in game's directory (backup it). Game will use PhysXDevice.dll from installed PhysX and will detect HW support (if you lucky enough).

Also you can try to replace that dll with an "verified" version (just remember about 32 and 64 bit).

Unfortunately, this advice applies to literally every other game in this series except Asylum - this is the only one without an associated PhysXDevice library. Only relevant NV library of this kind it has is PhysXExtensions.dll.

1MIN-EDIT: I just had to open my big mouth too early.
I stuck in Arkham City's PhysXDevice.dll into Asylum's binary directory (alongside BmLauncher.exe and etc.), and just with that, the PhysX effects are running with hardware acceleration like it should.
The launcher will still warn that the device isn't a dedicated GTX 260/9800 GTX, but that's now on par with Windows behavior - and much better than the erroneous incompatibility message before.

[ThisNekoGuy]

@SeongGino What Proton version did you use? I can't replicate that

[SeongGino]

@SeongGino What Proton version did you use? I can't replicate that

This is with GE.

[ThisNekoGuy]

@SeongGino Sorry about that; I had forgotten that the game needed a few protontricks verbs to get running; I have replicated what you described as well, with Proton-tkg :p

Also note, for anyone else, placing the same dll from the physxwinetricks install to substitute for the Arkham City one doesn't work; I'm aware this was iterated in another manner, but in case anyone was wondering, just moving that one to the game folder won't make a difference Lol
Something special about AC's library for it

[SeongGino]

If it matters, Origins' dll works as well, and the same applies to the one from Borderlands 2. I think the necessary file just needs to be pulled from any other PhysX game newer than AA.

[kisak-valve]

help

Issue transferred from #6347.
@Abdullahalshriqi posted on 2022-11-27T17:40:38:

batman Arkham asylum
my pc

amd ryzen 5 3500u

12 gigb ram
vega 8

fedora 37 gnome x.org with steam proton

i have batman arkham city
how i can fix that

[LeJimster]

@Abdullahalshriqi with it being a d3d9shadercompiler error, you likely need to install the relevant native dx9 compilers. A quick look on protondb gave an answer.

So use protontricks to install those 2 things to your games prefix.

[ghost]

I would like to report that the following fix is is required on my machine in order for the game to start after clicking "PLAY" in the game's initial Launcher window:

• The game is playable [on my Gentoo Linux machine with the compatibility tool GE-Proton7-42 and PhysX=Normal] only if Steam is started with LD_LIBRARY_PATH pointing to a directory in which libopenal.so.1 is a symlink to Steam's libopenal.so.1.16.0:

$ tree $HOME/ld_library_path
/home/steam/ld_library_path
├── i386
│   ├── libopenal.so.1 -> libopenal.so.1.16.0
│   └── libopenal.so.1.16.0 -> /home/steam/.local/share/Steam/ubuntu12_32/steam-runtime/usr/lib/i386-linux-gnu/libopenal.so.1.16.0
└── x86_64
    ├── libopenal.so.1 -> libopenal.so.1.16.0
    └── libopenal.so.1.16.0 -> /home/steam/.local/share/Steam/ubuntu12_32/steam-runtime/usr/lib/x86_64-linux-gnu/libopenal.so.1.16.0

$ cd $HOME/.local/share/Steam
$ export LD_LIBRARY_PATH=$HOME/ld_library_path/i386:$HOME/ld_library_path/x86_64
$ ./steam.sh

Cause of the problem: The machine's libopenal.so.1.22.2 is loaded by the ELF loader instead of Steam's libopenal.so.1.16.0 and this causes the game to SEGFAULT immediately after clicking "PLAY" in the game's Launcher window.

[andirsun]

Why this game works normally on Proton GE but not on the original Proton ? I dont want to use protonGE.

[SeongGino]

Because upstream Proton has no embedded DXVK-NVAPI (the same stuff used to enable RTX/DLSS is also needed for HW accelerated PhysX used in old implementations like Batman games). GE works better on average in my case - but if you don't want to, your only other choice is to build Proton yourself with the necessary NVAPI patches.

Or I guess, just not use physics. It works totally fine without them in Valve's Proton. The tangible effect really is quite minor for the performance hit you take.

[kisak-valve]

Because upstream Proton has no embedded DXVK-NVAPI this is not true.

[kisak-valve]

Btaman Arkham Asylum

Issue transferred from #6714.
@Abdullahalshriqi posted on 2023-04-23T23:45:33:

proton 8

ubuntu 23.04

---

@Abdullahalshriqi commented on 2023-04-23T23:48:09:

but arkham city work very fine

[EpicureanGit]

System Information:
OS: Slackware 15
NVIDIA Driver Version: 535.104.05
Steam Version: 1698777785
Steam Client Build Date: Mon, Oct 30 10:09 PM UTC -08:00
Steam Web Build Date: Fri, Oct 27 7:29 PM UTC -08:00
Steam API Version: SteamClient020
Proton: 1697709592 experimental-8.0-20231019

Steam System Information: https://gist.github.com/EpicureanGit/9e757e37b20ed10eff8271c0112dcf70

Steam Runtime Diagnostics: https://gist.github.com/EpicureanGit/19b9a3ec029894b46dabb793231146d2

Symptoms and Reproduction:
When I click "PLAY" to run Batman Arkham Asylum GOTY Edition, it crashes, and I receive this pop-up window:

Proton_LOG=1 https://gist.github.com/EpicureanGit/c8432164a4c2a21205f7612086e5a061

[vzsolt1981]

With latest Proton Experimental, I have the same issue as @EpicureanGit.

Winetricks is still required to make it run (thanks ProtonDB):
WINEPREFIX="$HOME/.local/share/Steam/steamapps/compatdata/35140/pfx/" WINE="$HOME/.local/share/Steam/steamapps/common/Proton - Experimental/files/bin/wine" winetricks d3dx9 d3dcompiler_43