js exception on ipad firefox
Localization: No localization: Core.Progress.Loading (int)
Unreal Tournament 99 running on WASM (2017)
81–90 of 117 posts
Re: Unreal Tournament 99 running on WASM (2017)
#82js exception on ipad firefox Localization: No localization: Core.Progress.Loading (int)
The github page states that this project doesn't work with mobile safari. Therefore all browsers based on the safari engine on ios including firefox will not work.
Re: Unreal Tournament 99 running on WASM (2017)
#83So when are we going to see modern Unity and Unreal games running on the web? Games seems like one of the last areas that is a holdout on desktop. We've seen terminals/IDE, productivity software, and even design software like Figma run in the browser, but not 3D games which is a multi-hundred billion dollar industry in it's own right. Correct me if I'm wrong, but it seems like a massive opportunity for both game engi…
This has already been possible for years - Unity and Unreal have had ports for a long time. The problem is that the web is a horrible platform to release AAA or AA games on. No way to pre-install, arbitrarily small local cache for your assets, long load times (due to slow I/O and code compiling every time), graphics API feature set from a decade ago, limited support for multithreading, SIMD not really widely usable y…
Exactly my point of view, 3D Web APIs are only good for 3D models in e-commerce, shadertoy like playgrounds, retrogaming and casual games with PS3 like capabilities.
And even the PS3 at least had a proper graphics debugger.
Re: Unreal Tournament 99 running on WASM (2017)
#84Re: Unreal Tournament 99 running on WASM (2017)
#85Cool cool cool ... though these kinds of browser proof-of-concepts have been around for a decade (more than a decade if you include Flash+alchemy running Quake). Is the browser coming back as a gaming platform yet?
Not really because the development experience sucks, no wonder the industry is turning into streaming instead.
Re: Unreal Tournament 99 running on WASM (2017)
#86Cool cool cool ... though these kinds of browser proof-of-concepts have been around for a decade (more than a decade if you include Flash+alchemy running Quake). Is the browser coming back as a gaming platform yet?
With WebAssembly and WebGPU, absolutely we are going to see resurgence in games, this time with near native performance and modern fidelity visuals that are closer to what can be done on PC, mobile, and consoles. Web will be huge for increasing accessibility, especially for casuals who have never downloaded Steam before. Imagine the Cambrian explosion that will take places when playing becomes as simple as clicking a…
Keep dreaming, WebGPU is a MVP of where next generation APIs were in their 1.0 version, almost 7 years ago.
It has taken a decade, it will arrive without proper tooling, and require everyone to rewrite their shaders as well.
Re: Unreal Tournament 99 running on WASM (2017)
#87Earlier quoted context omitted.
> Note that it's just the intro So 100 to 200 MB of PRECACHING /s
Technically a DLC
The joke was that the very first screen in the game is blue text "PRECACHING..." on the black screen which stayed for minutes on 99' hardware, so it could also be an intro of sorts.
Re: Unreal Tournament 99 running on WASM (2017)
#88Earlier quoted context omitted.
I don't think it's a cultural issue. The difference is you only have to download a game once from the store compared to downloading 10GB+ every time you load the webpage.
Quite a lot of cache storage can be used and can be expanded on as well if there was a serious demand for it. Browser games don't technically have to redownload the entire game every load. The reason I claimed it as "cultural" is because of how we view browsers and interactive media within them. We are totally fine with opening a games store app, clicking download, and waiting and playing. The same is technically pos…
No it can't, for security reasons.
Browser games have no idea how long their data is around and how big the cache actually is.
Re: Unreal Tournament 99 running on WASM (2017)
#89Earlier quoted context omitted.
No, Unreal can't export to the web using newer versions of engine actually. And UE5 does not have support for it out of the box at all.
The header on the previously linked docs page brings us to the GitHub repo where Epic OpenSourced it as a plugin. The missing support can be confirmed in the issues. Seems like web support was quietly removed after all. https://github.com/UnrealEngineHTML5/Documentation/issues/10...
It was, because no one was using it and it isn't as if 3D Web is capable of stuff like Nanite.