--
You received this message because you are subscribed to the Google Groups "Dawn Graphics" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dawn-graphic...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dawn-graphics/ccb24156-7ade-471c-9fe0-cb9efa103aff%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Dawn Graphics" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dawn-graphic...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dawn-graphics/ffb83083-8e7d-4699-bab2-10d9f1d0dd48%40googlegroups.com.
Hey everyone (und Moin Dominic),The WebGPU Node project is indeed just bindings to Dawn, things only got messy at the conversions from Javascript Objects to native Dawn structs (see this file).
I currently get sponsored to work on a Ray-Tracing extension, so that's my top priority at the moment. Though getting the CTS running in the node bindings would be a big favor, if you need any help on that, just let me know.Also next week, I'm targeted anyway at trying to build for Linux and Mac - I don't see any problems yet about a Linux build.
One general problem I currently see though is that I'm currently using a Dawn fork extended with the Ray-Tracing stuff, I'm not sure on how we should proceed with this kind of.. mixture - ?
P.S - I've added a Todo section to the node bindings readme
On Friday, 10 January 2020 04:47:59 UTC+1, Dominic Cerisano wrote:Noticed an update to NPM's webgpu package was posted a few hours ago and the downloads are really spiking.Pardon my enthusiasm, this is a lot of progress to absorb so suddenly, on top of the recent appearance of webgpu.io in Chrome Canary for Windows.
Is this a good place to start a discussion to track compatibility of webgpu.io for browsers with webgpu for NodeJS?
Where would issues between the two be tracked?