Proton icon indicating copy to clipboard operation
Proton copied to clipboard

Path of Exile 2 (2694490)

Open DSDV opened this issue 1 year ago • 64 comments

Compatibility Report

  • Name of the game with compatibility issues: Path of Exile 2
  • Steam AppID of the game: https://store.steampowered.com/app/2694490

System Information

  • GPU: 7900xtx
  • Video driver version: Mesa 24.3.0-1.fc40
  • Kernel version: Linux 6.11.9-200.fsync.fc40.x86_64
  • Link to full system information report as Gist: https://gist.github.com/DSDV/13a2b94e96680cb976f4921ae42d0230
  • Proton version: GE-Proton9-20

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

Does load Vulkan as default isntead of Dx12 (i guess intended by Devs)

Reproduction

DSDV avatar Dec 06 '24 18:12 DSDV

Hello @DSDV, you haven't communicated any information that would need to be looked at by a Proton dev, which effectively makes this a blank issue report template.

kisak-valve avatar Dec 06 '24 18:12 kisak-valve

oh sorry i thought we should open a ticket for every game my bad

DSDV avatar Dec 06 '24 19:12 DSDV

Any suggestions about the issue though? @DSDV if you solve it let me know

kittyandrew avatar Dec 06 '24 19:12 kittyandrew

System Information

  • GPU: RTX 4080
  • Video driver version: 4.6.0 NVIDIA 565.57.01
  • SO: Arch Linux
  • Kernel version: 6.12.1-arch1-1
  • Link to full system information report as Gist: Hardware info
  • Proton version: Proton experimental and ProtonGE 9.20

steam-2694490.log

Symptoms

As soon as the game starts, a sound is heard for a second, but then the sound is turned off. And the screen stays black since I start the game. After a while the game crashes without showing anything.

Reproduction

Start game

EnLaLuna91 avatar Dec 06 '24 19:12 EnLaLuna91

System Information

  • GPU: NVIDIA GeForce RTX 4070
  • Video driver version: 565.57.01
  • Kernel version: 6.12.1
  • Link to full system information report as Gist: https://gist.github.com/kittyandrew/8c2100d99b63982e54843a608b50e4f2
  • Proton version: Proton experimental and GE-Proton9-20

steam-2694490.log

Symptoms

Game opens a window, screen stays black without any progress after 10 minutes.

Reproduction

Start game

kittyandrew avatar Dec 06 '24 20:12 kittyandrew

Hello @EnLaLuna91, @kittyandrew, blind guess, does setting the game's launch options to PROTON_DISABLE_NVAPI=1 %command% have an effect?

kisak-valve avatar Dec 06 '24 20:12 kisak-valve

Hello @kisak-valve, It has no effect, the same thing happens.

EnLaLuna91 avatar Dec 06 '24 20:12 EnLaLuna91

@kisak-valve unfortunately didn't help, here is new log steam-2694490.log

kittyandrew avatar Dec 06 '24 20:12 kittyandrew

The issue seems to be related to wayland, the game launches just fine under X11

Edit: First launching the game in x11 and setting the renderer from vulkan to dx12 allows launching the game in wayland mode afterwards.

M2-TE avatar Dec 06 '24 21:12 M2-TE

I had the same black screen issue, but am able to launch the game after editing game config to use DirectX12 instead of Vulkan.

Can be done by editing the following file: ~/.steam/steam/steamapps/compatdata/2694490/pfx/drive_c/users/steamuser/My Documents/My Games/Path of Exile 2/poe2_production_Config.ini

Changed renderer_type=Vulkan to renderer_type=DirectX12

uio-torjus avatar Dec 06 '24 21:12 uio-torjus

~/.steam/steam/steamapps/compatdata/2694490/pfx/drive_c/users/steamuser/My Documents/My Games/Path of Exile 2/poe2_production_Config.ini

YES, thank you

kittyandrew avatar Dec 06 '24 21:12 kittyandrew

Replying to https://github.com/ValveSoftware/Proton/issues/8296#issuecomment-2524200434

Works!!!, thank you

EnLaLuna91 avatar Dec 06 '24 21:12 EnLaLuna91

Replying to https://github.com/ValveSoftware/Proton/issues/8296#issuecomment-2524134603

There might be a wsi issue there as people reports Vulkan renderer of game works with X11 sessions on Nvidia while stays at black screen on Wayland sessions on Nvidia.

Leopard1907 avatar Dec 06 '24 21:12 Leopard1907

Thanks you for the reports and for taking steps to characterize the issue. For future reference, I've filed NV-internal bug 4999362 to track and investigate this issue.

cubanismo avatar Dec 06 '24 22:12 cubanismo

From the client logs (logs folder next to the game executable), this looks like a Vulkan error not being handled by the game: 2024/12/07 09:35:44 8111398 db2b0f7b [INFO Client 340] [VULKAN] acquire: vk::Device::acquireNextImageKHR: ErrorOutOfDateKHR This happens on launch when using Vulkan and after switching to Vulkan in-game (started as DX12) the same error appears sometimes when switching windows (other than that the Vulkan renderer works fine). As per the Vulkan Spec, this should be handled by re-creating the swapchain

JSEverything avatar Dec 07 '24 09:12 JSEverything

I can play just fine on but experience sudden performance degradation after about an hour where the framerate starts jumping up and down and the CPU frametime goes above 50ms if you move your character (stays low when you stop moving), only a restart seems to fix that.

zr00da avatar Dec 07 '24 12:12 zr00da

I can play just fine on but experience sudden performance degradation after about an hour where the framerate starts jumping up and down and the CPU frametime goes above 50ms if you move your character (stays low when you stop moving), only a restart seems to fix that.

I had the same issue, enabling the steam overlay seems to have fixed this for me.

calebaden avatar Dec 07 '24 12:12 calebaden

Thanks you for the reports and for taking steps to characterize the issue. For future reference, I've filed NV-internal bug 4999362 to track and investigate this issue.

Hello @cubanismo, I see that you are working on making Nvidia Linux drivers and that you have created a bug to fix this. If it helps, this same error has happened to me with BG3, Satisfactory and other games I don't remember. In these games, since the game was booting in Dirext12 and I was the one switching to Vulkan, I knew how to fix it.

The pattern I detected is the following: Wayland + Game under proton + Vulkan + Nvidia.

As I didn't know, until now, where the error came from, I didn't know where to put the bug.

I add this as possible information to detect the bug.

EnLaLuna91 avatar Dec 07 '24 12:12 EnLaLuna91

I had the same issue, enabling the steam overlay seems to have fixed this for me.

That seems to have worked indeed, much appreciated!

zr00da avatar Dec 07 '24 13:12 zr00da

Can anyone launch the game (using Nvidia drivers) with gamescope? I am trying to running it with these options

DXVK_HDR=1 gamescope -f -w 2560 -h 1440 --hdr-enabled -- env VKD3D_DISABLE_EXTENSIONS=VK_KHR_present_wait %command%

in order to get HDR going. The renderer has been set to DX12 and the game launched without gamescope fine but won't run at all with gamescope. Using KDE Plasma & under Arch with 1080 GTX card.

afettouhi avatar Dec 07 '24 16:12 afettouhi

I have the game running pretty well. Unfortunately, any time a video is playing (including the cutscene at the end of Act 1), it completely kills all sound output on my system. Linux Mint 21.3 with Xanmod 6.11.10-x64v3 kernel. FWIW, I'm using the NVIDIA 550 drivers installed through apt on X11 with Cinnamon. I'm also using Pipewire/Pulse for my sound system, although I suspect that isn't related to this issue. Oh, I'm also running Proton Experimental. May try one of the GE flavors and see what that does.

Edit: gamemode has, in fact, not fixed it. I'm not 100% sure what's causing it, but having a YouTube video playing on my second monitor seems to be part of it.

TNTftw21 avatar Dec 07 '24 19:12 TNTftw21

image Game works with nvidia wayland if you start it in windowed mode. Game renderer vulkan.

You can then set fullscreen via KDE window settings and it will work fine

Kustovsky avatar Dec 09 '24 16:12 Kustovsky

We determined this is an issue we've already resolved in pending driver releases. In the meantime, could those who are running into the issue verify it does not occur with our Vulkan developer beta drivers? Note the first drivers on this page are our regular releases. The beta drivers are further down under an appropriate heading.

The fix should already be present there. However, please be aware these drivers are not meant for general use and have not gone through our usual QA process. They're intended primarily for developers who need to develop code using the latest Vulkan API features, and for verifying pending bug fixes, like this one.

cubanismo avatar Dec 10 '24 05:12 cubanismo

Replying to https://github.com/ValveSoftware/Proton/issues/8296#issuecomment-2530429943

Yeah, game works fine on latest 550.40.81 vulkan dev drivers. No DLSS support though

Kustovsky avatar Dec 10 '24 10:12 Kustovsky

Been playing the game for a bit on my system and comparing it to Windows. The framerate is about almost cut in half whenever visual effects happen. The loading screens are also almost doubled or tripled in length and the game initially seems to be extremely slow at streaming in effects and certain assets while its almost instantaneous on Windows.

This has mainly been through having DirectX12 renderer selected, but having Vulkan selected seems to produce the exact same results. Just tried it and it's still just as bad.

Running "NVIDIA RTX 2070" card with the "565.77" drivers on "Wayland" with the "6.12.3-arch1-1" kernel.

Tatisen avatar Dec 11 '24 19:12 Tatisen

I am unable to get remote play to function properly with the game. I am running it with proton. Can this be a proton issue or is it something else? I am trying to stream to a Steam Deck. Remote play functions perfectly with other games.

EndeavourOS 6.12.3-arch1-1 kernel Nvidia GTX 1070 (565.77 drivers) Plasma 6.2.4 X11 Ryzen 7 7800X3D

dev0T avatar Dec 11 '24 21:12 dev0T

I can play just fine on but experience sudden performance degradation after about an hour where the framerate starts jumping up and down and the CPU frametime goes above 50ms if you move your character (stays low when you stop moving), only a restart seems to fix that.

I had the same issue, enabling the steam overlay seems to have fixed this for me.

Thank you, strangely this fixed the issue for me as well.

spaghetticodez avatar Dec 12 '24 21:12 spaghetticodez

The ingame clock is off by one hour depending on the set timezone. The same is not seen on Windows. Tested on Proton Experimental (20241206).

To enable the ingame clock: ESC -> Options -> Interface tab -> Show Clock

image

$ date
Mo 16. Dez 17:09:21 CET 2024
$ localectl status
System Locale: LANG=en_US.UTF-8
               LC_NUMERIC=de_DE.UTF-8
               LC_TIME=de_DE.UTF-8
               LC_MONETARY=de_DE.UTF-8
               LC_PAPER=de_DE.UTF-8
               LC_MEASUREMENT=de_DE.UTF-8

Mershl avatar Dec 16 '24 16:12 Mershl

The ingame clock is off by one hour depending on the set timezone. The same is not seen on Windows. Tested on Proton Experimental (20241206).

unset TZ; %command%

codebam avatar Dec 20 '24 12:12 codebam

I suggest re-attempting to use the Vulkan Shaders. From what I can tell there was a hotfix released 12/21 that resolved the compatibility.

I'm using Proton-GE-9.21 20 Dec 2024 - I had to modify PoE2 rendering to use DirectX12 21 Dec 2024 - After hotfix, Vulkan Shaders was default again, but successfully loaded the game

My system reference:

  • Fedora 40
  • Proton-GE 9,21
  • AMD 5950X
  • Nvidia Quadro M2000
  • Drivers nvidia-6.11.10-200

athias avatar Dec 21 '24 16:12 athias