Actually seemed to get quite far.
Project has custom code.
LogPlayLevel: Program.Main: ERROR: AutomationTool terminated with exception: AutomationTool.AutomationException: BUILD FAILED D:\Projects\MMDev\Matchoo\Binaries\HTML5\Matchoo-HTML5-Debug.js.symbols was in manifest but was not produced.
Contents of that directory include five files (not a .symbols file) - .asm.js, .bc, .js, .js.mem and .target
Log attached.
I WAS able to build and launch the shipping build. Be nice to have a debug build especially as the shipping build doesn’t get anywhere (not unexpected for a first new platform launch…).
for HTML5 - build the developer version - this produces debug symbols.
also, please try with a newer version of UE4 (note: 4.19 is just around the corner). a lot of build steps were cleaned up for HTML5.
debug builds for HTML5 will not run in the browsers - the resulting “game (javascript) code” it will be too big to fit into the browser’s memory.
I may move to 4.19 when available. Solo developer though and have a few minor but needed (for me) engine fixes that make jumping between engines a bit annoying.
Good to know that work is going on the HTML5 plugin, I was pretty surprised to see my loading screen come up as easily as it did! Will the initial download always be there or will there be some method of caching?
for now, yes - the initial download will always be there –> until we get WASM with multi-threading available – which will be giving us the ability to have a cacheable filesystem and chunk (pak) file support.
we are waiting with great anticipation for WASM threading spec to be finalized (as well as the browsers that support it).