Hello @sTiKyt, Proton uses DXVK to translate DirectX 11 to Vulkan, and that error dialog along with err:vulkan:__wine_create_vk_instance_with_callback Failed to create instance, res=-1 in your log is telling us that the Vulkan render path is failing to initialize.

This is most likely a video driver issue of some kind, which would show in the extended diagnostics section of your system information, but unfortunately, you have copied that before Steam was able to complete gathering it.

Thanks, we've seen AMDVLK interfere with other Vulkan drivers before. Can you try removing the lib32-amdvlk system package and see if that has an effect NVIDIA's 32 bit Vulkan render path?

Against the Storm (1336490)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7368.
@mothringer posted on 2023-12-22T16:39:26:

Compatibility Report

• Name of the game with compatibility issues: Against the Storm
• Steam AppID of the game: 1336490

System Information

• GPU: RTX 3080
• Video driver version: Nvidia 535.146.02
• Kernel version: 6.1.68-gentoo-x86_64
• Link to full system information report as Gist: https://gist.github.com/mothringer/3153d5d446779a6e0f2369cfccb4c60c
• Proton version: Experimental, but happens on every version that I tried

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-1336490.log

Symptoms

Game hangs on last frame of publisher logo video at startup, with a stack overflow shown in the proton log.

Reproduction

Happens at every startup

Hello @Malchior95, can you check two details.

First, if you run the game with Proton 9.0, then from a terminal run nvidia-smi, is the game listed in the processes section. This is to verify the game is running on your NVIDIA GPU.

Second, while you're seeing the low framerate, open NVIDIA's GUI settings application and look for a PCIe Bandwidth Utilization percentage readout. Low percentages are healthy, high percentages are a hint that VRAM maxed out and part of the render hot path got bumped to system ram.

Against the Storm (1336490): uncached battery sysfs reads in ntdll cause ~82 ms main-thread stall every ~1 s on laptops with slow embedded controllers

Issue transferred from https://github.com/ValveSoftware/Proton/issues/9949.
@johndphipps-design posted on 2026-07-05T16:33:33:

Compatibility Report

• Name of the game with compatibility issues: Against the Storm
• Steam AppID of the game: 1336490

System Information

• GPU: NVIDIA RTX 3070 Mobile (hybrid with AMD Cezanne iGPU)
• Video driver version: NVIDIA 580.159.04
• Kernel version: 7.0.12 (Fedora 43)
• Link to full system information report: https://gist.github.com/johndphipps-design/440efe100d0476da69f0c1d39c7a8b48
• Proton version: GE-Proton10-34 (reproduced on multiple Proton versions; root
  cause verified present in current upstream Wine, see below)

Issue description

The game polls Windows battery status (GetSystemPowerStatus /
NtPowerInformation(SystemBatteryState)) ~46×/s from its main thread — it is a
Unity 2021 title and Unity exposes SystemInfo.batteryStatus.

Wine answers every call by re-reading /sys/class/power_supply/* — see
fill_battery_state() in dlls/ntdll/unix/system.c (current upstream master,
~line 4347): opendir + per-attribute reads of type/status/voltage_now/
charge_full/charge_now on each call, no caching. Windows answers this API from
cached data.

The Linux ACPI battery driver caches attribute values for 1 s
(/sys/module/battery/parameters/cache_time = 1000 default). Once per second
one read misses that cache and performs a synchronous embedded-controller
query. On this laptop (Lenovo IdeaPad, Ryzen 7 5800H) that query takes ~66 ms
with the game's main thread blocked:

read of BAT0/energy_now after cache expiry: 66.1 ms
immediate cached re-read:                    0.093 ms

Result: an ~82 ms frame spike every ~1.07 s (1 s kernel cache + 66 ms stall +
frame catch-up), i.e. a metronomic stutter for the whole play session.
MangoHud frametime logs: median spike 82 ms, median interval 1.071 s, ~100
spikes per 90 s. strace shows the main thread blocked ~65 ms in read() of
/sys/class/power_supply/ADP0/online, BAT0/* on the same period.

Not reproducible on native Windows (API is cached there) or on desktops
(no battery to read), which makes it look like a game/hardware problem —
it is likely underdiagnosed among laptop players. Main menu is unaffected
(no battery polling there), gameplay is affected from the first second.

Confirmed workaround

echo 600000 > /sys/module/battery/parameters/cache_time removes the stutter
completely (verified with frametime logs). Suggested proper fix: cache battery
state in ntdll for a few seconds, or refresh it off the calling thread.

Per-game workaround (auto-toggle via Steam launch options)

To avoid leaving the long cache system-wide, the following applies it only
while the game runs and restores the default on exit (including crashes):

Root-owned helper /usr/local/bin/battery-cache-set (validates input,
can only write this one file):

#!/bin/bash
if [[ "$1" =~ ^[0-9]{3,7}$ ]]; then
    echo "$1" > /sys/module/battery/parameters/cache_time
else
    echo "usage: battery-cache-set <milliseconds>" >&2
    exit 1
fi

Sudoers rule (file in /etc/sudoers.d/, mode 440, replace YOURUSER):

YOURUSER ALL=(root) NOPASSWD: /usr/local/bin/battery-cache-set

User wrapper script (executable, anywhere in your home):

#!/bin/bash
restore() { sudo -n /usr/local/bin/battery-cache-set 1000; }
trap restore EXIT
sudo -n /usr/local/bin/battery-cache-set 600000
"$@"

Steam launch options for the game:

/path/to/wrapper %command%

Note: while the long cache is active, desktop battery percentage and
low-battery warnings update lazily between AC plug/unplug events.

Reproduction

1. Laptop whose EC battery query is slow (measure: read a BAT*/energy_now or
   charge_now attribute twice, >1 s apart, and time the reads).
2. Launch Against the Storm under any Proton, load a settlement.
3. Observe frametime graph: ~80 ms spike every ~1 s.

MangoHud frametime CSVs (before / after workaround) and system information:
https://gist.github.com/johndphipps-design/440efe100d0476da69f0c1d39c7a8b48
strace captures available on request.