Felix Maier

Another issue I've found in the past is that wasm memory can't actually shrink. This means that once you've allocated a large chunk of memory, you can free it to...

I agree, a few years ago there was [this](https://hacks.mozilla.org/2018/10/calls-between-javascript-and-webassembly-are-finally-fast-%F0%9F%8E%89/) post regarding how mozilla managed to reduced the overhead of trampoline calls between Javascript and Wasm. I don't know if this...

I currently transition the project to vulkan 1.2, as long as that is in the process, I will keep this open as a reminder

I didn't add swapchain recreation yet. If I get back to this project, then I'll add it

@kvark thanks for the direction, but could you elaborate about number 2? Edit: Do you mean the different render backends?

For your interest, I've added a specification of the RT draft [here](https://github.com/maierfelix/dawn-ray-tracing/blob/master/RT_SPEC.md). DirectX and Vulkan Ray Tracing are very similar in their style and usage. - DXR seems to have...

I've made an example of the VK_KHR_ray_tracing extension [here](https://github.com/maierfelix/VK_KHR_ray_tracing), which I'll use as a base to port the current VK_NV_ray_tracing implementation in Dawn. Currently I'm mainly waiting for bug fixes...

@yyc-git The RT fork now uses VK_KHR_ray_tracing and is also included in the latest version of node-webgpu. If you want to try it, make sure you have the [Vulkan beta...

The RT fork now supports Ray tracing through the D3D12 backend. VK_KHR_ray_tracing and DXR are almost identical APIs, except 2 small differences I've found so far. DXR requires the maximum...

> For the record, I think it's totally fine for a sub-group to form that would develop this part of the API as an extension, as long as it doesn't...