-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Path of Exile 2 (2694490) #8296
Comments
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. |
oh sorry i thought we should open a ticket for every game my bad |
Any suggestions about the issue though? @DSDV if you solve it let me know |
System Information
SymptomsAs 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. ReproductionStart game |
System Information
SymptomsGame opens a window, screen stays black without any progress after 10 minutes. ReproductionStart game |
Hello @EnLaLuna91, @kittyandrew, blind guess, does setting the game's launch options to |
Hello @kisak-valve, It has no effect, the same thing happens. |
@kisak-valve unfortunately didn't help, |
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. |
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: Changed |
YES, thank you |
Works!!!, thank you |
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. |
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. |
From the client logs ( |
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. |
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. |
That seems to have worked indeed, much appreciated! |
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. |
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. Edit: |
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. |
Yeah, game works fine on latest 550.40.81 vulkan dev drivers. |
Been playing the game for a bit on my system and comparing it to 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. |
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 |
Thank you, strangely this fixed the issue for me as well. |
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:
|
Compatibility Report
System Information
I confirm:
Symptoms
Does load Vulkan as default isntead of Dx12 (i guess intended by Devs)
Reproduction
The text was updated successfully, but these errors were encountered: