World of Warcraft: Forever

protonclosed Game compatibility - Unofficial

ValveSoftware/Proton#10156 · opened 2026-09-18 by yak3d · updated 2026-09-18 · 1 comments · github

Yyak3d 2026-09-18 github

Compatibility Report

yak3d · 2026-09-18T00:01:22Z

# Compatibility Report - Name of the game with compatibility issues: World of Warcraft: Forever - Steam AppID of the game: N/A ## System Information - GPU: NVIDIA RTX 5090 - Video driver version: nvidia 615.71.09 - Kernel version: 7.2 - Link to full system information report as [Gist](https://gist.github.com/): - Proton version: 11 ## 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. ## Symptoms - `PROTON_LOG=1` causes extremely poor performance once logged into the game, even at low settings you can't get above single digit FPS - I'd attach the file but its literally 12.5 gb, however in a 200mb sample there were the following # of log statements ``` 1,979,676 trace:unwind:dump_unwind_info 247,741 trace:unwind:RtlVirtualUnwind2 11,311 trace:seh:RtlCaptureStackBackTrace 3,861 trace:seh:NtGetContextThread ``` My hunch is that this is because its a beta build, but I wanted to log it for future reference. I can't attach the log file given the size. ## Reproduction 1. Set `PROTON_LOG=1` 2. Start the game, create a character and login 3. Observe framerate, it should crater

Name of the game with compatibility issues: World of Warcraft: Forever
Steam AppID of the game: N/A

System Information

GPU: NVIDIA RTX 5090
Video driver version: nvidia 615.71.09
Kernel version: 7.2
Link to full system information report as Gist:
Proton version: 11

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.

Symptoms

PROTON_LOG=1 causes extremely poor performance once logged into the game, even at low settings you can't get above single digit FPS
I'd attach the file but its literally 12.5 gb, however in a 200mb sample there were the following # of log statements

1,979,676  trace:unwind:dump_unwind_info
  247,741  trace:unwind:RtlVirtualUnwind2
   11,311  trace:seh:RtlCaptureStackBackTrace
    3,861  trace:seh:NtGetContextThread

My hunch is that this is because its a beta build, but I wanted to log it for future reference. I can't attach the log file given the size.

Reproduction

Set PROTON_LOG=1
Start the game, create a character and login
Observe framerate, it should crater

Kkisak-valve maintainer 2026-09-18 github

Hello @yak3d, in general, noisy Proton logs and the overhead of writing the log is within expectations, and the performance impact from it is why we have logging off by default.

With #10157 coming in right behind this issue report with significantly more feedback related to the game, I'm left with a choice to either transfer all that feedback here or to close out this issue report and use the newer issue report as the one place to track feedback on the game. Since it's less disruptive to do the latter, I'm going to take that option.

For anyone coming across this issue report, please add your experience with the game to #10157.

Launch options

PROTON_LOG=1x1 2026-09