News for hackers. Stuff that matters.
Re:Blender 5.3 released with Gaussian Splat support by Boxxed on Tuesday November 10, 2026 @11:54AM (#50442979)
Pretty sure they use SDFs, not triangle or gaussian splatting
Re:Blender 5.3 released with Gaussian Splat support by debugnik on Tuesday November 10, 2026 @12:00PM (#50443069)
If I recall their talk correctly, models are unions of SDFs, which get sampled into a point cloud, and each point gets splatted as another SDF primitive called a "fleck".
Re:Blender 5.3 released with Gaussian Splat support by guitarlimeo on Tuesday November 10, 2026 @12:11PM (#50443204)
Ah thanks for the correction. The splat terminology they also use confused me.
Re:Blender 5.3 released with Gaussian Splat support by cma on Tuesday November 10, 2026 @02:28PM (#50445076)
I think SDFs is the data underneath, but baked into SDF voxel tiles at runtime and not always evaluating SDF shapes. The SDF tiles still get splatted.

At one point it used triangles for the large splats, and still compute shaders for the small ones due to quad overdraw. I'm not sure if the final version stuck with that or went all compute, but quad complexity is also why nanite does compute shaders for small triangles and traditional rasterization for the larger ones.

Re:Blender 5.3 released with Gaussian Splat support by mschuetz on Tuesday November 10, 2026 @02:37PM (#50445199)
In my experience it isn't really about quad overdraw/helper lanes, but rather about primitive assembly. On my RTX 4090, vertex shaders max out at about 20M tris/ms, while mesh shaders, which bypass primitive assembly, can reach 40M tris/ms.

But it's a bit difficult to find the exact reason since profilers won't really tell you a concrete bottleneck when drawing vast amounts of tiny tris.