If I am getting a certain FPS with Smooth Motion off shouldn’t I get roughly the same FPS being reported when Smooth Motion is on being reported say by Mangohud? Instead, what I am seeing is drastic hit in performance. in TLOU, it is almost a 50% performance hit.
Bug report: Path of exile 2. Game refuse to start with Vulkan renderer + Wayland Drv.
Brief Description
Trying to launch Path of Exile 2 with renderer_type=Vulkan+ PROTON_ENABLE_WAYLAND=1 lead to just black screen.
Xwayland: Vulkan = launch correctly.
Xwayland: Directx12 = launch correctly.
Wayland drv: Vulkan = black screen.
Wayland drv: Directx12 = launch correctly.
Steps to Reproduce and Frequency:
Frequency: Always.
Steps for reproduce:
1: I’m using proton-ge 10-15.
2: launch options:env OBS_VKCAPTURE=1 PROTON_ENABLE_WAYLAND=1 PROTON_USEWOW64=1 mangohud %command% --nologo. I tried without mangohud and PROTON_USEWOW64=1 also.
3: In"Documents/My Games/Path of Exile 2/poe2_production_Config.ini", edit renderer_type to Vulkan, or from the game itself in game options.
4: Black screen if launched on Vulkan. If we trying to change renderer type from DirectX11/DirectX12 to Vulkan, game will freeze. You can still hear sound and moving mouse around tho.
System Configuration:
- System: “x86_64-linux”
- Host os: Linux 6.16.5. NixOS, 25.11 (Xantusia)
- Desktop Environment: KDE Wayland-6.4.4
- GPU:Nvidia RTX 3090. Driver Version: 580.82.07. Open source driver.
- Monitors: DP-1: 2560x1440@240(VRR), HDMI-A-1: 1920x1080@60(No VRR)
I’m attaching my PoE 2 production config for reproducibility.
poe2_production_Config.txt (12.9 KB)
nvidia-bug-report.log.gz (1.6 MB)
1 Like
thank you for the detailed explanation!
It almost sounds like the Vulkan PresentWait bug is back.
Nevermind, I did it anyway because if I don’t do it clearly no one at Nvidia will.
Settings: 4K DLSS CN Ultra Performance low preset
Here is Windows 11 with FG off:
Here is it with it on without a restart:
Here is it on AND after a restart:
Here is Afterburner’s overlay on, showing basically the same FPS as Steam and the in-game overlay.
All of these screenshots have Steam’s in-game overlay on which according to:
includes frame generation frames. Afterburner was started after the game was already running.
Nevermind frame generation being completely broken on Linux, it doesn’t even do anything on Windows either besides nearly triple the latency.
It’s absolutely insane that a multi-trillion dollar company can’t do basic QA testing themselves and have to be told multiple times their software is broke.
I probably know of atleast a dozen driver bugs at this point(some major and could cause data corruption and some of which I thought were because my GPU was defective and costed me time and money for shipping) and the most anyone at Nvidia can do is create a bug report that gets ignored 90% of the time. Worse yet, you parrot a troll who doesn’t even have a GPU that supports frame generation but is somehow an expert on it.
Lets not even mention the 580 drivers have that close bug. No one at Nvidia could do a quick test on a Gnome system before hitting the upload button? Are you serious?
People at Nvidia really need to be fired at this point and lawsuits need to go flying. This is is a full on circus.
the gtk4 close bug has been fixed in the latest driver
chill bro
1 Like
Huh, okay. So these two legendary, classic environment variables are no longer needed?
PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command%
Try it with them. If that doesn’t fix it for you, I’ll remove that from all my games (finally). :D
They worked like this:
- PROTON_HIDE_NVIDIA_GPU=0 lets the game know that you have an NVIDIA GPU. Otherwise it pretends to have an AMD GPU, to prevent various buggy code from running. Many games used to crash if you didn’t hide the NVIDIA-ness of the GPU. If this is no longer necessary, I guess they’ve finally reached a stage where the NVIDIA emulation is stable and doesn’t need to hide anymore.
- PROTON_ENABLE_NVAPI=1 enables the DXVK-NVAPI library which emulates NVAPI to enable stuff like DLSS.
If those are no longer necessary, I wonder when the defaults changed… Maybe it’s a GE-Proton change? Valve’s Proton might still need these?
Has anyone else noticed that the Flatpak for Element (Matrix client) has become completely broken on Wayland and that it seems to be an NVIDIA driver bug and an Electron bug?
flatpak install im.riot.Riot
flatpak run im.riot.Riot
You’ll see this error:
“libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Could not bind the given EGLImage to a CoglTexture2D”
It happens on both 575.64.05 and 580.82.07, with Kernel 6.16.3.
Full details here:
you have a misconfigured multi gpu system, ie element is trying to use some other gpu. that doesn’t work when the display is connected to Nvidia card
They haven’t been needed since Proton 9.
1 Like
Thanks, I think you’re right. These problems began after I enabled the integrated GPU in the BIOS. I use my dedicated GPU as the display output to have full features (VRR, 120 Hz etc) for gaming. But then I switch the cable to the integrated GPU and reboot the system if I want a low power setup.
So what seems to be happening here is that Element is written to search for an integrated GPU and force itself to use it no matter what the user wants. I tried setting the vars to force it to use the NVIDIA GPU, but nope, they’re not working:
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia
Thank you, I had never heard that news.
DXVK-NVAPI covers PROTON_ENABLE_NVAPI here:
Proton 9.0 includes DXVK-NVAPI and enables it by default for all titles with a few exceptions. Proton 9.0 can force-enable DXVK-NVAPI for titles that have DXVK-NVAPI disabled by default and also for non-NVIDIA GPUs when setting
PROTON_FORCE_NVAPI=1. Contrary,PROTON_DISABLE_NVAPIdisables DXVK-NVAPI.
I then dug around in Proton 8 and 9 code. In Proton 8, “PROTON_ENABLE_NVAPI” caused “DXVK_ENABLE_NVAPI=1” to be set.
Nowadays, “PROTON_ENABLE_NVAPI” has been completely removed, and the “DXVK_ENABLE_NVAPI=1” flag is instead always set unless you explicitly disable NVAPI:
And regarding PROTON_HIDE_NVIDIA_GPU=0, I was able partially track it down. Proton checks the variable as follows:
- No value set: Do NOTHING.
- Value set to 0: Do NOTHING.
- Value set to 1: Set env variable “WINE_HIDE_NVIDIA_GPU=1”.
- Code is here:
After that, I looked in DXVK, DXVK-NVAPI, VKD3D and Wine and don’t find a reference to “WINE_HIDE_NVIDIA_GPU” in any of those codebases. Very weird.
But considering that Proton never does anything unless you set the value to “1” nowadays, it seems clear that the default behavior of “WINE_HIDE_NVIDIA_GPU” is already 0 (not hiding). In the past, I know that my GPU showed up as Radeon in games (for compatibility, to prevent games from trying to use NVIDIA features and crashing), unless I manually told Proton to unhide NVIDIA GPUs. But now that’s clearly not needed anymore.
That’s very nice news, I can clean up so many configs in Steam and Heroic Launcher now. Thanks!
This is the second time a GTK bug has been introduced because of lack of basic QA among dozens of other bugs, some of which have existed for years and costed me time and money.
chill bro
There was a similar issue in Chrome and Google fixed it on their side: 575 release feedback & discussion - #440 by amrits
Element has to fix it on their side too, most likely.
1 Like
on chromium < 139 you would fix it with
export __EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json # this and the 'render-node-override' argument are only needed on systems that also have gpus from other manufacturers
chromium --ozone-platform-hint=auto --render-node-override=/dev/dri/by-path/pci-0000:01:00.0-render #path to nvidia dri render node
no idea how to fix it on electron, might be worth to just wait for them to update electron
1 Like
Unless your desktop is pretty old or you have some pretty specific parts, your desktop will also have an iGPU. Almost all Intel CPUs come with an iGPU and almost all AMD CPUs with Socket AM5 will also come with an iGPU.
Annnnnnd ? iGPU that you simply disable in the bios
I have a 5950x and does not have a iGPU. I wouldn’t call it old.
2 Likes
Could you add some sort of CPU fallback for opengl support on the Maxwell and any other architectures affected? popcnt instruction being called now breaks opengl programs on hardware where no popcnt instruction is found. This created problem did not exist in the R550 drivers or earlier drivers. This was introduced starting with R570 and continues now into R580. Please fix before October? I already posted about the issue elsewhere and mentioning here.
This specifically involves nvoglv64.dll throwing the EXCEPTION_ILLEGAL_INSTRUCTION
1 Like
Here is a video of reproduction of this issue on my laptop, with newest 580.82.07 nvidia-open driver.
Video start: set RTXGI and Effects to Static&Low. Then game restart. Settings of RTXGI and Effects starts from 02:30. Freeze starts from 02:40 to 03:48 (game thread hang detected).