Extreme performance regression in Diablo 2 Resurrected with latest update(s)


I am primarily an EOS gamer, and since release I played Diablo 2 Resurrected with some friends. Yesterday, after having updated my system in the morning I played some other games, which all went very well. However, when we started playing D2R I noticed extreme performance problems. The game ran with maybe 10 FPS. I tried switching away from the current wine-staging which was updated in the morning, but no change.

Having set up my system with BTRFS for the whole drive and timeshift-autosnap I booted into the morning snapshot before updating, and it ran smooth again. Looking through the packages updated none (with the exception of the mentioned wine-staging) looked gaming-relevant to me. Here’s the list (how it looks now from yay -Syu, I don’t have the list from yesterday morning):

Pakete (74) aom-3.2.0-1  bluedevil-1:5.23.0-1  breeze-5.23.0-1  breeze-gtk-5.23.0-1  doublecmd-qt5-1.0.0-1  drkonqi-5.23.0-1  electron-15.2.0-1  graphviz-2.49.2-1  gst-plugins-bad-1.18.5-2
            gst-plugins-bad-libs-1.18.5-2  htop-3.1.1-1  hwinfo-21.77-2  kactivitymanagerd-5.23.0-1  kde-cli-tools-5.23.0-1  kde-gtk-config-5.23.0-1  kdecoration-5.23.0-1  kdeplasma-addons-5.23.0-1
            kgamma5-5.23.0-1  khotkeys-5.23.0-1  kinfocenter-5.23.0-1  kmenuedit-5.23.0-1  kscreen-5.23.0-1  kscreenlocker-5.23.0-1  ksshaskpass-5.23.0-1  ksystemstats-5.23.0-1  kwallet-pam-5.23.0-1
            kwayland-integration-5.23.0-1  kwayland-server-5.23.0-1  kwin-5.23.0-2  kwrited-5.23.0-1  layer-shell-qt-5.23.0-1  lib32-mesa-21.2.4-1  libkscreen-5.23.0-1  libksysguard-5.23.0-1  libx86emu-3.3-1
            libxmlb-0.3.3-1  mesa-21.2.4-1  milou-5.23.0-1  oxygen-5.23.0-1  plasma-browser-integration-5.23.0-1  plasma-desktop-5.23.0-2  plasma-disks-5.23.0-1  plasma-firewall-5.23.0-1
            plasma-integration-5.23.0-1  plasma-nm-5.23.0-1  plasma-pa-5.23.0-1  plasma-sdk-5.23.0-1  plasma-systemmonitor-5.23.0-1  plasma-thunderbolt-5.23.0-1  plasma-vault-5.23.0-1  plasma-workspace-5.23.0-2
            plasma-workspace-wallpapers-5.23.0-1  polkit-kde-agent-5.23.0-1  powerdevil-5.23.0-1  python-pillow-8.4.0-1  python-pyqt5-5.15.5-1  python-pyqt5-webengine-5.15.5-1  python-qtpy-1.11.2-1
            qt5-base-5.15.2+kde+r243-1  qt5-declarative-5.15.2+kde+r34-1  qt5-svg-5.15.2+kde+r13-1  qt5-wayland-5.15.2+kde+r34-1  qt5-webengine-5.15.6-4  sddm-kcm-5.23.0-1  systemsettings-5.23.0-1
            tzdata-2021d-1  vulkan-tools-1.2.194-1  wayland-utils-1.0.0-2  welcome-3.16.5-1  wine-staging-6.17-1  xapp-2.2.4-1  xdg-desktop-portal-kde-5.23.0-1  yarn-1.22.17-1  yay-11.0.2-1

I checked that KDE hadn’t switched to a wayland backend (which I know doesn’t work very well with my NVidia setup, and wayland was updated):

[dromundkaas@Pure ~]$ env|sort|grep SESSION_TYPE

I looked into GreenWithEnvy and nvidia-smi which both showed the GPU to be at 100%. I’m pretty much lost now on what could tank the performance of this one DX12 title.

Any ideas on how to proceed?

Edit 1: My inxi

System:    Kernel: 5.14.12-arch1-1 x86_64 bits: 64 compiler: gcc v: 11.1.0 Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 
           wm: kwin_x11 vt: 1 dm: SDDM Distro: EndeavourOS base: Arch Linux 
Machine:   Type: Desktop Mobo: Micro-Star model: MAG B550 TOMAHAWK (MS-7C91) v: 2.0 serial: <filter> UEFI: American Megatrends 
           v: A.40 date: 10/29/2020 
CPU:       Info: 8-Core model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3 rev: 0 cache: L2: 4 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 121663 
           Speed: 2058 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 1: 2058 2: 2061 3: 2049 4: 2056 5: 2057 
           6: 3598 7: 2063 8: 2060 9: 2094 10: 2056 11: 2055 12: 3747 13: 2047 14: 2551 15: 2793 16: 2058 
Graphics:  Device-1: NVIDIA GA104 [GeForce RTX 3070] vendor: CardExpert driver: nvidia v: 470.74 bus-ID: 2b:00.0 
           chip-ID: 10de:2484 class-ID: 0300 
           Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: nvidia resolution: 1: 1920x1080~144Hz 
           2: 1920x1080~144Hz s-dpi: 81 
           OpenGL: renderer: NVIDIA GeForce RTX 3070/PCIe/SSE2 v: 4.6.0 NVIDIA 470.74 direct render: Yes 
Audio:     Device-1: NVIDIA GA104 High Definition Audio vendor: CardExpert driver: snd_hda_intel v: kernel bus-ID: 2b:00.1 
           chip-ID: 10de:228b class-ID: 0403 
           Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: Micro-Star MSI driver: snd_hda_intel 
           v: kernel bus-ID: 2d:00.4 chip-ID: 1022:1487 class-ID: 0403 
           Device-3: SteelSeries ApS SteelSeries Arctis 7 type: USB driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-6:5 
           chip-ID: 1038:12ad class-ID: 0300 
           Sound Server-1: ALSA v: k5.14.12-arch1-1 running: yes 
           Sound Server-2: JACK v: 1.9.19 running: no 
           Sound Server-3: PulseAudio v: 15.0 running: yes 
           Sound Server-4: PipeWire v: 0.3.38 running: no 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8168 
           v: 8.049.02-NAPI port: e000 bus-ID: 06:00.0 chip-ID: 10ec:8168 class-ID: 0200 
           IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: N/A port: d000 bus-ID: 2a:00.0 chip-ID: 10ec:8125 
           class-ID: 0200 
           IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:    Local Storage: total: 4.59 TiB used: 1.07 TiB (23.4%) 
           ID-1: /dev/nvme0n1 vendor: Seagate model: XPG GAMMIX S11 Pro size: 1.86 TiB speed: 31.6 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: 32B2T6TA temp: 39.9 C scheme: GPT 
           ID-2: /dev/sda type: USB vendor: Western Digital model: WD30EZRX-00D8PB0 size: 2.73 TiB type: HDD rpm: 5400 
           serial: <filter> scheme: MBR 
Partition: ID-1: / size: 1.83 TiB used: 1.07 TiB (58.7%) fs: btrfs dev: /dev/nvme0n1p2 
           ID-2: /boot/efi size: 299.4 MiB used: 836 KiB (0.3%) fs: vfat dev: /dev/nvme0n1p1 
           ID-3: /home size: 1.83 TiB used: 1.07 TiB (58.7%) fs: btrfs dev: /dev/nvme0n1p2 
Swap:      ID-1: swap-1 type: partition size: 34.48 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 42.8 C mobo: N/A gpu: nvidia temp: 59 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 0% 
Info:      Processes: 359 Uptime: 4h 8m wakeups: 0 Memory: 31.28 GiB used: 5.49 GiB (17.6%) Init: systemd v: 249 Compilers: 
           gcc: 11.1.0 Packages: pacman: 1321 Shell: Bash v: 5.1.8 running-in: yakuake inxi: 3.3.06 

wine / mesa / vulkan / wayland could cause it, how exactly do you play Diablo 2 Resurection?
Is it wine directly, Lutris, Steam?

Also share your

inxi -Fxxxz

It’s a lutris wine prefix, using the Battle.net installer (because at installation time there was no specific D2R install script available and using the Battle.net installer was recommended).

Isn’t Mesa only used when using an AMD card?

Not sure, but i think some stuff from mesa is used with Nvidia too (since i remember Mesa update utterly broken my Manjaro with Nvidia back in a day)

Try https://github.com/GloriousEggroll/wine-ge-custom/releases or https://github.com/Frogging-Family/wine-tkg-git/releases wine engines, see if it helps

It’s still early days for the game, so some weirdness is expected, usually GE / TKG handles new games better since they’re bleeding edge

Thanks for your answer, but for me it looks like wine is not the culprit. As I described, I tested wine-staging and 6.14-2 from Lutris, both showed the same problem, and after switching back wine-staging 6.16 runs it without problems. I cannot find a bug report in the WineHQ regarding D2R, so I would guess it’s not a problem with wine or wine-staging.

I’d still recommend you do that (in portable wine fashion), changing to wine-staging is not an answer, it could help but not likely.

You won’t find it there, almost nobody uses it :upside_down_face:

My guess it’s wine / dxvk because of very early days, next guess the rest of stuff i’ve mentioned before, which is less likely, but possible.

Are you using a joypad?

No, just mouse and keyboard.

Yesterday I did the update again, wanted to try things out, and maybe somebody else had the problem and it was fixed. After upgrading and restarting I tested D2R again. D2R had an update, so maybe that’s the reason, but the performance problems are gone.

Thanks for taking the time and trying to help. Cheers.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.