Maybe this information is helpful for you: https://github.com/HansKristian-Work/vkd3d-proton/issues/890
I recommend you to use latest releases from Proton-GE or Wine-GE (wine-custom for lutris). Also try latest release from vkd3d-proton.
You can debug with winedbg, besides proton and dxvk have environment variables that help you to log process information and errors.
I tried D2R and wine-staging 6.20 + vkd3d-proton too, worked but mediocre FPS so it's better that you stick to the projects I mentioned.
Good luck!
Thanks for the tips :)
Ive performed a wine, lutris & mesa drivers upgrade and rebooted.
seems to be more stable now was able to play on low settings for over 40 min and was very stable.
forgot to look at the FPS rate unfortunate but iGPU seemed to be between 50-80% on the Ryzen 5600g and the game was playable.
Yes i'm using both Wine-GE & Proton-GE (glorious eggroll) and the initial post was base on the latest versions of those libraries at the time.
O an i also upgraded proton as well using "proton-up" so im going to guess that all of the above updates + reboot resolved the issue.
tried D2R and wine-staging 6.20 + vkd3d-proton too, worked but mediocre FPS
Out of curiosity what sort of FPS where you seeing ?
""Cheers
G
With Wine-7.0rc3-GE-1 I've been able to play Diablo II Resurrected at max settings with no real framerate issues. Occasionally I have to change the resolution in settings and this fixes some strange slowdown I've experienced when switching between fullscreen and windowed, and also experienced when dragging between displays.
I can play Diablo II Resurrected at 1440p on my 5700XT with all settings turned up to the maximum. This puts the GPU under about 85-90% load according to MangoHud. The framerate runs at around 90fps with no real drops, though I play it on a 60hz monitor so I usually keep the game capped. I haven't gotten too far in, I'm only around the 5 hour mark, but so far I haven't experienced any major issues - Likely none related to vkd3d-proton.
The issues I have experienced:
Your mileage may vary between distro, DE and hardware though.
System Information:
@velocity08 Friendly ping. Was this issue resolved or do you still have issues?
@velocity08 Friendly ping
@velocity08 Last friendly ping
@Blisto91 I don't think @velocity08 is going to get back to you on this, but I can report the game works great for me with GE-Proton10-34 and the following setup:
OS: Arch Linux x86_64
Kernel: Linux 6.19.12-arch1-1
BIOS (UEFI): 2.A50 (5.41)
Board: MAG B850 TOMAHAWK MAX WIFI (MS-7E62) (2.0)
Init System: systemd 260.1-1-arch
Omarchy: 3.5.1
Omarchy Branch: master
Omarchy Channel: edge
CPU: AMD Ryzen 7 9800X3D (16) @ 5.27 GHz - 46.0°C
GPU 1: AMD Radeon RX 9070 XT (64) @ 2.52 GHz - 39.0°C (1.11 GiB / 15.81 GiB, 7%) [Discrete]
GPU 2: AMD Ryzen 7 9800X3D 8-Core Processor (2) @ 2.20 GHz - 42.0°C (146.81 MiB / 488.15 MiB, 30%) [Integrated]
Memory: 3.54 GiB / 30.40 GiB (12%)
Disk (/): 589.40 GiB / 1.82 TiB (32%) - btrfs
Physical Disk (Samsung SSD 9100 PRO 2TB): 1.82 TiB [SSD, Fixed] - 32.9°C
Display (Panasonic-TV): 3840x2160 in 58", 120 Hz [External]
Display (MAG274QRF-QD): 2560x1440 in 27", 165 Hz [External]
Monitor (Panasonic-TV): 3840x2160 px @ 120 Hz - 1280x720 mm (57.82 inches, 76.20 ppi)
Monitor (MAG274QRF-QD): 2560x1440 px @ 164.835 Hz - 600x340 mm (27.15 inches, 108.18 ppi)
WM: Hyprland 0.54.3 (Wayland)
Vulkan: 1.4.335 - radv [Mesa 26.0.5-arch1.1]
OpenGL: 4.6 (Compatibility Profile) Mesa 26.0.5-arch1.1
OpenCL: clGetPlatformIDs() failed: CL_PLATFORM_NOT_FOUND_KHR
Mesa: mesa 1:26.0.5-1
vulkan-radeon: vulkan-radeon 1:26.0.5-1
libdrm: libdrm 2.4.131-1
linux-firmware: linux-firmware 20260410-1
In general the Proton DB reports are also good when people are running in a cutting edge environment.
Hi All
Currently running the below:
Hardware:
Asrock Mini PC X300
AMD Ryzen 5600g
16 GB 3200 MHz Ram
Dell 4K monitor
Software:
wine-6.20 (Staging)
lutris-0.5.9.1
DVXK 1.92 (latest)
Kernel 5.15.2-051502-generic
KDE Neon all updates and patches applied (Ubuntu 20.04)
Mangohud
Goverlay
Battle.net installed and working
Litrus properties on D2R set to RADV_DEBUG=nohiz (game also launched and played without this entry)
Monitor resolution 4K
Game resolution 4k
In Game resolution set to 50% (default low preset settings)
Diablo 2 resurrected installed and will launch.
Cinematic's play
Game starts all video working as expected
Game play works as expected.
When trying to adjust video resolution from within the game the entire PC crashes and is stuck requiring a hard power cycle.
Changing the resolution can only happen in the game lobby otherwise the PC freezes.
Game can play initially for roughly 10 min then crashes and exits to the battlenet app
can relaunch the game and it will play again for 2 min
subsequent launching of the game also results in 2 min of play.
Similar issue with Diablo III launched from the same Luitris launching of battlenet app.
Wondering if this may be a Kernel issue?
any tips on log dump or other method to gather log info?
Checking Goverlay while playing
thoughts and ideas?
""Cheers
G