There is no "NVMe > PCIe > GPU" route. That feature didn't make it into Windows 11 yet. It's in any case "NVMe > PCIe > RAM > PCIe > VRAM". Just the used APIs (Overlapped + Copy via compute shader / IORing + Copy via Copy Engine) differ with "DirectStorage" Off / On. GDeflate is merely yet another compute shader chained - and will also be naturally stalled by the copy on the wrong engine in the "non-DirectStorage" path.
Yea, it exacerbates the stuttering that happens every camera cut too.
Clearly one game with NVIDIA losing performance is enough proof of Microsoft being at fault
Multiple games. Ratchet and Clank as well. Basically... every game which used GPU decompression.Clearly one game with NVIDIA losing performance is enough proof of Microsoft being at fault
First we need to see benchmarks with AMD and Intel hardware to see if they behave the same.
www.computerbase.de
Doesn't matter how they behave. Was DirectStorage made to only benefit AMD/Intel?First we need to see benchmarks with AMD and Intel hardware to see if they behave the same.
Ratchet & Clank didn't show performance degradation with DirectStorage on AMD back in the day, couldn't find updates if it has changed since
Ratchet & Clank: Rift Apart: Ohne DirectStorage gibt es mehr FPS auf GeForce-GPUs
Ratchet & Clank: Rift Apart unterstützt als eines der ersten Spiele DirectStorage. Offenbar gibt es aber auf Nvidia-Grafikkarten Probleme.
Got any other links to games with GPU decompression and preferably benchmarks of said games with AMD, Intel and NVIDIA, not just NVIDIA?
Of course it matters
No, but if only NVIDIA loses performance the problem is far more likely NVIDIA than API/MS.
What came first, the API or Nvidia RTX gpus? That API also uses GDeflate.. from Nvidia. Pretty pathetic that the API was designed in such a way that doesn't work well with the vast majority of GPUs out there. Is that not on Microsoft?
No, if NVIDIA is having issues and others are not, it's on NVIDIA.
Doesn't change the fact that this API was designed by Microsoft to work with these GPUs.. and clearly it doesn't without issues. It's the API and Microsoft's fault.. plain and simple. If it doesn't work well with the majority of GPUs out there... then don't release it into the world while acting like it will improve things for them.. like Microsoft did.No, if NVIDIA is having issues and others are not, it's on NVIDIA.
It doesn't matter if their cards are "vast majority" or not, nor which came first; if your cards can't support it properly don't claim support for it until they can.
What you're saying sounds like you're suggesting everyone should just bend over backwards for NVIDIA
"The problem" is that Nvidia doesn't have gobs of unused h/w sitting idle w/o async compute which means that when you put that onto Nvidia h/w it takes performance from what was running on it previously (i.e. graphics).
You got it all reversed. API doesn't claim to support cards, cards claim support for API.
"Like all DirectX technologies, with DirectStorage, Microsoft is working to ensure that gamers have great options for compatibility and performance for their hardware."
For NVIDIA, AMD seems to be doing just fine with no such reports. Like I said, looks like a NVIDIA problem. Intel is unknown, haven't seen any reports either way."Like all DirectX technologies, with DirectStorage, Microsoft is working to ensure that gamers have great options for compatibility and performance for their hardware."
GPU decompression has been awful so far.. with terrible frametime spikes. That wasn't in any of MS marketing.
