Hi - thanks for your response. From what I could see, is just a HTML packaged build, that has to be downloaded by a browser entirely before bring played?
What I am trying to achieve is “streaming the game content”. You could think of it as a client server architecture.
Essentially:
-
The browser downloads the initial part of a game/app (e.g. the HTML packaged Engine, and a minimal starting scene of say, a few meshes) from the sever.
-
As the game progresses, other meshes (.uassets?) are streamed to the browser, by the server, and are then rendered.
The reason for asking this is: if the game is very large (say 200 - 300 MB), it will be inconvenient to wait for the entire game to be first downloaded (especially over mobile wireless networks) and the played out.
In summary - can you package the HTML game/app an a client-server architecture, where .uassets are streamed from the server to the client? The client runs on browsers, while the server on a dedicated PC.
Thanks again!