Path of Exile (238960)

[DataBeaver]

It gives a dialog saying "Failed to create WIC factory" followed by a bunch of reference count errors. The behaviour matches this bug in the Wine bug tracker.

[ernstp]

The game comes further with DX9 but then has a lot of other issues, and bad performance.
From the winehq.org bug it looks like there's only very small changes needed to get the DX11 version running fine!

[DataBeaver]

It runs with DX9 but performance is indeed bad and it crashes frequently. In one hour-long session I had it crash four or five times. I've tried getting the DX11 version work on Wine and DXVK but after applying that CoInitialize patch it freezes at a black screen on startup. I was hoping Proton might do something differently and make it work.

[dumpsters]

According to this it only needs one line change in wine nowadays, not sure how much it affects other games

[tainium]

Note that PoE isn't whitelisted so I doubt if we get any official support just yet.

I was recently ironing out a process to get PoE running for more people and posted those steps here

The gist is that PoE runs great with DX11 (DXVK) with a shader patch. Right now Proton is just running it in DX9 mode that doesn't work for very many people. We need to dig into this new configuration they've provided and figure out how to get DXVK enabled and how to inject custom patches.

[DataBeaver]

I realize it isn't whitelisted but was hoping to raise interest in the game by opening the issue. Maybe if we can figure out the problem here it will result in the game being whitelisted sooner.

PoE does not run great with DX11 for me. In fact it does not run at all. The furthest I've got is avoiding all the outright crashes on startup, but the game only hangs at a black screen (it actually only renders a single black frame), eating 100% of CPU time. I don't know if it's trying to load something in the background but even after an hour of waiting it hasn't gotten anywhere. Using Lutris, PlayOnLinux or plain Wine does not make a difference. The DXVK async patch does not make a difference. Trying to use Wine's builtin D3D 11 implementation errors out with "Failed to create deferred context".

I've tried using WINEDEBUG, DXVK_LOG_LEVEL, even gdb, but so far I'm completely clueless about what's wrong. If you have any ideas for what I should check I'd love to hear it.

[tainium]

@DataBeaver What is your OS, graphics card model and graphics card driver version?

[DataBeaver]

Debian unstable, GTX 980, 396.51. The Lutris DXVK howto mentions that 396.45 is missing a Vulkan extension; I figured if that was the case with this version as well, DXVK would simply fail to initialize. I've tried a few different builds of Wine 3.13 and 3.14, both staging and not. Staging does not seem to make a difference as long as the CoInitialize patch is present.

[tainium]

@DataBeaver That is a Maxwell chip that supports Vulkan & DX11 so there's likely a software/configuration problem somewhere. Are you using a version of the driver that comes with the NVIDIA control panel? If so, does it indicate any problems?

[DataBeaver]

You mean nvidia-settings? I have it installed and can't find any problem indicators. I can also successfully run vkmark (https://github.com/vkmark/vkmark) so Vulkan appears to be working.

[edmondo]

My experience with PoE DX11 (AMD Radeon RX470) and wine is very good with following prerequisites applied:

• Must have: WIC patch (CoInitialize)

• Variant 1: DXVK 0.70 - strong shader compilation stuttering at first until cache ready, but then very stable and good performance (with occasional shader compilation when entering new areas)

• Variant 2: Patched DXVK 0.65 with shader hack (https://github.com/jomihaka/dxvk-poe-hack) to avoid stuttering - some glitches and flickering during compilation but no stuttering and good performance
  DXVK_USE_PIPECOMPILER=1 DXVK_USE_PLACEHOLDER_SHADERS=1 DXVK_HUD=1 WINEPREFIX=/mnt/storage/wine/poe wine64-staging-3.13 PathOfExile.exe --nologo

I could be interesting to port the hack to the new DXVK 0.70 config system and maybe allow to activate it for very stuttering games when no cache is ready.
EDIT: Or a much better and simpler implementation as suggested here doitsujin/dxvk#564 (comment)

[DataBeaver]

I downloaded the Unigine Heaven benchmark (https://benchmark.unigine.com/heaven) and it works with both DXVK and Wine's builtin D3D 11 support. So whatever the issue with Path of Exile is, it seems to be specific enough to affect only some programs but not others.

[DataBeaver]

By applying the patchset d3d11-Deferred_Context from wine-staging Wine's builtin D3D 11 implementation now behaves the same way as DXVK. In other words, it hangs on a black screen at startup.

[DataBeaver]

After yet more staring at logs and scouring the web I found out that the windowscodecs-* patches from wine-staging are also necessary. The game now launches up to the login screen at least, with both DXVK and Wine's D3D 11. I'll report when I've had time to actually play it and test stability and performance.

Why the Lutris approach didn't work for me when it does for many others is still a mystery.

[jaccarmac]

I don't even get the dialog to pop, and DX11 should be possible to use based on my LLVM install.

I ran PoE under regular old Wine a couple years back, but it involved a lot of tweaking. Excited to figure out how to get it working again inside Proton.

[ernstp]

Let's not turn this into a support forum for PoE on all different versions of Wine. This is about Proton...

[DataBeaver]

I didn't have a lot of time to test stability yet but I ran a few maps and didn't see any problems.

I did some more investigation to find the minimal set of changes required to get the game working. It boils down to this (with Wine 3.14 as a starting point):

1. The CoInitialize patch. I created my own version which handles the call in a smarter way: https://gist.github.com/DataBeaver/5e1f1a256c7f1abb339831fc2b72a5db

2. windowscodecs-32bppPRGBA from wine-staging. It pulls in most of the other windowscodecs-* patches as dependencies, but I verified the game does not work without this particular patchset.

3. DXVK. Wine's own D3D 11 lacks support for deferred contexts, but using DXVK bypasses this issue. The placeholder shader hack is optional.

Looking at the Wine source tree included in Proton as a submodule, it does not include either the CoInitialize or windowscodecs patches. The base Wine version is fairly old (3.0-rc1 according to git tags) so I don't know if something else would be required on that version as well. DXVK is included and although it's version 0.65 I have no reason to believe it wouldn't work.

[c0r73x]

I downloaded the proton source and applied the patches that @DataBeaver is talking about. After the CoInitialize and windowscodec patches the game works flawlessly with DX11. However the 0002 winecodec patch failed but after applying it manually it wasn't a problem.

[GregSutcliffe]

@c0r73x any chance you could share your Proton dist build? I'm trying to build it with the PoE patches myself, but I'm hitting build errors with winegcc...

[c0r73x]

@GregSutcliffe sure, here it is https://mega.nz/#!3253ECqJ!WViplmIgM6FNDSJwnsWFJwEXUUY3_Qzm1c1LVYGfSJ8

[GregSutcliffe]

@c0r73x thanks, I can confirm that works for me too. Appreciated!

[tainium]

@c0r73x Thanks for sharing! Makes testing easy.

Unfortunately that build is only partially successful for me.

PoE will load and run with DX11 (DXVK) now, but the coinitialize patch isn't working as well as the old replacement shaders patch. I get lots of stuttering and freezing with this in Steam, whereas the shader patch has PoE running near flawlessly in Lutris+DXVK for me.

EDIT: Tried again with different driver version but still no luck with the shader stuttering. I'm also getting some odd graphics behavior with the in-game item filter and atlas now.

EDIT: The other version (shader patch + DXVK + Lutris) is otherwise still working great for me. I can't figure out why the Proton configuration has such worse performance.

[c0r73x]

@tainium did you try to disable steam overlay?

[tainium]

@c0r73x Yes.

[c0r73x]

@tainium Ok, I applied the shader patch to dxvk in proton and you are right. The game runs much better with it. The microstutter form playing necro with alot of pets is gone :p

Here is the patched dxvk files if anyone wants it https://mega.nz/#!nnBylIpB!0KNQwsTf48V861IoFGPBtbZ_sZtX4LRDSA3FdEampnM

[tainium]

@c0r73x Thanks for the new patch, will test it ASAP. Yeah, its like the coinitialize patch definitely enables DXVK and better performance than without it, but the full shader patch takes performance a step up.

[GregSutcliffe]

@c0r73x Confirmed, that's a huge improvement - thanks! Since you have builds working, any chance you could comment on #494? Then I can stop bugging you for builds :)

[rgehlen]

The mesa version is actually 21.2.3, I copied the version from the wrong container by mistake.

https://gist.github.com/38aa635eca0a68d435aa473af9b3266f

Edit: Updated to mesa 21.2.4, no change.

[edmondo]

I can reproduce the black square cursor issue with Proton Experimental (19.10.2021).

With Proton 6.3-7 the cursor looks fine.

[anders-larsson]

Hello. I can add that the mouse cursor has turned into a black block for me as well. It was working correctly before (earlier this league).

• GPU: Nvidia GTX 1070
• Driver: nvidia-drivers 495.29.05
• Kernel version: 5.14.10
• Proton version: Current Experimental

It helps to switch to 6.3-7.

[edmondo]

With today Proton Experimental update the black block cursor issue is fixed on my configuration (RX 470).
Thanks.

[wastedcoffeecup]

After recent updates, Path of Exile crashes frequently during game play. According to PROTON_LOG information the crashes all occur during the same function. This can be seen in the back traces located at the end of the crash logs below.

Crash logs:
202206111200-steam-238960.log
202206110924-steam-238960.log
202206110754-steam-238960.log

System Information:

System:
  Host: c-box Kernel: 5.17.5-76051705-generic x86_64 bits: 64 compiler: gcc
    v: 11.2.0 Desktop: GNOME 42.1 Distro: Pop!_OS 22.04 LTS
    base: Ubuntu 22.04 LTS Jammy
Machine:
  Type: Desktop Mobo: ASRock model: AB350 Gaming K4
    serial: <superuser required> UEFI-[Legacy]: American Megatrends v: P5.40
    date: 12/19/2018
CPU:
  Info: 8-core model: AMD Ryzen 7 1800X bits: 64 type: MT MCP arch: Zen
    rev: 1 cache: L1: 768 KiB L2: 4 MiB L3: 16 MiB
  Speed (MHz): avg: 2075 high: 3034 min/max: 2200/3600 boost: enabled
    cores: 1: 1836 2: 1870 3: 1853 4: 1827 5: 1830 6: 1846 7: 2790 8: 3034
    9: 2527 10: 2752 11: 1903 12: 1826 13: 1846 14: 1849 15: 1845 16: 1771
    bogomips: 114967
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1080] vendor: eVga.com. driver: nvidia
    v: 510.73.05 bus-ID: 26:00.0
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia resolution:
    1: 1920x1080~60Hz 2: 1920x1080~60Hz
  OpenGL: renderer: NVIDIA GeForce GTX 1080/PCIe/SSE2
    v: 4.6.0 NVIDIA 510.73.05 direct render: Yes
Audio:
  Device-1: NVIDIA GP104 High Definition Audio vendor: eVga.com.
    driver: snd_hda_intel v: kernel bus-ID: 26:00.1
  Device-2: AMD Family 17h HD Audio vendor: ASRock driver: snd_hda_intel
    v: kernel bus-ID: 28:00.3
  Sound Server-1: ALSA v: k5.17.5-76051705-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: no
  Sound Server-3: PipeWire v: 0.3.51 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASRock driver: r8169 v: kernel port: d000 bus-ID: 25:00.0
  IF: enp37s0 state: up speed: 1000 Mbps duplex: full
    mac: 70:85:c2:42:3a:e1
  IF-ID-1: virbr0 state: down mac: 52:54:00:7d:85:ab
Drives:
  Local Storage: total: 1.56 TiB used: 214.2 GiB (13.4%)
  ID-1: /dev/sda vendor: Toshiba model: TR150 size: 223.57 GiB
  ID-2: /dev/sdb vendor: Crucial model: CT1000BX500SSD1 size: 931.51 GiB
  ID-3: /dev/sdc vendor: A-Data model: SU650 size: 447.13 GiB
Partition:
  ID-1: / size: 215.06 GiB used: 30.62 GiB (14.2%) fs: ext4 dev: /dev/sda1
  ID-2: /home size: 915.82 GiB used: 182.69 GiB (19.9%) fs: ext4
    dev: /dev/sdb1
Swap:
  ID-1: swap-1 type: partition size: 4 GiB used: 915.2 MiB (22.3%)
    dev: /dev/dm-0 mapped: cryptswap
Sensors:
  System Temperatures: cpu: 36.0 C mobo: N/A gpu: nvidia temp: 47 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
  Processes: 412 Uptime: 2d 17h 37m Memory: 15.62 GiB used: 4.56 GiB (29.2%)
  Init: systemd runlevel: 5 Compilers: gcc: 11.2.0 Packages: 2751 Shell: Bash
  v: 5.1.16 inxi: 3.3.13

[kisak-valve]

Can't start Path of Exile anymore after switching from nVidia to AMD

Issue transferred from #6358.
@x0r13 posted on 2022-12-02T01:43:15:

Proton Version: 7.04

[System]
OS:              Ubuntu 20.04 focal
Arch:            x86_64
Kernel:          5.4.0-132-lowlatency
Desktop:         Budgie:GNOME
Display Server:  x11

[CPU]
Vendor:          AuthenticAMD
Model:           AMD Ryzen 7 1700 Eight-Core Processor
Physical cores:  8
Logical cores:   16

[Memory]
RAM:             15.6 GB
Swap:            3.8 GB

[Graphics]
Vendor:          AMD
OpenGL Renderer: AMD Radeon RX 6600 (dimgrey_cavefish, LLVM 14.0.1, DRM 3.46, 5.4.0-132-lowlatency)
OpenGL Version:  4.6 (Compatibility Profile) Mesa 22.1.0-devel
OpenGL Core:     4.6 (Core Profile) Mesa 22.1.0-devel
OpenGL ES:       OpenGL ES 3.2 Mesa 22.1.0-devel
Vulkan:          Supported

I recently switched from a nVidia 1060 6GB to a rx6600 AMD GPU. I uninstalled the nVidia drivers via the installer (./installer --uninstall) and then installed the amdgpu package. I can play CS:GO fine via steam, also Diablo II Resurrected via a manual wine installation.

However when trying to start my installation of Path of Exile via Steam using proton 7.0.4 (over 500h with the nVidia card) nothing happens. It just says "Running" for a moment, then the button changes back to "Play".

I tried running it manually via:
STEAM_COMPAT_CLIENT_INSTALL_PATH=~/.local/share/Steam/ STEAM_COMPAT_DATA_PATH=~/.steam/steam/steamapps/compatdata/238960 '~/.steam/steam/steamapps/common/Proton 7.0/proton' run '~/.steam/steam/steamapps/common/Path of Exile/PathOfExileSteam.exe'

but it instantly crashes:

*** stack smashing detected ***: terminated
Aborted (core dumped)

Checking the crash dump shows:

Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50\t../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) br
Breakpoint 1 at 0x7fdfacbfc00b: file ../sysdeps/unix/sysv/linux/raise.c, line 50.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007fdfacbdb859 in __GI_abort () at abort.c:79
#2  0x00007fdfacc4626e in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fdfacd7008f "*** %s ***: terminated\
") at ../sysdeps/posix/libc_fatal.c:155
#3  0x00007fdfacce8aba in __GI___fortify_fail (msg=msg@entry=0x7fdfacd70077 "stack smashing detected") at fortify_fail.c:26
#4  0x00007fdfacce8a86 in __stack_chk_fail () at stack_chk_fail.c:24
#5  0x00007fdfacd199b4 in __GI__dl_catch_exception (exception=exception@entry=0x0, operate=operate@entry=0x7fdfacdf22d0 <call_dl_init>, args=args@entry=0x7ffef202c990) at dl-error-skeleton.c:219
#6  0x00007fdfacdf30cf in dl_open_worker (a=a@entry=0x7ffef202cb40) at dl-open.c:758
#7  0x00007fdfacd19928 in __GI__dl_catch_exception (exception=exception@entry=0x7ffef202cb20, operate=operate@entry=0x7fdfacdf2c20 <dl_open_worker>, args=args@entry=0x7ffef202cb40) at dl-error-skeleton.c:208
#8  0x00007fdfacdf260a in _dl_open (file=0x7fdfabefd050 "libGLX_nvidia.so.0", mode=-2147483646, caller_dlopen=<optimized out>, nsid=-2, argc=4, argv=0x7ffef202db88, env=0x7ffef202dbb0) at dl-open.c:837
#9  0x00007fdfacb9134c in dlopen_doit (a=a@entry=0x7ffef202cd60) at dlopen.c:66
#10 0x00007fdfacd19928 in __GI__dl_catch_exception (exception=exception@entry=0x7ffef202cd00, operate=operate@entry=0x7fdfacb912f0 <dlopen_doit>, args=args@entry=0x7ffef202cd60) at dl-error-skeleton.c:208
#11 0x00007fdfacd199f3 in __GI__dl_catch_error (objname=objname@entry=0x2666c30, errstring=errstring@entry=0x2666c38, mallocedp=mallocedp@entry=0x2666c28, operate=operate@entry=0x7fdfacb912f0 <dlopen_doit>, 
    args=args@entry=0x7ffef202cd60) at dl-error-skeleton.c:227
#12 0x00007fdfacb91b59 in _dlerror_run (operate=operate@entry=0x7fdfacb912f0 <dlopen_doit>, args=args@entry=0x7ffef202cd60) at dlerror.c:170
#13 0x00007fdfacb913da in __dlopen (file=<optimized out>, mode=<optimized out>) at dlopen.c:87
#14 0x00007fdfacdc8ad1 in ?? () from /usr/lib/python3.8/lib-dynload/_ctypes.cpython-38-x86_64-linux-gnu.so
#15 0x00000000005f69ca in PyCFunction_Call ()
#16 0x00000000005f74f6 in _PyObject_MakeTpCall ()
#17 0x0000000000570d55 in _PyEval_EvalFrameDefault ()

So, it looks like it somehow tries to load libGLX_nvidia.so.0 even though the nVidia driver has been removed, and other games run well using the rx6600. Any idea what the problem is and how to solve it?

[kisak-valve]

Hello @x0r13, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

[x0r13]

content of steam-238960.log

======================
Proton: 1660576899 proton-7.0-4
SteamGameId: 238960
Command: ['/home/xxx/.steam/steam/steamapps/common/Path of Exile/PathOfExileSteam.exe', '--nopatch']
Options: {'forcelgadd'}
depot: 0.20221018.74
pressure-vessel: 0.20221014.0
scripts: v0.20220823.0-0-gcc4e44f
soldier: 0.20221017.1 soldier 0.20221017.1
Kernel: Linux 5.4.0-135-lowlatency #152-Ubuntu SMP PREEMPT Wed Nov 23 21:01:58 UTC 2022 x86_64
======================

Nothing more is logged there.

Sys info from steam is here: System info

[x0r13]

Update: After checking my own syslog, I realized that there are a lot of old driver leftovers under /usr/lib/i386-linux-gnu/ and /usr/lib/x86_64-linux-gnu/ - mostly from nv installer 390.116. After manually deleting all those, the game started just fine and runs perfectly well now.

So if anyone else runs into that issue after switching from nVidia to AMD, it might be worth a shot to look for those old driver leftovers.

[kisak-valve]

Glad to hear you got it working. That issue is being tracked at ValveSoftware/steam-runtime#420.

[kisak-valve]

Path of Exile (238960) : random POE and steam closure

Issue transferred from #6677.
@feydreva posted on 2023-04-10T21:00:59:

Compatibility Report

• Name of the game with compatibility issues: Path Of Exile
• Steam AppID of the game: 238960

System Information

• GPU: AMD Radeon RX 6600 XT
• Driver/LLVM version: Mesa 23.0.1
• Kernel version: 6.2.8-zen1-1-zen (64-bit)
• Link to full system information report as Gist:https://gist.github.com/feydreva/03a852ee2ce24e8986841ee63a71ced0
• Proton version: Proton Experimental

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

steam-238960.log

Symptoms

When playing game, game randomly crash.
it happened once in Hideout, once in Maps, when entering a zone in the campaign. (it happend after entering my hideout, after few second of play when I took the log)

game closes, and steam shuts down and close properly.

Reproduction

Open stay, play path of exile and wait it happens.

Thank you fr your help

[feydreva]

after looking around, it seems to be an issue with baloo.
After suspending baloo, not more issue.

[Tipcat-98]

Hey, while trying to run Path of Exile with Proton 8 my game hangs when in the loading screen when trying to enter a zone/map.
Character select works fine.
Proton 7 and GE-Proton plays the game fine on my system.

EDIT:
It seems the issue is related to loading the act 10 hub "Oriath Docks", as creating a new character successfully loads the tutorial area.
The Act 4 hub - "Overseer's Tower" gives me the same issue.

System Info
CPU: Intel i7 6700
GPU: NVIDIA GeForce RTX 2060
Kernel: 6.2.6

steam-238960.log

[garpu]

Same for me, except I'm on the Karui shores. I was able to play yesterday morning on Proton 8, so this might be related to the patch yesterday?

steam-238960.log

System info: (wrong soundcard reported, it's an M-Audio delta 1010LT) https://gist.github.com/garpu/be09f7f57f8271200b44cecbbe712978

[ernstp]

I could often play for 15 minutes or so with Proton 8 but then the game would hang. No crash, music still playing, but minimal CPU usage and not responding. Reverting to Proton Experimental seems to have fixed it.

[Turmfalke2]

Can confirm the crash to desktop when loading in while using Proton 8. Is there a list of releases? So we can test which one exactly introduced the issue?

[Turmfalke2]

Can't reproduce the crash right now, now it just freezes? Proton_log attached.

...
19125.336:0134:0160:err:sync:RtlpWaitForCriticalSection section 00000000009400D0 "../src-wine/dlls/ntdll/heap.c: main process heap section" wait timed out in thread 0160, blocked by 0158, retrying (60 sec)
19125.336:0134:015c:err:sync:RtlpWaitForCriticalSection section 00000000009400D0 "../src-wine/dlls/ntdll/heap.c: main process heap section" wait timed out in thread 015c, blocked by 0158, retrying (60 sec)
19125.336:0134:0154:err:sync:RtlpWaitForCriticalSection section 00000000009400D0 "../src-wine/dlls/ntdll/heap.c: main process heap section" wait timed out in thread 0154, blocked by 0158, retrying (60 sec)
19125.336:0134:0138:err:sync:RtlpWaitForCriticalSection section 00000000009400D0 "../src-wine/dlls/ntdll/heap.c: main process heap section" wait timed out in thread 0138, blocked by 0158, retrying (60 sec)

steam-238960.log

[TrueNeutralDesu]

Replying to #58 (comment)

For me game crashes on loading first location (login and character select screens work) when I use Proton Experimental, with Proton 8 it just hangs.

[BIGFAAT]

It seems that the crashes are related of using build in vulkan. Switching to dx12 and so using dxvk fixed all the crashes for me. In the process i lost ~20 max fps but the low 1% and 0.1% got significantly much better.

Running the game on a 2700x with a vega 64, latest zen kernel on arch. Swaping proton versions between 7, 8, ex and ge, or using wayland or x11 didnt matter.

[kisak-valve]

Path of Exile (238960) crash

Issue transferred from #6780.
@Steamvoker posted on 2023-05-17T06:27:13:

Compatibility Report

• Name of the game with compatibility issues: Path of Exile
• Steam AppID of the game: 238960

System Information

• GPU: RTX 4090
• Driver/LLVM version: nvidia 530.41.03
• Kernel version: 6.3.2-arch1-1
• Link to full system information report as Gist:
• Proton version: 7.0-6, 8.0-2, experimental

I confirm:

• [:heavy_check_mark: ] that I haven't found an existing compatibility report for this game.
• [:heavy_check_mark: ] that I have checked whether there are updates for my system available.

steam-238960.log

Symptoms

Game crashes.

Reproduction

1. Open options.
2. In the UI tab check the "Hide login email".

[AlexandreBonneau]

Path of Exile (Trials of the ancestors) just crashed after loading my third character (for which I need to change the name (haven't logged since 2019), with the following Vulkan error:

This is using the latest Proton version as of today.
I was unfortunately not able to reproduce the bug so far.

[NicTanghe]

I`ve had 0 problems

[kisak-valve]

Steam Linux | Path of Exile | Proton 8+ | comctl32.dll failed to initialize | Works with Proton 7

Issue transferred from #7278.
@freddiehaddad posted on 2023-11-22T14:12:32:

Compatibility Report

• Name of the game with compatibility issues: Path of Exile
• Steam AppID of the game: 238960

System Information

• GPU: RX 7900 XTX
• Video driver version: Mesa 23.2.1
• Kernel version: 6.6.2
• Link to full system information report as Gist:
• Proton version: 8 and Experimental

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

40892.597:0124:0128:err:module:LdrInitializeThunk "COMCTL32.dll" failed to initialize, aborting
40892.597:0124:0128:err:module:LdrInitializeThunk Initializing dlls for L"Z:\\\home\\\\freddiehaddad\\\\.local\\\\share\\\\Steam\\\\steamapps\\\\common\\\\Path of Exile\\\\PathOfExileSteam.exe" failed, status c0000005

https://gist.github.com/freddiehaddad/388bd33e062682a63ff0964ea78ef8e7

Symptoms

Game fails to start using Proton 8 and Proton Experimental, works with Proton 7.

Launch Options:

PROTON_LOG=1 WINEDLLOVERRIDES="version.dll=n,b" %command%

Reproduction

1. Install Path of Exile via steam
2. Change launch options for game to:

   PROTON_LOG=1 WINEDLLOVERRIDES="version.dll=n,b" %command%

3. Download: https://github.com/RoseTheFlower/UltrawideIndex/releases/download/pathofexile/Path.of.Exile.Ultrawide.v1.1.zip
   1. Unzip archive to game directory.

   2. unzip ~/downloads/Path.of.Exile.Ultrawide.v1.1.zip -d ~/.local/share/Steam/steamapps/common/Path\ of\\ Exile/
      

4. Attempt to launch game using Proton Experiment or Proton 8, game will not launch and logs will show the comctl32.dll error.
5. Switch to Proton 7 and game will launch.

[ghen-arcanum]

steam-238960.log
Game launches for me fine on proton experimental but
Since 3.23 i'm experiencing freeze loading for 1 second which makes the game nearly unplayable:

[AlexandreBonneau]

Path of Exile (Trials of the ancestors) just crashed after loading my third character (for which I need to change the name (haven't logged since 2019), with the following Vulkan error: This is using the latest Proton version as of today. I was unfortunately not able to reproduce the bug so far.

Affliction works great for now. Except it's a bit laggy in large area (in caves it's very smooth, just not outside).