Friday, August 1st 2025

Intel Opens Up XeSS 2 to NVIDIA and AMD GPUs with SDK 2.1.0

Intel on Thursday released the XeSS 2 SDK version 2.1.0, with which it announced support for non-Intel GPUs. This would be any GPU that supports Shader Model 6.4, which are GeForce GTX 10-series "Pascal" or newer from NVIDIA, and Radeon RX 5000 RDNA from AMD, or newer. The update opens up not just super resolution (XeSS SR), but also frame generation (XeSS FG) and low latency (XeLL), however, using XeLL requires XeSS FG to be enabled, it cannot be exclusively used.

The release of XeSS 2 SDK would make it possible for game developers to update their binaries to support XeSS 2, and expose the feature-set to even non-Intel GPUs. At a hardware-level, XeSS 2 would rely on DP4a compute to run its super resolution and frame generation models. Only on Intel Arc "Alchemist" or "Battlemage" GPUs will the technology leverage XMX accelerators.
Source: Intel Graphics
Add your own comment

14 Comments on Intel Opens Up XeSS 2 to NVIDIA and AMD GPUs with SDK 2.1.0

#1
ZoneDymo
Intel imo is currently just a badly run company, bad choices...but their gpu devision is a glimmer of hope.
Currently on a rx7800xt so no need for an upgrade but when that time comes, I hope Intel has something interesting to go for.

Also while this is excellent news I just keep saying this, this is SUCH a boring time in gaming, pls lets just have 1 upscaler that fits all, one that works on older hardware but detects support on newer cards for more advanced features (shadermodel 6.4+ / AI cores) and then run the better version on those regardless of brand......
I just hate this mismash of support and then, if its supported, what version, its just so silly.
Like I played KF3's server test and FSR looked like crap, I have no clue what version it used but it just sucked, XeSS was much better (kinda blurry in motion but good enough)......and yet FSR (which we know is atleast V3 here) looks prefectly fine for 95% in GTA Enhanced.

Just these different versions and then different versions within the same ffing upscaler....its a mess, I want it to be over already!
Posted on Reply
#2
soder
I believe its a desperate attempt from intel to keep the GPU division alive by letting game studios to use their tech without even requiring an ARC GPU.
Seems the entire ARC divison is staying in front of the great scythe. The new boos can axe the entire GPU team in any second.
Posted on Reply
#3
Verpal
Tried DP4A XESS before and it is quite expensive to run, I wonder if DP4A frame gen would fare better?

Also, worth noting while Intel supports every GPU with Shader model 6.4, they did explicitly recommend RTX 30 or RX 6000 series or above.
Posted on Reply
#4
ToTTenTranz
IIRC for XeSS 1 the DP4A model was different than their XMX one in output quality.

Is this still true for XeSS 2 upscaling?


Regardless, for AMD handhelds with RDNA3+ forcing XeSS through optiscaler might be an excellent choice.
Posted on Reply
#5
RejZoR
As much shit Intel gets these days, props to their graphics division. It's nice to see FSR and XeSS being an open choice that works on all GPU's, even if there is a slight split on how the logic behind works since I know XeSS on Intel is different than on other vendors, but results are pretty similar. I wish AMD would do the same for FSR4 because that will help boost its presence in games if any GPU can run it which gives devs more incentive to include it in their game.
Posted on Reply
#6
john_
RejZoRAs much shit Intel gets these days, props to their graphics division. It's nice to see FSR and XeSS being an open choice that works on all GPU's, even if there is a slight split on how the logic behind works since I know XeSS on Intel is different than on other vendors, but results are pretty similar. I wish AMD would do the same for FSR4 because that will help boost its presence in games if any GPU can run it which gives devs more incentive to include it in their game.
AMD already offers FSR 3.1 to everyone. Opening up FSR 4 is either not technically possible and explains why it isn't offered to at least RX 7000 owners, or they have decided to take the Nvidia route this time. It does work for Nvidia.
Posted on Reply
#7
Mysteoa
RejZoRAs much shit Intel gets these days, props to their graphics division. It's nice to see FSR and XeSS being an open choice that works on all GPU's, even if there is a slight split on how the logic behind works since I know XeSS on Intel is different than on other vendors, but results are pretty similar. I wish AMD would do the same for FSR4 because that will help boost its presence in games if any GPU can run it which gives devs more incentive to include it in their game.
SDK for FSR4 is scheduled for H2 this year, and we are just 1 month in it. There is still time to be released.
Posted on Reply
#8
Kaotik
john_AMD already offers FSR 3.1 to everyone. Opening up FSR 4 is either not technically possible and explains why it isn't offered to at least RX 7000 owners, or they have decided to take the Nvidia route this time. It does work for Nvidia.
The reason why FSR 4 isn't available for RX 7000 is performance. RDNA 3 doesn't support FP8, which FSR 4 uses, which means they'd have to run it in FP16 precision, which doubles the cost.
Someone actually did "hack" FSR 4 to work on RX 7900 XTX on Linux and it was barely faster than native at 4K Quality, at lower output resolutions it didn't offer performance benefits over native.
Posted on Reply
#9
RejZoR
MysteoaSDK for FSR4 is scheduled for H2 this year, and we are just 1 month in it. There is still time to be released.
I mean, if devs weren't lazy as f**k (looking at you Blizzard) and upgraded FSR from ancient 2.2 to a bit less ancient FSR 3.1 there would be no need to have FSR4 natively implemented, it would be applied via driver.
Posted on Reply
#10
john_
RejZoRI mean, if devs weren't lazy as f**k (looking at you Blizzard) and upgraded FSR from ancient 2.2 to a bit less ancient FSR 3.1
Maybe they didn't cared to offer support for that 10% of their customers using AMD/Intel hardware. They got payed in full from those customers, they just didn't cared to serve them.
Or maybe FSR 3.1 is not compatible with Nvidia's libraries or Nvidia's financial support.
I was reading this yesterday
RDNA 4's Unreal Engine 4 ray-tracing stutters may not be AMD-specific | Tom's Hardware
with the subtitle
"Even Intel's B580 suffers from the same stuttering issue."

Then in the article with big letters we can read this
Both games use a proprietary version of UE4 built by Nvidia
and I have to wonder what kind of incompatibilities do developers find with newer AMD(and Intel) software and hardware when using proprietary libraries from Nvidia. Maybe those libraries are not just unoptimized for use with AMD or Intel hardware, they are also incompatible with anything new or somewhat new from the competition. Maybe those libraries aren't updated often enough to offer better compatibility with latest versions of FSR or XeSS, or be 100% compatible with RDNA4 or Battlemage, so developers don't integrate AMD or Intel features fast enough to avoid ending up with a problematic game.
Tech Yes City also discovered that both games run off of an Nvidia RTX branch of Unreal Engine 4, featuring Nvidia-specific ray-tracing technologies tailor-made for Nvidia GPUs. This is different from the vanilla branch of Unreal Engine 4, which has its own set of proprietary ray tracing technologies that are based on DXR, not NvRTX.
P.S. The comments in the article are sad and funny at the same time. People just realizing what is happening the last 15 years.
Posted on Reply
#11
Event Horizon
ToTTenTranzIIRC for XeSS 1 the DP4A model was different than their XMX one in output quality.

Is this still true for XeSS 2 upscaling?
It's mentioned that there is still an image quality gap between the two models, but I haven't seen any side-by-side comparisons for 2.x yet. Image quality on XeSS 2.x is pretty decent now for all vendors, so maybe the gap between the dp4a and xmx models has shrunk.
Posted on Reply
#12
Mysteoa
RejZoRI mean, if devs weren't lazy as f**k (looking at you Blizzard) and upgraded FSR from ancient 2.2 to a bit less ancient FSR 3.1 there would be no need to have FSR4 natively implemented, it would be applied via driver.
I don't think devs are lazy, it's just not a priority of management. Why spend money and dev time on something with little to no money return, instead of working on the next update/expansion?
AMD is also partly responsible, they could always offer to help with the implementation. It is possible that they did, but we would never know.
Posted on Reply
#13
Visible Noise
john_and I have to wonder what kind of incompatibilities do developers find with newer AMD(and Intel) software and hardware when using proprietary libraries from Nvidia. Maybe those libraries are not just unoptimized for use with AMD or Intel hardware, they are also incompatible with anything new or somewhat new from the competition. Maybe those libraries aren't updated often enough to offer better compatibility with latest versions of FSR or XeSS, or be 100% compatible with RDNA4 or Battlemage, so developers don't integrate AMD or Intel features fast enough to avoid ending up with a problematic game.
AMD and Intel are free to maintain their own branch of UE just as Nvidia has.

Actually, with AMD having declared themselves a software company they should have done it already.
Posted on Reply
#14
Event Horizon
XeSS 2.1 is an easy upgrade over older versions by replacing the dll with the one from the 2.1 SDK. No need to wait for a game update. Try it out (on single player games).
Posted on Reply
Add your own comment
Nov 16th, 2026 08:35 CST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts