I’d like to stream specific objects (meshes & their corresponding textures) of a HTML packaged game/application. e.g. - say, a simple game consists of 10 buildings and 4 roads, and a user walking down a road. Can one stream, say 3 buildings and one road initially - in the game only these objects are initially visible to the user. As the user walks further, other buildings & roads start becoming visible and those are then streamed.
For a game/application of several 100 MBs in size, this will be an essential requirement, as users may not want to download the entire HTML5 package. Especially, when browsing from phones/tablets over wireless networks.
Hi Adam - thanks for your response. From what I could see, Tappy Chicken 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.
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.