NVIDIA did a big splash at Computex 2021 with the expected announcement of two new top-end GPUs and quite a big surprise for Linux gaming with the official inclusion of NVIDIA DLSS for Proton. Don't know what Proton is? Check out our dedicated Steam Play Proton section.
They said in their official email press release that this is a collaboration between "NVIDIA, Valve, and the Linux gaming community". Currently DLSS is already in the NVIDIA Linux driver (since July 2020) but it doesn't work with Proton right now but that's about to change, so you'll be able to use "the dedicated AI cores on GeForce RTX GPUs to boost frame rates for their favorite Windows Games running on the Linux operating system". NVIDIA said support for Vulkan games is coming this month, with DirectX titles coming "in the Fall".
An NVIDIA engineer also sent us over the links to the freshly squeezed and juicy Pull Requests to get things moving for Proton and Wine:
- dxvk-nvapi: Add to Proton #4877
- loader: Set default regkey for NVIDIA NGX FullPath #111
- proton: Copy DLLs provided by the NVIDIA driver into prefix #4878
So the upcoming NVIDIA 470 driver series should not only have the Wayland support work in, to allow for hardware accelerated GL and Vulkan rendering with Xwayland but also to extend DLSS on Linux to Proton too. That's going to be their biggest driver release for some time.
As for the new GPUs, their new top of the line gaming flagship is the GeForce RTX 3080 Ti which isn't quite as expensive as the 3090 while still offering up some ridiculous performance.
GeForce RTX 3080 Ti - it will be available June 3rd starting at $1199. Here's a comparison:
| RTX 3090 | RTX 3080 Ti | RTX 3080 | |
|---|---|---|---|
| NVIDIA CUDA Cores | 10496 | 10240 | 8704 |
| Boost Clock | 1.70 GHz | 1.67 GHz | 1.71 GHz |
| Memory Size | 24 GB | 12 GB | 10 GB |
| Memory Type | GDDR6X | GDDR6X | GDDR6X |
RTX 3070 Ti - it will be available June 10th starting at $599. NVIDIA said the 3070 has been their most popular of the Ampere line so they've decided to turbo charge it too.
Here's another comparison:
| RTX 3070 Ti | RTX 3070 | |
|---|---|---|
| NVIDIA CUDA Cores | 6144 | 5888 |
| Boost Clock | 1.77 GHz | 1.73 GHz |
| Memory Size | 8 GB | 8 GB |
| Memory Type | GDDR6X | GDDR6 |
While they both look and sound amazing, the question is: will there be any stock? We're fully expecting them to completely sell out in minutes just like everything else over the last year. NVIDIA announced that both cards will be shipping with a "reduced Ethereum hash rate" to make them less desirable to miners. Will it be enough though?
Watch the full key note below:
YouTube videos require cookies, you must accept their cookies to view. View cookie preferences.
Direct Link
Direct Link
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
Quoting: x_wingQuoting: 3zekielSo 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
QuoteAMDVLK 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.
0 Likes
Quoting: 3zekielI 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
QuoteAMDVLK 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.
0 Likes
gardotd426 Jun 2, 2021
Quoting: mphuZIt 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.
0 Likes
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
0 Likes
Quoting: kfpenguinWell, 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
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.
1 Likes, Who?
fearnflavio Jun 2, 2021
Quoting: kfpenguinWell, 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
I have a 3440x1440 screen with DP and it works fine. Even freesync/gsync is working perfectly with latest drivers.
0 Likes
gardotd426 Jun 2, 2021
Quoting: kfpenguinWell, 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
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 June 2021 at 9:23 am UTC
0 Likes
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.
Farewell green team, you served me well over the last 2 decades but your time is up.
0 Likes
Quoting: gardotd426This 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.
1 Likes, Who?
Patreon
PayPal
See more from me