Quoting: 3zekielRay tracing is coming, and it is to be expected that it will be ubiquitous real fast now.

But will it come before 2018 aka Wayland in production use? Oh, wait, it's already 2020! Using a 27' 4k screen, I already depend on it in production for fractional scaling.

Quoting: 3zekielAMD cards will become expensive open source paperweights before long

Until they do not offer acceleration in XWayland, NVidias cards are 'expensive closed source' paperweights for Games right NOW for me. Ofc, your situation can be different (so this is not to answer Kimyrielle's original question about there being any use, but rather to comment the fallacies in reply to it).

Even putting OSS ideals aside, what I see is NVidias driver stack more and more failing to enable a modern Linux desktop experience, not for being badly implemented, but for being at odds with the Linux model architecturally. Just look at the EGLStreams mess. If they want to address these problems, this would require NVidia to rewrite large parts of their driver in a way more compatible with Linux's model, and therefore lose the advatages they get from sharing large parts of the codebase with Windows.

They were the best on the market in the early 2010s, but AMD has integrated much better into the Linux ecosystem and is now offering the superior driver situation for general desktop use and Intel always had a good practice for Linux drivers and upstreaming graphics stuff. I'm looking forward to them joining the dGPU market.

View this comment - View article - View full comments

Seems interesting. How is Wayland support in the driver these days? GPU acceleration in XWayland available?

If not, no thanks, wake me up when AMD 6700 is released...

View this comment - View article - View full comments

Quoting: slaapliedjeI don't run the latest drivers, like ever. I grab what the distro gives me. https://packages.debian.org/sid/nvidia-driver [External Link] Or I can even pull from experimental https://packages.debian.org/experimental/nvidia-driver [External Link] which currently has 455.38. Tiny bit behind, but still supports the RTX 3xxx cards. So yeah, much easier than AMD.

But if Your distro has the most recent proprietary packages of NVidia in their repo, but not the same for AMD, how does that mean the vendors are behaving differently?

View this comment - View article - View full comments

Quoting: tuubiThese discussions tend to end up full of partisan hyperbole (often mostly based on hearsay), but in the end, both vendors are easy to live with these days for someone who just wants to play some games. No game requires the latest kernel or Wayland—so Nvidia's reluctance to play ball is almost irrelevant—but new kernels and Mesa packages are readily available on any mainstream distro for those who need them so us AMD/Mesa users are fine too.

That said, in my opinion and experience AMD currently has an edge on Linux even if you ignore the ethical and technical implications of Open Source vs proprietary. Personally I don't like to ignore these implications, so that's another reason I'm happier on AMD.

This sums up the discussion pretty nicely. And from my personal experience I agree with your opinion, I only experienced breakages on proprietary, and having acceleration in XWayland is a pretty strong argument for Intel AND AMD GPUs.

Quoting: slaapliedjeSo I really WANT to support AMD as I believe that the hardware should all have open source drivers. I just want it to be easier to do so without compromising convenience and stability by adding third party repos or compiling custom libraries.

Debian stable is great, I run it on some VServers, and they do amazing work for stability. But at a certain point, one has to admit that for supporting cutting edge hardware that just released yesterday on mainline packages, the model of releasing a new version in the year of the fox when the stars align in the ascendant of Virgo and three kings come to Bethlehem is maybe not the way to go. So On my gaming rig, I run Fedora 33 and it just works.

View this comment - View article - View full comments

Quoting: ShmerlSince Gamescope is its own compositor, it doesn't need to worry about Mutter.

Not quite, it acts as a nested compositor in the desktop usecase, so it is inside Mutter.

Edit: Typo

View this comment - View article - View full comments

Quoting: ShmerlThis is an interesting project, but why does it mention using XWayland instead of just Wayland? Sounds like it always relies on X?

From the description on GitHub, I believe it always uses XWayland. Probably due to the fact that games tend to run in XWayland almost exclusively, I am not aware of any games running natively Wayland (among commercial games, that is).

View this comment - View article - View full comments

Quoting: Liam Dawe

Quoting: minfaerBtw, the article confuses me. It sounds like Hutchinson tweeted this by himself, but then keeps using 'they' as if it was his studio's (or some groups) stance. Which is it?

Hutchinson did tweet directly, not from a studio account. Perhaps you're tripping up on singular they [External Link]? Don't know, hard to tell, as you didn't point out the parts confusing you. When talking about a person, using "they" is just pretty normal here.

Thanks for claryfing, that was indeed what tripped me up. Non-native speaker here :huh:

View this comment - View article - View full comments

While the streamer's input is certainly a substantial part of the stream, I would still say that it is a derivative work (in a layman sense, not sure if that is a legally applicable term here). So the points Hutchinson raises are not completely amiss.
But in the end, it is in the interest of the publishers to grant the license to streamers as the article points out.

Btw, the article confuses me. It sounds like Hutchinson tweeted this by himself, but then keeps using 'they' as if it was his studio's (or some groups) stance. Which is it?

View this comment - View article - View full comments

Quoting: jensWell, it really depends on the setup. Here on Fedora everything is fine, but according to this post especially Arch users with some weird things installed (steam-native cough) seems to have issues. Steam within Flatpak seems to be another thing that doesn't work now. Not sure though if one of those are relevant for your setup.

I guess it does depend on the setup, but I'm on Fedora without Flatpak or native runtime and nothing works with 5.13 here, either. 5.0 still works perfectly. So no, not because of weird things instaled.

Edit: should mention that I am on F 33 beta, though. Maybe a package update breaks it on Arch and F 33, but not sure.

View this comment - View article - View full comments