What's New in Direct3D 11.2 http://channel9.msdn.com/Events/Build/2013/3-062

Any hope, wish-list?

other related sessions:

• Massive virtual textures for games: Direct3D Tiled Resources http://channel9.msdn.com/Events/Build/2013/4-063
• DirectX Graphics Debugging Tools: http://channel9.msdn.com/Events/Build/2013/3-141
• Innovations in High Performance 2D Graphics with DirectX: http://channel9.msdn.com/Events/Build/2013/3-191
• Unlocking the power of DirectX in apps that use XAML: http://channel9.msdn.com/Events/Build/2013/4-065

EDIT:

slides and videos are up:

• What's New in Direct3D 11.2 http://channel9.msdn.com/Events/Build/2013/3-062
• Massive Virtual Textures for Games: Direct3D Tiled Resources http://channel9.msdn.com/Events/Build/2013/4-063
• Unlocking the Power of DirectX in Apps That Use XAML http://channel9.msdn.com/Events/Build/2013/4-065
• DirectX Graphics Debugging Tools http://channel9.msdn.com/Events/Build/2013/3-141
• Innovations in High Performance 2D Graphics with DirectX http://channel9.msdn.com/Events/Build/2013/3-191

nothings exciting here... http://msdn.microsoft.com/en-us/library/dn312084(v=vs.85).aspx and dxgi 1.3 http://msdn.microsoft.com/en-us/library/dn280344(v=vs.85).aspx

if AMD or NVIDIA ask to buy a new GPU for this, they can suck my balls..

It appears that the only new GPU feature is tiled resources, which sounds like an interface for PRT without the shader side of things. The rest of it is just shader compiler stuff.

Most of changes of D3D11.1 were some useless and old dx9 formats (with cap bits), a shader tracing API (they could provide it with a simple remapping their own proprietary tracing apis), 3d stereo (no need to changes, AMD has HD3D, nvidia has 3D Vision Surround), UAVs on all shader stages (and openGL has a similar feature...).. the rest is quite a big rename of interface, structs and functions.. the most cool and exiting feature was in fact UAVs on all shader stages, and no-one provides it to the "old" dx11 cards (AMD still lack of full opengl 4.3 support too, but not nvidia).

the funny is that half of AMD WDDM 1.3 cards are just simple, "old" and rebranded DX11 GPUS (mostly VLIW4, but there are VLIW5 cards too as I read in the ini file of the last leaked drivers)...

Of course Windows 7 is dead with vista in MS plans... And they kill PIX too...

let's see what happens, but I don't feel confident..

edit: the funniest is that Microsoft still doesn't provides some "cool" APIs and tools that Chuck Walbourn post around the web (not only DXTK and DXTex, but SSE3/4AVX/FMA extension support to DXMath, SHM library, updated BC6HBC7Encoder etc..).. the new Windows SDK lacks of everything of that..

Input assembler moved completely into the vertex shader. You bind resources of pretty much any type to the vertex shader, access them directly via texture look-ups. Would make things a lot simpler and more flexible IMHO. Granted you sort-of can do this already, but I'd be nice if the GPUs/drivers were optimized for it.

GPU's already work this way. The driver generates a small bit of shader code that runs before the vertex shader (AMD calls it a fetch shader), and all it does is load data out of the vertex buffer and dump it into registers. If you did it all yourself in the vertex shader there's not really reason for it to be any slower.

Depth/stencil/blend stage moved completely into the pixel shader. Sort of like UAVs but not necessarily with the ability to do 'scatter' operations. Could be exposed by allowing 'SV_Target0', 'SV_Target1' ect... to be read and write. So initially its loaded with the value of the target, and it can be read, compared, operated on, and then if necessary written.

Programmable blending isn't happening without completely changing the way desktop GPU's handle pixel shader writes. TBDR's can do it since they work with an on-chip cache, but they can't really do arbitrary numbers of render targets.

Doing depth/stencil in the pixel shader deprives you of a major optimization opportunity. It would be like always writing to SV_Depth.

I'm interested in the low-latency stuff. I heard about it some time ago, I was thinking it was just a rumor. I wonder if it'll turn out to actually be useful. Preferably soon.