"We use the word 'politics' to describe the process so well: 'Poli' in Latin meaning 'many' and 'tics' meaning 'bloodsucking creatures'."

Metaballs 2
Sunday, August 25, 2019 | Permalink

It's been quite a while, but now I have a new demo available.

This demo explores the new Mesh Shader pipeline available in NVIDIA Turing GPUs. It is a bit similar to my old Metaballs demo from 2005, except much greater mesh density and a lot more balls, and implements the Marching Cubes algorithm on the GPU instead of on the CPU.

Also noteworthy is that this demo is based on a new framework I've been working on for a while, which is based on DX12 and Vulkan. This particular demo uses Vulkan, but I plan to release more demos in the future based on DX12 as well, depending on what makes more sense for a given demo.

Some of the code in this framework has been more or less just adapted from code in my previous framework, like model loading and other utils, but a lot of stuff is new also. I spent probably a little too much time on putting in SIMD support in various places, like the vector classes and image utilities, but it's fun exploring. But the biggest difference is of course implementing a renderer for DX12 and Vulkan with a completely new abstraction, a relatively thin layer over the commonalities of these APIs. This is based on modern concepts like pre-built pipeline objects, descriptor sets, root constants etc. These APIs are not stable as I'm still exploring a lot, so I expect things to change as I add more stuff that I need for future demos. There are plenty of gaps in functionality.

Another new thing in this framework is a PipelineCompiler. This allows you to specify your root signature with a clear syntax together with all shaders and constant buffer structs in the same .pipeline file so that shaders and C++ code links up together minimizing risk for mismatch. The PipelineCompiler compiles all shaders, automatically generating the resource binding according to the specified root signature, and outputs a header file for the C++ code to use. In this header you will find the binary code for the shaders and resource binding enums matching what you put in the .pipeline as well as the constant buffer structs, so that the shader and C++ code can agree on inputs. Earlier frameworks relied on runtime shader compilation, but with this framework the shaders are precompiled and linked into the exe file of the demo. To see this in action, check the MarchingCubes.pipeline file in the new Metaballs2 demo.

Enjoy this release. Everything free and open source as usual.

Name

Comment

Enter the code below



Nuninho1980
Tuesday, August 27, 2019

I hope to read only 1 or 2 comments (except Humus as you) in this year because GeForce RTX is too expensive - NVIDIA is shameful. GF RTX 2080 non-Ti and 2080 Ti would cost max US$600 and max US$800~US$900 respectivately for avoid shameful.

ockiller
Friday, August 30, 2019

So glad to see a new demo from you!

IMHO that's a good use case for the new task and mesh shaders. I'm eager to see how it compares to an compute path.

Mindbody Matrix Pain Relief Cream Review
Thursday, July 9, 2020

It comes in different forms and we call it by different names: headaches, menstrual cramps, joint or arthritis pain, gout, fibromyalgia, etc. And although we do not like pain, pain is really a friend, a warning or alarm system that something needs attention.
http://www.supplementexpertreview.com/mindbody-matrix-pain-relief-cream-review/