Skip to content
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

Latest Gamescope breaks NVIDIA #987

Open
kodatarule opened this issue Oct 15, 2023 · 18 comments
Open

Latest Gamescope breaks NVIDIA #987

kodatarule opened this issue Oct 15, 2023 · 18 comments

Comments

@kodatarule
Copy link

The latest version of gamescope has broken nvidia completely, all you see is a black window.

Operating System: EndeavourOS
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11
Kernel Version: 6.5.7-273-tkg-bmq (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 31,3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2

gamescope 3.12.7-1

@HunterCZ122
Copy link

Unfortunately, Gamescope is affected by an Nvidia driver bug that Josh needs to work around (#948). My recommendation is to use an older version of Gamescope until it gets fixed.
You can revert it on your Arch-based system by grabbing an older package from Arch Linux Archive:
sudo pacman -U https://archive.archlinux.org/packages/g/gamescope/gamescope-3.12.5-1-x86_64.pkg.tar.zst

@jarrard
Copy link

jarrard commented Nov 13, 2023

Yeah I noticed this issue with gamescope-plus package.

@Sweeper5
Copy link

Sweeper5 commented Dec 5, 2023

Well you are in luck, since May this year, no package of Gamescope have worked for me under Nvidia.
Now to verify it wasn't Gamescope itself being faulty, I have tried the same versions on my laptop that is an all AMD setup with a Vega 3 GPU.
Suffice to say, it runs flawlessly and I can really see why people love Gamescope on there.

@HunterCZ122
Copy link

Well you are in luck, since May this year, no package of Gamescope have worked for me under Nvidia.
Now to verify it wasn't Gamescope itself being faulty, I have tried the same versions on my laptop that is an all AMD setup with a Vega 3 GPU.
Suffice to say, it runs flawlessly and I can really see why people love Gamescope on there.

I also ran gamescope through Intel iGPU, which worked fine as a workaround until 545.
Hopefully NVK will give us some hope in the future if Nvidia doesn't fix this.

@ageisen2000
Copy link

I'm also getting this error on a 3090 on endeavouros. Let me know if I can send any logs or anything to help

@unhappy-ending
Copy link

Try the 535.43.20 vulkan beta branch, gamescope is working on that branch for me.

@jarrard
Copy link

jarrard commented Dec 11, 2023

just use gamescope 5.12, easier solution

@jeisom
Copy link

jeisom commented Dec 13, 2023

Try the 535.43.20 vulkan beta branch, gamescope is working on that branch for me.

Still broke here with Vulkan beta x.x.20. Immediate segfault. 5.12.5 works though.

@unhappy-ending
Copy link

Try the 535.43.20 vulkan beta branch, gamescope is working on that branch for me.

Still broke here with Vulkan beta x.x.20. Immediate segfault. 5.12.5 works though.

Yeah, it beta drivers fixed some stuff on 5.13 but some games would outright refuse to launch. 5.12.5 was working yesterday, but now it's not working, no idea what changed so it's a little frustrating

@unhappy-ending
Copy link

unhappy-ending commented Dec 21, 2023

Another update, 535.43.20 Vulkan beta branch had intense horizontal screen tearing while playing games. I can't recommend it. 545 has major flickering in Chromium based web views which means Steam's overlay, but there isn't the screen tearing issue and Steam can use software rendering to "resolve" the disappearing graphics and flickering issue. Gamescope 5.12.5 is still working fine with 545, so it seems the best thing to do is stick to it until Nvidia resolves all the issues at hand.

@jarrard
Copy link

jarrard commented Dec 21, 2023

Some of the issues may just be wayland related if your using that (most are these days). Still some rough edges for NVIDIA under Wayland which you need to work around.

@HunterCZ122
Copy link

HunterCZ122 commented Dec 25, 2023

If you guys get crash when launching any Vulkan game, you need to disable Gamescope WSI as a workaround:
ENABLE_GAMESCOPE_WSI=0 gamescope -- %command%
Kinda weird Nvidia didn't backport fix for Vulkan WSI on Wayland.

@jarrard
Copy link

jarrard commented Jan 7, 2024

Still blackscreens games on nvidia and wayland

@thechitowncubs
Copy link

Total black or transparent window with nvidia 545

@AlexFolland
Copy link

I'm getting permanent freezes in the first minute with gamescope on Nvidia with Nvidia 545.29.06. It's not a black screen, but it's still unplayable.

@thechitowncubs
Copy link

I pulled updated git and it works but permanent freeze issue here too

@peacey
Copy link

peacey commented Jan 30, 2024

I am having a similar issue with gamescope freezing or having a blank screen when running a game. Using latest gamescope git, latest Nvidia 550 beta driver, and kernel 6.7.2.

The issue manifests slightly differently if running gamescope from within another compositor or standalone.

  1. If running gamescope from another compositor (like kwin), the game starts up and video works for a few seconds to a couple minutes then freezes completely (only video freezes, audio remains playing in background so game is still running). The game never unfreezes, can't be exited sanely, and can only be force closed by killing the gamescope session.

  2. If running gamescope in its own standalone session, the game starts up in a black window and never updates. The audio can be heard so game is running, but the window remains black forever. Again, only force killing the game or gamescope can close it.

All these tests were done with only the minimal parameters "-W 1920 -H 1080 -f". Issue happens whether HDR is enabled or not.

Sidenote: HDR gaming with Nvidia for the first time with the 550 driver was super cool for a hot minute before the game froze!

@profpyrus
Copy link

As far as I can tell, this issue still persists, specifically trying to fix Fragpunk running in hyprland.
The game starts just fine, and when I try to join a match or go into the range, it works briefly before crashing. Any news on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests