Felix Maier

This project is no longer maintained and is heavily outdated, so please continue inside a fork.

When I continue working on the ray tracing extension then I'll probably add support for ray queries. Also please post issues regarding ray tracing [here](https://github.com/maierfelix/dawn-ray-tracing)

I'm not sure what you're referring to, do you mean [this](https://github.com/KhronosGroup/GLSL/blob/master/extensions/ext/GL_EXT_nonuniform_qualifier.txt)?

I don't remember if I actually enabled this extension, why do you need unbound textures?

I see, so you can use `NonUniformEXT` as a workaround as I did [here](https://github.com/maierfelix/tiny-rtx/blob/master/assets/shaders/ray-closest-hit.rchit#L67) for example. The problem is that this approach doesn't support textures of different sizes. > storage...

There are different ways to implement it, here is an idea: - 1 shader array containing texture information (`width`, `height`, `offset`) - 1 shader array containing the texture data. Each...

Not yet, I'm not sure how important they are for ray tracing. Also please post issues regarding ray tracing [here](https://github.com/maierfelix/dawn-ray-tracing)

The project was deprecated in favor of the chromium's team effort to create [official node bindings](https://dawn.googlesource.com/dawn/+/refs/heads/main/src/dawn/node/). Also at some point this project only acted as sort of a playground for...

I don't know the state of the official node bindings, but there was a discussion before to move the webgpu npm package over to the dawn team and let them...