GLSL VS score

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).

https://ossia.io uses widgets and qgraphicsscene for the main UI rendering and Qt rhi for the GPU pipeline, and it's performing well enough for our use-cases - I was working on it on a 1080p screen on a Pi4 recently and it certainly felt much much faster and responsive than chrome on the same hardware.

I use it for live c++ recompilation in https://ossia.io - all the code is in there. https://github.com/ossia/score/tree/master/src/plugins/score-plugin-jit/JitCpp

> I feel like visual programming gets a bad rap because of things like this. As an electronic engineer that used to love LabView and life long user of NI Reaktor and Max/MSP, those tools are fantastic if you don’t approach them with an imperative programming mindset.

aha, in the long run I ended up making https://ossia.io which is as VPL as it can get. Yet it still embeds a LOT of textual languages.

For me both VSCode and CLion lag heavily.. whenver I tried CLion it was completely unuseable on my project https://ossia.io which is only 500kloc (and I try to try it pretty much once a year since it was in beta)

https://ossia.io does some of it, I've been working on a new release that also supports the whole QtQuick stack in the node graph items but you can already combine videos & shader effects

In https://ossia.io with PCH, using clang, ninja, mold, and some artificial split in shared libraries for development builds, I get a compile-edit-run cycle of a couple seconds in general... I wouldn't say it's too much of a problem if you use the tools already available

If you're interested in multimedia https://ossia.io is always looking for new contributors!

Tools like Ossia Score, Chataigne and PureData (pd) can also help a ton in building interactive art and triggering other A/V software.

here's a simple example of how to do it in https://ossia.io score : https://streamable.com/wkklek