Nvidia’s decision to rebuild Quake II as a ray tracing title was, in my opinion, a really clever way to show off what the feature was capable of, while simultaneously giving people a reason to return to the well-regarded classic title. Up until now, however, the only gamers who could enjoy it were folks who owned an Nvidia RTX GPU. While some games will run ray tracing on Pascal, Quake II RTX isn’t one of them.
Now, however, AMD fans have an opportunity to enjoy Quake II RTX as well, apparently with Nvidia’s explicit help. Any GPU that supports the Vulkan Ray Tracing extensions maintained and developed by the Khronos Group can also run Quake II RTX. On AMD’s side of the fence, that support appears to be limited to the RX 6000 series, at least for now.
Nvidia’s support is much wider. In addition to Ampere and Turing, Vulkan Ray Tracing is also supported on the GTX 1660 family of GPUs, the Volta-based Nvidia Titan V and the Quadro GV100, and on Pascal GPUs with at least 6GB of RAM. If you haven’t seen the Quake II RTX launch trailer, we’ve embedded it below.
Nvidia actually did some of the heavy lifting to bring ray tracing to Vulkan in the first place. There are already existing tools in place to assist with translating DX12 calls and HLSL (High Level Shader Language) code into Vulkan and SPIR-V, respectively. Nvidia’s specific contribution to the project was to add ray tracing support to Microsoft’s open source DirectXCompiler, which is commonly used to port HLSL code to Vulkan.
In other words, Nvidia’s open source work is a key part of why AMD GPUs can now run Quake II RTX. This kind of ‘coopetition’, if you will, is a key part of ensuring standards are widely supported and making certain gamers can expect certain features on a wide range of systems. In theory, developers that already have a Vulkan and a DX12 path could keep Nvidia RTX support for one API and support both Nvidia and AMD in Vulkan. So far, we haven’t heard much about whether or not RTX-enabled games will receive an update to allow AMD to use ray tracing, or how much additional optimization is required to make use of the feature on RDNA2 GPUs as opposed to Turing / Ampere.
For now, it doesn’t look as though AMD has any plans to enable ray tracing on the 5700 or 5700 XT. One thing we know is that the performance impact of enabling ray tracing is heavy, especially on GPUs that weren’t designed to support it. On paper, Nvidia supports a huge range of cards. In practice, most of the Pascal cards other than the 1080 Ti and maybe the GTX 1080 have often proven too slow to run ray tracing effectively. Even if you turn down other detail levels enough to get the feature running, you may not feel ray tracing makes up for the losses in other places.
It would be nice to see AMD offer Vulkan support for RX 5700 and 5700 XT cards, but keep in mind, the 6800 XT and 6800 lag Nvidia’s ray tracing performance already. It’s entirely possible that the reason the company isn’t enabling ray tracing support in its lower end products is that it can’t guarantee a high-quality experience.
Either way, if you want to check out Quake II ray traced, AMD’s beta drivers with Vulkan RT support can be downloaded here, while Nvidia’s beta driver with the same can be downloaded here. For now, the only title using Vulkan Ray Tracing is Quake II RTX, as far as I know, but Khronos has designed the standard for use across computers and mobile devices and is hoping for robust uptake, long term.
SpaceX Launches ‘Better Than Nothing’ Starlink Beta
Those lucky few who have gotten invitations to try the service will have to pay a hefty up-front cost, and the speeds aren't amazing. Still, it's a new generation of satellite internet.
Apple’s New M1 SoC Looks Great, Is Not Faster Than 98 Percent of PC Laptops
Apple's new M1 silicon really looks amazing, but it isn't faster than 98 percent of the PCs sold last year, despite what the company claims.
Apple Cuts Fees in Half for App Store Developers Earning Less Than $1 Million
Going forward, Apple's customary 30 percent cut of sales on the iOS platform will drop to just 15 percent for smaller developers. Epic, however, claims this is just an attempt to split the developer community.