I was playing Batman Arkham Asylum up to the part where you save Dr. Young from Zazz and, after the following cutscene, I proceeded to turn around and head towards a wall in the same room that's been discovered to be destructible if you attempt to blow it up enough times, revealing a room. However, in my attempt to do so, the game froze and threw a "General Protection Fault" error thereby crashing the game after interacting with it.
I'm not sure how or why this was triggered, and the Proton log doesn't seem very descriptive of the issue at all, as far as I can tell... :/
The only other indication I can give at the moment was what my game settings were, and the other logs that might be involved; hopefully this information can help track down this odd behavior:
This specific issue happens on all Batman Arkham games with wine/proton, seemingly randomly. Usage of mods/nvapi addons might make the issue easier to trigger, but there is no fix for this right now.
Related? (Unsure, but probably not)
Screenshot:
Proton version:
proton-tkg-7.5.r5.gf0719cee
proton-tkg.cfg.zip steam-35140.zipWinetricks/Protontricks verbs used:
d3dx9 d3dcompiler_43 physx
(Was placed in the game's binary directory) dxvk.conf.zip
Launch options:
PROTON_LOG=1 PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_NO_ESYNC=1 PROTON_USE_D9VK=1 %command%
The Batman Arkham Asylum Reborn texture pack was installed
Description:
PhysXDevice.dll
from Batman Arkham City into Arkham Asylum's binary folder allows support for properly working PhysX for the gameI was playing Batman Arkham Asylum up to the part where you save Dr. Young from Zazz and, after the following cutscene, I proceeded to turn around and head towards a wall in the same room that's been discovered to be destructible if you attempt to blow it up enough times, revealing a room. However, in my attempt to do so, the game froze and threw a "General Protection Fault" error thereby crashing the game after interacting with it.
I'm not sure how or why this was triggered, and the Proton log doesn't seem very descriptive of the issue at all, as far as I can tell... :/
The only other indication I can give at the moment was what my game settings were, and the other logs that might be involved; hopefully this information can help track down this odd behavior:
ShippingPC-BmGame_d3d9.log ShippingPC-BmGame_dxvk_config.log ShippingPC-BmGame_dxgi.log
(The community open-source launcher was used) (Try to ignore the odd-colored fonts, I couldn't fix them due to a pending issue)
BmLauncher_dxgi.log