Sway 1.7-rc1 Has Better Zero-Copy Direct Scanout, Drops "--my-next-gpu-wont-be-nvidia"

[ehansin]

Editing the .desktop via Menulibre is the easiest/best option.

A little later on this, but thanks for the heads up.

[Azpegath]

I have issues with pointer stuttering when playing Valheim on Sway, for the in-game pointer.
The game and mouse input works well otherwise. Perhaps some of the improvements in 1.7 fixes my issue?

I should try installing the rc and test it, and if it doesn't, log a bug.

[dec05eba]

I wish sway (wlroots) supported overlay planes and zero copy direct scanout for them because right now I have to run applications in fullscreen to get reasonable performance on my pinephone. With the overlay planes I should be able to have the same performance while being able to see a top and bottom bar (or a virtual keyboard).

[funforums]

Didnt know about that flag name. Lol

[Ironmask]

Too soon IMHO. NVIDIA Wayland support is still highly incomplete and we're not even sure if it's coming sooner than in next 5 years or so

That's what I thought, too. But it's better for the Linux side to be the "bigger man" and lend out an olive branch sooner than nVidia. Makes them look even more pathetic in the long-run.

[c117152]

The tab dragging ( https://github.com/swaywm/sway/pull/6219 ) is nice. Thanks.

[QwertyChouskie]

Not related to "eff nvidia", but serious question if anyone can help me out here

I'm running Sway on a minimal Fedora 35 install and trying to stay Wayland native for as much as I can (for many reasons, but scaling being big obvious difference.) The default Firefox package is starting for me on XWayland, though after installing the "firefox-wayland" package, I can just launch that. I can probably make better, and on a related note...

Chromium and VSCodium (built on Electron, which is built on Chromium) both can run Wayland native if I pass them these flags:
--enable-features=UseOzonePlatform --ozone-platform=wayland

But I have to do that on the command line. I don't know where I can just set these so I can launch from my launcher (using bemenu for now.) Can I set some variables for this (and if so where and how?)? Or do I modify the .desktop files? What is correct here? I can figure a lot of things out, but to be honest I am clueless here Any help appreciated -- thanks!

Btw, seeing the reference to the foot terminal being default on Sway 1.7, I found it is in the Fedora repos and installed that and set as my $term variable in the Sway config (was using alacritty.) So far so good as best I can tell.

Editing the .desktop via Menulibre is the easiest/best option.

[ehansin]

Not related to "eff nvidia", but serious question if anyone can help me out here

I'm running Sway on a minimal Fedora 35 install and trying to stay Wayland native for as much as I can (for many reasons, but scaling being big obvious difference.) The default Firefox package is starting for me on XWayland, though after installing the "firefox-wayland" package, I can just launch that. I can probably make better, and on a related note...

Chromium and VSCodium (built on Electron, which is built on Chromium) both can run Wayland native if I pass them these flags:
--enable-features=UseOzonePlatform --ozone-platform=wayland

But I have to do that on the command line. I don't know where I can just set these so I can launch from my launcher (using bemenu for now.) Can I set some variables for this (and if so where and how?)? Or do I modify the .desktop files? What is correct here? I can figure a lot of things out, but to be honest I am clueless here Any help appreciated -- thanks!

Btw, seeing the reference to the foot terminal being default on Sway 1.7, I found it is in the Fedora repos and installed that and set as my $term variable in the Sway config (was using alacritty.) So far so good as best I can tell.

[aufkrawall]

Too soon IMHO. NVIDIA Wayland support is still highly incomplete and we're not even sure if it's coming sooner than in next 5 years or so

It still might already help to find some bugs (mostly on the side of the NV driver ofc) now, opt-in doesn't hurt anyone. It's surely welcome to be frank about dumb issues of proprietary drivers, but let's not be fundamentalists.

[bple2137]

Too soon IMHO. NVIDIA Wayland support is still highly incomplete and we're not even sure if it's coming sooner than in next 5 years or so