Quoting: EikeI can only repeat myself: I'm not experiencing what you're talking about. And I'm not talking about some obscure future, but present and past years. I don't have tearing in Unity games (and I didn't change driver buffering optiond), neither met the other things you mentioned. What am I doing wrong...?

Good for you. I had constant tearing, and the worst in Unity games (my previous card was GTX 680). That's completely gone since I switched to AMD / Mesa.

View this comment - View article - View full comments

Quoting: GuestI don't get lockups with mesa.

I'm waiting for this one to be fixed:

https://bugs.freedesktop.org/show_bug.cgi?id=104193 [External Link]
https://bugs.winehq.org/show_bug.cgi?id=43872 [External Link]

radeonsi now has a problem of hanging the whole system when some wrong stuff goes on with OpenGL. It's surely not the best experience, but I think they improved GPU reset with Vega.

The difference is, I don't mind participating in Mesa bug reporting, but with Nvidia it's completely opaque. I have no idea if anyone is working on that bug, or if they even care.

Quoting: GuestI have no application that uses GL4.6, let alone a game

Exactly my point. And as I said, Mesa already supports 4.6, except for 2 SPIR-V related extensions.

View this comment - View article - View full comments

Quoting: XpanderConstant breaking of system? what? in 2007, yes. last 5 years, no

I had it until I switched, so surely it was an issue even recently.

Quoting: XpanderWayland is still ways off

It was off for years, and now all DEs are finally ready to switch to it. Nvidia is nowhere ready.

Quoting: XpanderNow lets ask about AMD? Freesync? HDMI/DP audio? (ok those 2 are coming soonish, but what took so much time?) No Simple GUI to change your GPU settings, OC etc? have to use some third-party ones i guess?

AMD have their GUI, but they didn't open source it, so I've never used it. Not that I care much - I rarely tweak hardware parameters, defaults work OK. But I don't see why AMD can't open source that as well, once they completely replace their PRO with Mesa (they are gradually working on it, even adding compat profile to Mesa itself). I don't think it makes any sense for them to open it before, since they'll need to rework it.

Quoting: Xpanderno OpenGL4.6 support?

Mesa supports OpenGL 4.6 except for a couple of extensions needed for Vulkan / OpenGL interop, which are being worked on. Those aren't trivial, since they require reimplementing some parts like IR translation. But it's well on the way. And I don't think you'll notice that. Which application even relies on such interop at present?

See https://mesamatrix.net [External Link]

View this comment - View article - View full comments

Quoting: EikeI surely must be doing something wrong that I haven't met any of this in many years...

Nvidia addresses some of those with a crawling pace. They supposedly fixed tearing by making a special double / triple buffering option, but it's off by default. They are working now on new API to propose for Wayland compositors (years late). If it will work out - great, but I don't expect it any time soon. They started supporting DRM/KMS kernel interfaces only recently, and even that isn't done properly yet (so PRIME kind of is there, but doesn't really work from what I've heard). And they never implemented framebuffer, so no idea how you could think it was fixed.

The bottom line - they are moving very slowly, simply because Linux integration was never a priority for them.

View this comment - View article - View full comments

Quoting: XpanderStandard APIs or not, the end user doesn't care. If it doesn't work it doesn't work. I know all the "political" stuff behind all this. Nvidia sucks, yeah. Gsync? F this, their own standards F this... but it works.

It doesn't, a least not at all seamlessly. Constant screen tearing (especially in Unity games), constant breaking of the system and need to reinstall the driver on each kernel or xorg update, no framebuffer support, Optimus horror story, opaque bug reporting process and etc. and etc. Wayland support? Forget it. If you really don't care about proper system integration, then Nvidia is OK. But I really appreciate how much better AMD works after switching to it. So talking about "just works" - AMD is way ahead, and that's to be expected, AMD are putting an effort into upstreaming their driver, while Nvidia don't care in the least.

And not really accidentally, all those benefits in AMD are from the fact that their drivers are open. My personal favorite feature though is GALLIUM_HUD.

View this comment - View article - View full comments

Quoting: SinaCutieUp until a few months ago, I was 100% AMD. But I kept increasingly having problems AMD video cards in Linux, so I bought an NVIDIA card to try out... and so far, it works flawlessly. It makes me wonder why I stuck with AMD so long.

What was the last AMD card you used? I was Nvidia user for a long time, but got fed up with poor integration and need to use the blob, so I switched to Polaris a while ago (RX 480). It's been a breeze since.

View this comment - View article - View full comments

Quoting: LeopardBut on Mesa you can't play some games without doing workarounds. For example; Divinity , Dying Light , X11 etc.

All of them are bad ports. I.e. they are doing some weird stuff with OpenGL, so if developers don't want to fix them - skip those games, or if there are workarounds - apply them. Such games suffer from the fact that developers didn't test them with Mesa. This issue should be non existent for newer games.

Quoting: LeopardAlso note that Hdmi audio , Freesync etc are not available with Mesa.

They should be soon, from Linux 4.15 and on. AMD were actually working on upstreaming it all, unlike Nvidia who don't care. So it will all "just work", using out of the box kernel.

View this comment - View article - View full comments

Quoting: GuestnVidia, AMD, and Intel force this now, one way or another.

One of the reasons they do it is DRM garbage as far as I understand (HDCP).

View this comment - View article - View full comments

Quoting: GuestWeird. It's exactly the same reason i made the switch to "team red" a good 5-6 years ago. It just worked. (and was cheaper even back then)

Mesa caught up to performance and features support in the modern OpenGL only in the last year or so. Before that, using AMD had quite a lot of downsides.

View this comment - View article - View full comments

Quoting: LinasI'd like to believe that, but I don't see how? Unless they switch to a more common type of memory.

No need to. HBM memory usage will naturally grow, so it will be less of a problem in the future.

View this comment - View article - View full comments