[v1sea]

It's neat, but I have a feeling this will result in very large downloads and long load times. Like the Unity WebGL exports of the past.

The car example https://car.tiwsamples.com/ took 120 seconds to load, making 1820 network requests, and transferred 392MB of data / 487MB decompressed.

You can deliver a significantly better user experience by building for the web directly.

[astlouis44]

There are definitely pros and cons, just like there is for using web-first 3D frameworks and engines. In terms of Unreal, asset streaming is a must and helps significantly here. Also, these demos are going to continue to be optimized for file size/load time, so you can expect speedups over what we've currently made available.

This represents a way for Unreal developers to export their authored content to the web. It is an option, but is by no means the only way to do 3D in the browser. What web native frameworks lack is the rich functionality that comes with game engines such as Unity and Unreal.

[v1sea]

There has been a chicken and egg problem for gpu intensive media on the web. WebGL overhead limits complexity -> demanding applications remain native -> tooling for WebGL/WebGPU is limited or lags behind.

I bet these are some of the most complex WebGPU programs.

Congrats on the launch! Good luck on the optimization.

[seanisom]

Can you utilize streaming compilation of the Wasm modules? This significantly improved load times in Photoshop Web.