-
Notifications
You must be signed in to change notification settings - Fork 65
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
Actually, NVIDIA works pretty well on wayland. #194
Comments
Not if you use Discord, and I'd bet that's a significant amount of people. https://www.reddit.com/r/Fedora/comments/13rk5rs/discord_stutters_on_wayland_but_the_problem_goes |
There is nothing wrong with this video. If there is a delay in drawing / stutters, this is fixable by forcing discord to use Wayland instead of xwayland. I am using discord daily. The problem is that the apps don't want to use Wayland natively. There are well-known flags which one can use to fix discord. |
The site should probably link to Nvidia's own Wayland limitations list in the latest driver. https://forums.developer.nvidia.com/t/wayland-information-for-r545-beta-release/214275 |
Late reply, but that is not an acceptable solution. Forcing Wayland introduces regressions in the window decorations (like, actually no options to select from but exit). |
I know it was pointed out that it is not acceptable solution. Additionally currently not everything works even with Ozone layer, f.e. screen sharing, as per arch wiki. But we're getting there, I'd suggest adding Hyprland to list of environments supporting NVIDIA graphics, even though they do not claim official support, as explained on upstream wiki |
Well, we are already there, this is a problem with Discord shipping electron 22 which is 6 major versions behind the currently-latest-at-time-of-writing 28 version. All these problems are self-inflicted by Discord itself. You can attempt to use a custom Discord packaging (of the official client) that swaps out its Electron for a system 28, but people seemingly don't have great luck with that either, so best just wait for an official release. Since am already here, in addition to #194 (comment) there's also an issue with 545+ drivers that have introduced historical ghost frames even for native wayland windows. There are workarounds by installing protocols for explicit sync which, while they're not supposed to work due to lack of support in the drivers, somehow bug it out enough to make it a better experience anyway. At least one Nvidia employee publicly said they expect https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/967 to be merged "relatively soon", so all of the xglamor and now even wayland window issues should hopefully be gone this year once and for all, at least for the GPUs that Nvidia still releases drivers for. |
Had to RMA my 7900 XTX recently, and had to switch back to my 2080Ti for a week. I installed the proprietary drivers and it was near unusable on Wayland. My windows were constantly flickering, X11 was fine. |
The flickering is now fixed due to explicit sync and nvidias section should be updated |
That's waiting on 555 and 560 driver version respectively, so still some months away. |
NVIDIA claimed 15.05.2024 for the release of the working driver
|
hahahahahahahsashdfhashdfhasdhf the last 6 months of my fucking life i couldn't play any game running xwayland because of extreme flickering that would kill any seizure prone person if they saw it. since 545 my linux experience has been nothing, but trying to get these drivers fucking stable, whether it was applying not yet merged patches or inputting different environment variables it was nothing, but pure pain and IT STILL IS. they better make that 15.05 schedule or i'm actually gonna film myself pissing on this graphics card |
Take the numbers from the utility's output and read the man. |
I'd not mention any "caveats" of any sort on the main page. I ran i3 (sway), qtile, and a few others until I finally landed on Hyprland. The proprietary driver works like a beast. I am not sure what kind of trouble there might be. I have actually fully moved from my X11 setup to Wayland today.
The text was updated successfully, but these errors were encountered: