Robert Stewart

@TimonPost Thanks for the explanation! A few of the main things I'm interested in is timing, latency and especially bandwidth (packet overhead). The reason I'm comparing is because I'm writing...

Just want to say, I think adding raytracing makes sense, it seems to be the way forward with graphics. AMD, NVIDIA and INTEL are all adding hardware support for raytracing,...

I'm currently running into this issue. Do you know how much work might be involved to fix this?

Just confirmed that rtp-to-webrtc also has the same issue, again the eqv. example works from webrtc-rs, so the ivf and rtp packets are both valid.

There seems to be twcc code here now webrtc/interceptor/src/twcc. However there are no examples I can find on how to use it. Can the [bandwidth-estimation-from-disk](https://github.com/pion/webrtc/tree/master/examples/bandwidth-estimation-from-disk) from pion be ported yet...

Just voicing support for this as well! Many new rendering techniques require texture atomics and support for them is becoming much more prevalent now. For instance, desktop and many newer...

> When will the open source code of Radeon Rays 4.0 become available - in a month or in half a year ? Apparently much longer than half a year......

I'm not sure forcing all proxying back to the main thread is the best idea... For instance, we have a thread/worker dedicated to webgpu and we ensure all webgpu calls...

Correct and yes we use OFFSCREENCANVAS_SUPPORT with one small emscripten change needed to make it work var context = canvas.getContext('webgpu'); to var context = canvas.offscreenCanvas.getContext('webgpu'); inside library_webgpu.js (wgpuInstanceCreateSurface)