VK-GL-CTS VS compute_rasterizer

Minecraft Java edition uses the OpenGL graphics engine, which was created by the Khronos Group. Vulkan was also created by them.

In the C++ standard, there is nothing. But if you are searching for something that can qualify as a standard, try the Khronos Group libs, here: https://www.khronos.org/

The caretaker of the SYCL spec is Khronos a non-profit standards body that is home to several projects focused on graphics, machine learning, parallel computing, VR and visual computing. You will note that all these pieces work together to build frameworks. Some of the more visible ones that you might be familiar with are openGL and Vulkan.

Why does the Khronos group have so many standards? Do they really need all this?

It's more than that, it's the official conformance tests:

https://github.com/KhronosGroup/VK-GL-CTS/blob/main/external...

https://www.khronos.org/ is the open standards body in charge of OpenGL and Vulkan. They’re pretty far from being a big commercial product maker ;)

The Haptics Industry Forum (HIF) and The Khronos® Group have entered into a cooperative liaison agreement to foster synergy between the two organizations to encourage the integration of advanced haptics functionality into the Khronos OpenXR™ open standard for portable augmented and virtual reality, to enable broad availability of haptics in the metaverse and beyond. This agreement enables HIF and Khronos to collaborate with a shared goal to enable broad, cross-platform access to next-generation haptic feedback in XR applications, enabling rich multisensory experiences to reach beyond 3D visuals for the eyes and spatial audio for the ears – and include expressive haptics for touch.

The true metaverse concept (not rebranded private apps like roblox, vrchat, second life, decentraland or horizons) will be based on an open set of standards, which are still in development.

Compute rasterization has the potential to be faster if you do it correctly but unless you're drawing a lot of points (hundreds of millions or even billions) just use GL_POINTS.

Write the application first and find out; you're not going to be bottlenecked by the GPU for a very long time, as even several hundred bodies will become a major CPU bottleneck until you implement some acceleration structures. If you do get to the point of being able to simulate more bodies than you can render (for what it's worth, I've never gotten close even with a 2-body approximation), you can explicitly double-buffer your application or look into persistent mapping. Beyond that, you can actually achieve faster point rendering by writing your own compute-based point cloud rasterizer, but obviously this is not something to take on lightly.

If you find traditional OpenGL techniques too slow, you can gain a 10-100 fold speedup by using compute shaders to manually rasterize your point cloud: https://github.com/m-schuetz/compute_rasterizer

Another example: https://github.com/m-schuetz/compute_rasterizer

well said! I think UE5 does use compute shaders for very small triangles. The other use case I know of is rendering dense point clouds (with more than 100 million points in the scene, see: https://github.com/m-schuetz/compute_rasterizer)

This is beyond your needs right now (you should take care of the basic first), but you might be interested in this. Turns out, a compute shader can rasterize big point clouds way more efficiently than using GL_POINTS, but don't look into that until you've identified a performance issue first.