NVIDIA DLSS coming to Proton, plus GeForce RTX 3080 Ti and GeForce RTX 3070 Ti announced

So yeah, AMD's behavior does bother me. Actually, compared to what I hear from many persons, AMD support is in many way not that great. You often have to wait for months before new GPUs are supported (as in booting)...

Sorry, but that's BS. All AMD release in the last 3 or 4 years had a proprietary driver release on Linux the same day they hardware was released. And if your point is that kernel and Mesa version releases doesn't sync with the hardware release, I can tell you that this issue is not isolated to AMD.

I indeed ignored the closed source driver, as it seems to have its support limited to a few distro. And it is not the target for games and so on.
Also, there is still no full support in the "normal" driver for quite a few features, see Joshua Ashton's closing words in his blog about RTX and about supporting a driver no one cares about. I did rephrase it, but this is not me saying it in the first place. [Joshua Ashton](https://blog.froggi.es/bringing-vulkan-raytracing-to-older-amd-hardware/)

AMDVLK and AMDGPU-Pro are pretty much worthless as targets for developers. Waiting between 3-months and half a year for a release with new fixes/features is a complete joke for anyone wanting to ship a game or really anything.

As for the Mesa/Kernel issue not being only for AMD, it might be, but the only competitor in x86 space making use of open source driver for their (i)GPUs actually has a much better track record (except for one obscure dGPU that no one really cares about and was more of a warm up). So I don't really get your point. Supporting your products so as to release code and merge it sufficiently ahead of release is quite possible, and again, AMD has the manpower/money/ressources/smart enough people to do just that. It is just not their priority / not worth enough for them. So is life.

I indeed ignored the closed source driver, as it seems to have its support limited to a few distro. And it is not the target for games and so on.
Also, there is still no full support in the "normal" driver for quite a few features, see Joshua Ashton's closing words in his blog about RTX and about supporting a driver no one cares about. I did rephrase it, but this is not me saying it in the first place. [Joshua Ashton](https://blog.froggi.es/bringing-vulkan-raytracing-to-older-amd-hardware/)

AMDVLK and AMDGPU-Pro are pretty much worthless as targets for developers. Waiting between 3-months and half a year for a release with new fixes/features is a complete joke for anyone wanting to ship a game or really anything.

As for the Mesa/Kernel issue not being only for AMD, it might be, but the only competitor in x86 space making use of open source driver for their (i)GPUs actually has a much better track record (except for one obscure dGPU that no one really cares about and was more of a warm up). So I don't really get your point. Supporting your products so as to release code and merge it sufficiently ahead of release is quite possible, and again, AMD has the manpower/money/ressources/smart enough people to do just that. It is just not their priority / not worth enough for them. So is life.

You're mixing a lot of stuff here.

First of all, Joshua is talking about the release of official RT support for Vulkan and what has pissed him off is how AMD took around 5 extra months to release these extension on Linux while on Windows it was released the same day. Is this is a pitty? yes. Is this something that Linux users will complain? well, probably if they want to develop RT apps or if the really love to play Quake 2 they will... just like many Nvidia users has been complaining because they can't use wayland with their GPU.

And regarding AMD proprietary drivers, it's true that they only support SUSE, RHEL/CentOS and Ubuntu but want no one takes in account is that shipped on them you have the source code for AMDGPU module. So, if you want to, you can install/adapt to you system what you need, just like many other distros have to do with Nvidia drivers dkms (if they can).

TL;DR: If for missing feature we want to talk we can do the same with both companies. But we can agree that not being able to boot with a new AMD GPU is something that doesn't happen since long ago as is just a bias that never goes away.

It looks extremely offensive. What kind of features do you need to wait for to develop games?
I'm currently looking at the list of Stadia games, and I see that the porters did not interfere with anything with AMDVLK.

This is nonsense and demonstrates that you have no idea what goes into anything to do with vkd3d-proton. And Joshua is a vkd3d-proton *and* DXVK developer, and knows infinitely more about this shit than you do.

Developers porting their games to Stadia (which are EXTREMELY few and far between compared to the Windows games that vkd3d-proton and DXVK have to work with) are not even remotely in the same situation as the vkd3d-proton devs. They can tailor their games to fit what's provided by AMDVLK. And since these games don't use anything like ray tracing or DLSS, it's even less like what vkd3d-proton has to do.

Meanwhile, vkd3d-proton has NO input, and they have to translate one entire graphics API over to Vulkan, and if the extensions aren't there, it doesn't work. Which is *exactly* what Josh is talking about.

Your entire comparison is complete and utter nonsense.

Please don't throw shade at people if you don't know what you're talking about.

Well, I wish NVidia would fix their drivers and do better QA. Their new drivers crashes on boot if your montior is connected with DP and/or resoution greater than 1080p.

[https://forums.developer.nvidia.com/t/465-24-02-page-fault/175782](https://forums.developer.nvidia.com/t/465-24-02-page-fault/175782)

Well, I wish NVidia would fix their drivers and do better QA. Their new drivers crashes on boot if your montior is connected with DP and/or resoution greater than 1080p.

[https://forums.developer.nvidia.com/t/465-24-02-page-fault/175782](https://forums.developer.nvidia.com/t/465-24-02-page-fault/175782)

To be fair, it seems confined to some models, which might explain why they missed it. No issue here with 2k freesync MSI monitor, and seems many of us have no issue. Likely some specific incompatibilities.
But overall, I wish vendors would do more QA yes ... Cheaping out on QA will only cause issues for yourself down the road.

Well, I wish NVidia would fix their drivers and do better QA. Their new drivers crashes on boot if your montior is connected with DP and/or resoution greater than 1080p.

[https://forums.developer.nvidia.com/t/465-24-02-page-fault/175782](https://forums.developer.nvidia.com/t/465-24-02-page-fault/175782)

I have a 3440x1440 screen with DP and it works fine. Even freesync/gsync is working perfectly with latest drivers.

Well, I wish NVidia would fix their drivers and do better QA. Their new drivers crashes on boot if your montior is connected with DP and/or resoution greater than 1080p.

[https://forums.developer.nvidia.com/t/465-24-02-page-fault/175782](https://forums.developer.nvidia.com/t/465-24-02-page-fault/175782)

Um, no?

I have an RTX 3090 and my overall resolution is 5120x1440@165Hz (2x2560x1440@165Hz), with both connected over DisplayPort. Never once has it failed to boot. And I'm on 5.13-rc4 right now.


Last edited by gardotd426 on 2 Jun 2021 at 9:23 am UTC

At last good news on the nvidia side, too bad I finally got my hands on a AMD GPU.
Farewell green team, you served me well over the last 2 decades but your time is up.

This is nonsense and demonstrates that you have no idea what goes into anything to do with vkd3d-proton. And Joshua is a vkd3d-proton *and* DXVK developer, and knows infinitely more about this shit than you do.

In particular, he was involved with the creation of the vendor-neutral Vulkan ray tracing extension, redid Q2RTX to use the vendor-neutral Vulkan ray tracing extension, and... wrote an open source implementation of Vulkan ray tracing for AMD hardware, which AMD have failed to do themselves.

you cant buy non TI
why the F do they make a TI then?

Hopefully this means Metro Exodus Enhanced Edition will be playable soon. Although I only have a 2060 so maybe it's irrelevant.

It plays OK on my system minus the RT and DLSS which show in options but not accessible. and DLSS should help with a 2060 once up and running. Real test will be when we see what Proton does with Q2 RTX v the native Linux version.

Hopefully this means Metro Exodus Enhanced Edition will be playable soon. Although I only have a 2060 so maybe it's irrelevant.

It plays OK on my system minus the RT and DLSS which show in options but not accessible. and DLSS should help with a 2060 once up and running. Real test will be when we see what Proton does with Q2 RTX v the native Linux version.

That's the normal version, not the enhanced edition. And Q2RT in Vulkan, so doesn't require any translation.

you cant buy non TI
why the F do they make a TI then?

Maybe to distribute their mining restricted GPUs so that they actually have a chance of delivering them to gamers?


Last edited by Ehvis on 2 Jun 2021 at 11:51 am UTC

you cant buy non TI
why the F do they make a TI then?

For 3070, good question.
For 3080 TI, according to LTT, it seems the supply of rtx 3090s is currently bound by the DDR6X supply, so instead of having 24GB, you get 12GB on a GPU which is essentially the same otherwise. It then allows you to do twice as many with as many dies. The 2% shave off is probably to support using GPU with low defect rate too.
The 3080ti is a 3090 with less ram, not a boosted 3080.


Last edited by 3zekiel on 2 Jun 2021 at 3:26 pm UTC

Um, no?

I have an RTX 3090 and my overall resolution is 5120x1440@165Hz (2x2560x1440@165Hz), with both connected over DisplayPort. Never once has it failed to boot. And I'm on 5.13-rc4 right now.

Well, this is an nvidia-recognized bug that is currently affecting many people across multiple distributions. And anyone it does affect is in for a rough day. The type of bug that leaves a sour impression on the company for those affected.

But you aren't having this issue, so I'm sorry I've wasted everyone's time.

Um, no?

I have an RTX 3090 and my overall resolution is 5120x1440@165Hz (2x2560x1440@165Hz), with both connected over DisplayPort. Never once has it failed to boot. And I'm on 5.13-rc4 right now.

Well, this is an nvidia-recognized bug that is currently affecting many people across multiple distributions. And anyone it does affect is in for a rough day. The type of bug that leaves a sour impression on the company for those affected.

But you aren't having this issue, so I'm sorry I've wasted everyone's time.

The formulation from gardotd426 was a bit brutal maybe. But essentially it seems to be bound to a few screen models. The bug does exist, and that is sad of course. But we are far from a systematic, massive problem. It is indeed not linked to distro it seems, but really to some screens. And the Nvidia guy did not manage to reproduce it yet it seems. So it is probably not a massive bug either.
The point is more that it is not a bug that is anywhere as massive or systematic as you made it sound in your first message. Proof is, we seem to find more people without the issue than people with it on this very forum.
It also mitigate the idea that Nv is not doing QA since the problem seems to be a corner case, on a particular setup, on a few models amongst the many that exists. It is very hard to catch all those bugs, no matter how careful you are. Once again, considering they did not manage to reproduce it directly tend to show it is not trivial/easy to see.
Now, if it shows that the amount of people affected is not neglectable, then Nv defo should extend their QA to this, but it is hard to know in advance this kind of stuff.
Whatever you do, there will always be some bugs that pass through the testing, it is really unavoidable. Testing time is not infinite, and there will always be some corner cases creeping thru.

Your entire comparison is complete and utter nonsense.

Damn, what does vkd3d-proton have to do with it, if we're talking about drivers?

I do not care about VKD3D-Proton, like potential developers who want to want to release native games for Linux.

Joshua says the main obstacle is the driver and its support. I do not agree with his harsh statements.


Last edited by mphuZ on 2 Jun 2021 at 5:14 pm UTC

Um, no?

I have an RTX 3090 and my overall resolution is 5120x1440@165Hz (2x2560x1440@165Hz), with both connected over DisplayPort. Never once has it failed to boot. And I'm on 5.13-rc4 right now.

Well, this is an nvidia-recognized bug that is currently affecting many people across multiple distributions. And anyone it does affect is in for a rough day. The type of bug that leaves a sour impression on the company for those affected.

But you aren't having this issue, so I'm sorry I've wasted everyone's time.

The thing is, you misrepresented the situation.

Their new drivers crashes on boot if your montior is connected with DP and/or resoution greater than 1080p.

That's what you said. When in reality, the truth is "**if** you happen to own one of just a handful of monitor models, you're running a resolution above 1080p, *and* it's over DisplayPort, then you can have trouble booting on the current driver."

There are legitimately thousands of people running Linux on Nvidia GPUs above 1080p that aren't having this issue, and it's probably less than 1/10th of 1% of the Nvidia users on Linux that are experiencing this bug. But you decided to make a blanket unequivocal statement, which was false.

Your entire comparison is complete and utter nonsense.

Damn, what does vkd3d-proton have to do with it, if we're talking about drivers?

I do not care about VKD3D-Proton, like potential developers who want to want to release native games for Linux.

Joshua says the main obstacle is the driver and its support. I do not agree with his harsh statements.

Um, for one, even you never mentioned "native games." And the things Josh mentioned are absolutely relevant. vkd3d-proton has to work with the Vulkan driver. That's literally how it works. And if the Vulkan driver is trash, doesn't support extensions it should, etc., how is that not relevant?

Your tirade of a post about how what Josh said was "offensive" is blatant AMD worship. And you excuse their waiting 5 months to bring RT support to *just* their proprietary driver and not AMDVLK even though Nvidia had it on day one by saying "well who cares RT is a niche," but it's not just RT where AMD does this.

AMD hasn't released a GPU in the last 4-5 years where they supported all of its functions at launch on Linux. Not just in the userspace drivers, but in the amdgpu kernel driver. It took months and months for RDNA 1 to get overclocking/voltage control, and the same goes for RDNA 2, it just now got it. That's a basic functionality. And there are countless other functions that AMD didn't enable for new GPUs until months after launch. Like I said, they've not released a single architecture in the last 5 years where they've actually fully supported it on Linux at launch.

It's really not a good idea to worship a corporation like that.

you cant buy non TI
why the F do they make a TI then?

For 3070, good question.
For 3080 TI, according to LTT, it seems the supply of rtx 3090s is currently bound by the DDR6X supply

i meant because of miners. a hardware mining blocker would be more helpful

you cant buy non TI
why the F do they make a TI then?

For 3070, good question.
For 3080 TI, according to LTT, it seems the supply of rtx 3090s is currently bound by the DDR6X supply

i meant because of miners. a hardware mining blocker would be more helpful

All new models (including newly taped out older models) will come with one. Now, whether it will truly be solid enough, that it the question.