Direct3D Mesh Shaders

Nice we can party like it’s 1999!

It took 20 years to come full circle. Crazy. I assume it’s because early GPUs didn’t have the storage or processing power to accept the full scene geometry and culling was left up to the CPU.

 

Maybe hardware wasn't really ready for it but it is now?

 

Test new NV 440.23 driver on Turing on Windows insider 18970 with D3D12CheckFeatureSupport maybe it's enabled already?

 

Did the vector unit operate on work groups and have local memory?

 

Work probably differently but have the same function and it looks like it is a relief for developer.











And the other answer shows they are happy to go back to square one. A more exact term would be Mesh shading is an evolution of PS2 VU...

They would probably have been more happy to improve from the PS2 VU idea...

 

Even though GS was a misstake, it didn't stop the PS2's huge success with the weakest hw.

 

Based on the prior tweets I think GS meant Geometry Shader though when used while discussing PS2 I can see your interpretation.

 

Next step is Vulkan/DX including an Emotion Shader stage so nothing is left behind.

 

Fixed it for ya.

 

AMD has an ES stage when GS is used.

 

Was about time to get fixed function support for reprojection.

 

SIGGRAPH 2019: Applications of Mesh Shading with Dx12
This has the 2nd part of the talk as well, implementation of DX12 tessellation using mesh shaders.

 

NVidia Developer Program login is required to view the slides.

Here is the video of the talk - starts with the Asteroids demo:
https://on-demand.gputechconf.com/siggraph/2019/video/sig944-applications-of-mesh-shading-with-dx12/

The last year's presentations and papers:
https://forum.beyond3d.com/posts/2076010/

 

Interesting and read the other tweet about it Mesh shader against compute shader

Advantage Mesh shader because compute shader need a pretty big intermediate memory buffer.

 

Online documentation for D3D Mesh Shader API and Shader Model 6_5 is available on GitHub:

https://microsoft.github.io/DirectX-Specs/d3d/MeshShader.html
https://microsoft.github.io/DirectX-Specs/d3d/HLSL_ShaderModel6_5.html

Vulkan 1.1 Mesh Shaders extension
https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/chap24.html

 

Talk about mesh shaders

 

NetEase developer Thunder Fire Games, developers of Justice (MMO) have added Mesh Shaders to their rendering pipeline..allowing for over 1.8 billion triangles running at over 60fps @ 4K on an RTX 3060Ti.

Demo video:


Article/Interview:
https://developer.nvidia.com/blog/realistic-lighting-in-justice-with-mesh-shading/

Justice supports 8K DLSS, as well as RTXGI global illumination.

 

Holy crap, thought ue5 demo was already a nice demo.

 

It's a nice little demo for sure.

I think we're going to see some amazing looking stuff coming up in the near-ish future, once developers have all these advanced features ready in engine.. and development pipelines are well integrated.

They speak about high resolution textures being a must. To really show off the models at this high of a geometric density, you need high frequency textures to go along with it.. so you can see how Sampler Feedback Streaming plays into enabling this on a larger scale. They don't speak about supporting SF yet, at least not in the article, so I'd assume that is another thing they will be updating to there renderer in the future.

 

Isn't the big difference between the nanite demo and the mesh shaders that the nanite doesn't require the entire models in memory?