4 ms·

We've been doing work in Godot Engine trying to get wasm working. How did you overcome the shared array buffer accessibility problem on safari vs access to ad

by iFire 3y ago

We've been doing work in Godot Engine trying to get wasm working. How did you overcome the shared array buffer accessibility problem on safari vs access to ad networks which is important for online games? I called it single threads vs regular builds. Hope to help make sure there's a diverse set of rendering kernels for everyone. Edited: Link to our work at making portable 3d graphics on the web with an editor. https://editor.godotengine.org/releases/latest/ https://editor.godotengine.org/releases/latest/

iFire 3y ago
We also collaborate with https://github.com/thorvg/thorvg https://github.com/thorvg/thorvg. We were impressed by your work, https://github.com/rive-app https://github.com/rive-app and https://graphite.rs/ https://graphite.rs/
- Keavon 3y ago
  Thanks! If perhaps we spoke at GDC (taking a guess given the context), it was nice meeting you! (Keavon from Graphite here.)
  - seanisom 3y ago
    Hey Keavon, I'm also a big fan, been lurking in your Discord for years! The design of the render tree of Wasm nodes certainly took inspiration from Graphite's node system.
seanisom 3y ago
Big fan of Godot! I think it has done wonders to make graphics more accessible. From an Adobe perspective - it doesn't. If you go to photoshop.adobe.com in Safari, you will see the answer. Things can work in a single-threaded build, but that is not production code. I can't speak for the Safari team, but I do see this getting traction soon with the current priorities for Wasm. Seems like now the most common answer is just to use Chrome.
spxneo 3y ago
whew game engine running on WASM + WebGPU would finally be what it takes to power browser based AAA titles. We shouldn't have to download executables via garden walled ecosystems that take a huge chunk of devs revenues
- seanisom 3y ago
  This right here. The web is the OS of the future - the standards are getting there, the tools are just starting to catch up.
  - PaulDavisThe1st 3y ago
    What platform(s) do you think browsers will run on?
    - seanisom 3y ago
      More of a comment on how apps are being built in the future - web-first is becoming the default. I already see web even taking over in things like embedded UIs where native toolkits like QT historically were popular.
- 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 ago
    Not 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/

by iFire 3y ago

iFire 3y ago

We also collaborate with https://github.com/thorvg/thorvg https://github.com/thorvg/thorvg. We were impressed by your work, https://github.com/rive-app https://github.com/rive-app and https://graphite.rs/ https://graphite.rs/

Keavon 3y ago
Thanks! If perhaps we spoke at GDC (taking a guess given the context), it was nice meeting you! (Keavon from Graphite here.)
- seanisom 3y ago
  Hey Keavon, I'm also a big fan, been lurking in your Discord for years! The design of the render tree of Wasm nodes certainly took inspiration from Graphite's node system.

seanisom 3y ago

Big fan of Godot! I think it has done wonders to make graphics more accessible. From an Adobe perspective - it doesn't. If you go to photoshop.adobe.com in Safari, you will see the answer. Things can work in a single-threaded build, but that is not production code. I can't speak for the Safari team, but I do see this getting traction soon with the current priorities for Wasm. Seems like now the most common answer is just to use Chrome.

spxneo 3y ago

whew game engine running on WASM + WebGPU would finally be what it takes to power browser based AAA titles. We shouldn't have to download executables via garden walled ecosystems that take a huge chunk of devs revenues

seanisom 3y ago
This right here. The web is the OS of the future - the standards are getting there, the tools are just starting to catch up.
- PaulDavisThe1st 3y ago
  What platform(s) do you think browsers will run on?
  - seanisom 3y ago
    More of a comment on how apps are being built in the future - web-first is becoming the default. I already see web even taking over in things like embedded UIs where native toolkits like QT historically were popular.
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 ago
  Not 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/