Vulkan-Guide VS GLSL

Vulkan directly supports many platforms, and also supports MacOS and IOS through porting tools.

You have access to atomics in vulkan

You might want to take a look at our Vulkan guide. The linked chapter has common terms for Vulkan, DirectX and Metal.

Vulkan has WSI, which is roughly equivalent to GLX or EGL in the OpenGL world.

https://github.com/KhronosGroup/Vulkan-Guide/blob/master/cha...

Vulkan Guide for more

Yes The gist is: you don't actually save any time trying to not-rerecord, and it limits your ability to do many basic real optimizations, like frustum culling. https://github.com/KhronosGroup/Vulkan-Guide/blob/master/chapters/common_pitfalls.md#recording-command-buffers

Looks like there is a lot more work before it can be used for anything more than dash entertainment system.. https://github.com/KhronosGroup/Vulkan-Guide/blob/master/chapters/what_vulkan_can_do.md#safety-critical

You're looking for this repo

You have access to physical (u64) global memory pointers through buffer_reference in GLSL, note you should be using buffer_reference2

On April 27, 2023 the Vulkan® Ray Tracing TSG released the VK_KHR_ray_tracing_position_fetch extension, which exposes the ability to fetch vertex positions from an acceleration structure hit when tracing rays. The SPIR-V SPV_KHR_ray_tracing_position_fetch and GLSL GL_EXT_ray_tracing_position_fetch extensions have also been released to provide SPIR-V and GLSL support for this functionality.

You can also have general extensions that are only supported on some hardware, for instance NVIDIA supports all of these extensions on OpenGL that add support for Vulkan's thread subgroup operations while AMD only supports these extensions and a few others that add support for similar features to the extension that NVIDIA supports, but with way more restrictions.

GL_NV_ray_tracing is a vendor extension, but it does exist.

According to this document, one should be able to extract those values through

The reports of my death are greatly exaggerated

https://github.com/KhronosGroup/GLSL/blob/master/extensions/...

I don't think there's away. For Vulkan, there's GL_EXT_nonuniform_qualifier which allows you to index with gl_InstanceIndex but AFAIK it's not available for OpenGL.

AMD hardware works a little differently, and for that you have to write a waterfall loop with subgroup instructions to get the correct behavior (since GL_EXT_nonuniform_qualifier doesn't exist in OpenGL GLSL). The loop might look like this (you would use it the same way as NonUniformEXT in Vulkan GLSL).