153 ms·
Can't https://bevyengine.org/ https://bevyengine.org/ do this? AFAIK https://wgpu.rs/ https://wgpu.rs/ makes this possible with Rust. --- But this is very di
by jasonjmcghee 3y ago
Can't https://bevyengine.org/ https://bevyengine.org/ do this?
AFAIK https://wgpu.rs/ https://wgpu.rs/ makes this possible with Rust.
---
But this is very different than what was demonstrated in the vimeo video.
- Animats 3y agoNot all that different. See these WGPU demos.[1] As someone who's been using the Rend3/WGPU/Vulkan stack for over three years, I'd like to see some of these renderer projects ship something close to a finished product. We have too many half-finished back ends. I encourage people who want to write engines to get behind one of the existing projects and push. [1] https://wgpu.rs/examples/ https://wgpu.rs/examples/
- jasonjmcghee 3y agoMy understanding of the project here (Renderlet) was it allowed direct embedding in other non-wasm projects, which I didn't fully wrap my head around, allowing for injecting this engine inside of others? Or something to that effect? Which is quite different than a renderer that targets wasm/webgpu. I think super highly of, and have used wgpu a fair amount. I just interpreted Renderlet to have different goals.
- seanisom 3y agoThat's exactly it. With renderlet, the goal is to compile the "frontend" code that's driving the rendering pipeline to WebAssembly, and provide a runtime that embeds that in any app, with the host app providing any configuration necessary to connect renderlet modules and use its canvas. On the "backend", we will switch fully to wgpu as we retool around wasi-webgpu. I explicitly don't want to rebuild a project like wgpu, and everybody should commit upstream to that - we will likely have stuff to upstream as well.