RTX vs FFX – Acronyomican!

In my limited experience attempting to force the notoriously fickle and hyper critical gaming industry to universally adopt one arcane company’s proprietary innovations usually ends with the latter being compelled to either shrewdly compromise or embarrassingly capitulate. by a similar token, when the task of communicating with the “innovator’s” developers becomes as hard as actually implementing the “technology” they’re providing, it’s only a matter of time before “open source” fills the void! As much for my own sanity as a researcher’s point of reference.


Fidelity FX is to RTX what FSR is to DLSS. The former pairing being a collective monikers respectively defining AMD’s and Nvidia’s algorithmic image enhancing techniques and the latter, two specific such techniques.

I appreciate that “RTX” was originally conceived as a “feature identifier” for Turing’s real-time raytracing abilities but since Nvidia appears to have rebranded “RTX” as a “platform” and extended the term to account for the “AI Candy” enabled by its post-Pascal “Tensor Cores” – see quotes and information on the following pages (https://developer.nvidia.com/rtx, “Only NVIDIA’s RTX platform includes dedicated RT Cores for ray tracing and Tensor Cores for AI that enable ground-breaking technologies at breakthrough speed.” And there is so much confounding conflation across the tech community regarding such article and video titles as “Fidelity FX Vs. DLSS”

https://www.youtube.com/watch?v=Y-z-6147xJE&ab_channel=TestingGames, that I feel an up-sampling of clarity is compulsorily to avoid terminal confusion.

IMPORTANT: Raytracing is implemented via multiple API’s including Microsoft’s DXR, Nvidia’s “OptiX” and Vulkan (evolved from AMD’s “Mantle”). Moreover, performance discrepancies between each company’s products is dictated by a combination of the processing power provided by their GPU’s dedicated subset of hardware components – A Radeon card’s “RT accelerators” compared to The Geforce’s “RT Cores” – combined with broad range of driver optimisations.