![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
That might not be that odd of an idea. Apple's MetalFX use's elements of FSR for it's AI enhanced upscaler as well.
Looking at the list of presenter (that include someone from Nvidia and AMD), feel like Microsoft will have one that use NPU (so not entierelly like FSR) in their AI push and bring usecase for NPU present in laptop, youtube and other streaming video upscaling as well has some ways to make it easier for game to use one of those solution (like DLSS and FSR) in a very similar way for the game engine, maybe not in Direct3D, more like in their many API-toolkits around it that they have in the DirectX family.
Could be but Nvidia has been working with Microsoft internally on it for 2 years now. So I expect it's an evolution or forking of the Streamline program.
Not really, honestly Microsoft doesn’t have the talent on hand to re create the wheel here, whatever Microsoft could do the other three could do better. Microsoft creates the API that’s what they’re good at, let the vendors figure out how to best implement it on their hardware.
It is already announced (to be something between the game engine and the dlss-fsr of the world) and not their own upscaler, it is in their Agility SDK, can see it make FSR 2 on Xbox and DLSS-Xess support on PC for game that only launch on both not having to support change in the surface of DLSS-FSR-Xess to update them if they ever happen, OS update sdk able to take care of it... maybe ?
Well we all know what MS based DX12 on so I wouldn't be surprised if they continued that evolution as it help defeat monopolistic practices.
DX12 was not based on Mantle, AMD released Mantle in late 2013, and DX12 was initially released only a few months later in early 2014. Microsoft started developing DX12 while they were still actively supporting DX10 and DX11 still hadn't been released yet.
That was on queuing.
I disagree. AMD wanted Mantel to be their break from an Nvidia dominated, driver fuckery, DX11 that they had mastered.
I don't know how much of that was Nvidia fuckery or Balmer fuckery, but fuckery was indeed a foot.
AMD called out nothing. Don't know what you're remembering. MS clearly stated ATT, that they had NO intentions of moving beyond DX11.
Not quite, they said it was no longer evolving, and they used that as their explanation as to why they killed off their XNA platform.
The fuckery was Nvidia's Nvapi, which was their API that ran on top of DX11 that gave Nvidia an edge in performance. Think of it like EAX and DirectSound or OpenAL. It's also now a problem for those using Linux and wanting to play Windows games with this API.
And AMD didn't have DX12 drivers ready until early 2015, months after NVIDIA had their drivers ready.
Yes, because the goals of the API were the same. That doesn't mean Microsoft based DX12 on Mantle. You can only write how to do things like command list queues a limited number of ways.
No, it was only DX11.2, the Xbox One S (Aug 2, 2016) got the Durango 2 and that had DX12 but developers didn't have the tools then to make use of it until quite a while after its release.
I do not know enough to say what this mean in that context:
Both. The Xbox One had some features bolted on that were integrated into DX11.3 and later 12, so it had limited compatibility but not full DX12. One of the core features brought in was better multi-core support which lets DX12 titles do a better job of breaking up the master thread.
This will not be open, but developers don't have to build multiple upscaling interfaces into game engine
This was badly needed to keep people from being upset about their favorite upscaler not being included in their games.
And it prevents developers from being in a place where it’s contractually tricky to add both.
Good question and maybe??
No. That nvapi only ran when an Nvidia card was installed. When an AMD card was installed, AMD's api would run.