Hacker News Reader

Comment by pjmlp | Hacker News Reader

Yet I am still waiting to see a game with the same capabilities of Infinity Blade, that Apple used in 2011, as an example of a game showing of the newly acquired OpenGL ES 3.0 capabilities of iDevices.

Or the Unreal Engine 3.0 citadel demo, also in 2011, for Flash/CrossBridge.

It seems the only thing usable is running ShaderToy demos, and 3D views on ecommerce sites.

View on HN

That expectation is off by nearly a decade. WASM games in terms of performance are closer to 2000 than 2010. Here's an open source indie game from 2003 that I ported to WASM [1]. It struggles to hit 60 FPS on devices that were released a good 15 years after the game itself. Browsers sometimes struggle to animate simple lines at 60 FPS still to this day, because they're just hugely massive platforms with thousands of moving parts with no room for big, complex apps on top of them.

[1] https://neverball.github.io/

If we hadn't lost a decade with what Flash and PNACL already offered us in 2011...

No wonder studios rather bet on streaming than a tech that will never deliver.

Let's be clear what Flash was though. It was a native binary that would paint to a region owned by the browser. So yes, it was performant because basically the only thing it was doing differently than any other native application was how it was hosted by the browser.

That's also why it was such a security nightmare. It was a complete escape from the browser sandbox.

It was a great development experience, destroyed by pitch forks and lanterns by the folks that a decade later have failed to deliver a sound alternative.

Hence why the gaming industry is focusing on streaming instead.

Flash was destroyed by Apple, which had no interest in improving the web either. The iOS platform turned out to be a pretty good replacement for Flash though.

Apparently people keep forgetting that after that memo, Adobe produced an AOT compiler for Flash, targeting iOS.

Sure, but what's the point if it's not supported by Safari. Adobe Air was at best a porting aid to get your old Flash code wrapped in an iOS app, but the writing was on the wall and nobody in their right mind would start new Flash projects.

And now a decade later, despite PlayCanvas and Babylonjs, there is hardly anything that compares.

Mobile, handhelds and cloud streaming, is where the indie party is going on.

I bet WebGPU is going to be equally the same, ShaderToy and 3D commerce visualisation tools will be updated for it, and that is it.

Specially given that it made the same mistake of WebGL, lagging 10 years behind native APIs.

PNaCl was a joke though, it suffered from much longer client-side compilation times than both asm.js and WASM ever had, and performance was at most on par with asm.js.

(NaCl was better in those areas, but required to stamp out one binary for each target CPU architecture)

A joke that was able to deliver more than WASM/WebGL have yet to deliver.

I need to double check what you're saying, how do you show the FPS in your WASM port?

Devtools or F9 while in game. Type a famous magic word in the title screen to access all levels. Not sure how to do this on a phone which is what I was referring to - but framedrops are pretty obvious.

Thanks, I suspect it might be gl4es but I need to find my old phone to investigate. Magic word is "xyzzy" for anyone else looking.

I've done a quick test and it runs very smoothly on my original OnePlus One from 2014 (so 11 years after the game). This is on latest Chrome, Android 11 (LineageOS 18.1).

I still find it amazing that this game never made with this in mind, the web tech at the time on the OnePlus One was nowhere near able to run this in browser and it works perfectly today!

To be fair my reference browser is Firefox, WebGL is a fair bit slower there.

What blows my mind with this technology is little things: porting the game to the browser gave me a half-working mobile port basically for free (had to implement touch input handling in Neverball). On top of that, thanks to SDL2 and the game controller web API, I can attach a game controller to my phone and play the game in the browser on my phone with a game controller. It just seems unreal that this combination of technology just works.

A browser also has the baked in expectation of you interacting with hypertext.

A video game of this caliber you are discussing is typically entitled to:

- have a dowload and installation process that might span over say 20min or more

- load slowly, because it needs to push a ton of assets through

- demand a ton of resources such CPU, GPU, threads, memory etc. to achieve amazing graphics and simulation

- being the primary foreground process or possibly the only one

None of these things apply to the typical web. Quite the contrary: most web devs would get fired or ridiculed if they demanded these resources.

So I assume that browsers optimize for the typical usage, which is hypertext.

Problems that can be sorted out, if there was any industry interest.

As it stands, everyone is going with cloud streaming instead.

Still uses a browser.

Glancing at the project, one area where things could go terribly wrong is the translation layer from GL 1.x to WebGL. For instance 'tricks' that are common on native GL implementations like buffer orphaning are actually harmful on WebGL and may cause lock stalls which would cause exactly the issues you describe (e.g. struggling to hit a consistent frame rate despite extremely low CPU and GPU load).

Even though WebGL and WebGL2 are implementations of the GLES2 and GLES3 APIs you usually can't just take a non-trivial GLES2/3 code base and expect it to work without hickups on WebGL, what's going on under the hood is just too different.

A couple of years back I also wrote a pure WebGL renderer for Neverball levels [1]. No physics, no translation to WebGL, just the 3D renderer part in direct WebGL. It also has a surprisingly low performance ceiling. I'd say I managed even worse than what the gl4es translation layer does for Neverball. By far the biggest performance boosts were instanced arrays and vertex array objects - basically just reducing the number of calls into WebGL. Seems to me that WebGL has a lot of overhead with or without a translation layer.

[1] https://github.com/parasti/parabola

I did some GL benchmarking for simple draw calls (on desktop) a couple of years ago, and while it's true that WebGL came out lowest, the difference between native drivers were much bigger. I basically checked how many trivial draw calls (16 bytes uniform update + draw call) were needed on Windows before the frame rate drops below 60 fps, and for WebGL in Chrome this was around 5k, Intel native was around 13k, and NVIDIA topped out at arond 150k (not all that surprising, since NVIDIA has traditionally the best GL drivers).

It is definitely true though that you need to employ old-school batching tricks to get any sort of performance out of WebGL, but that's also not surprising, because WebGL is only a GL by name, internally it works entirely different (for instance on Windows, WebGL implementations are backed by D3D).

There's definitely something strange going on here. I'm getting about 3x as much CPU load on the WASM version as compared to native. Still low enough for a solid 144fps on my machine, but there shouldn't be this much overhead.

The number of calls needs to be lower for a WebGL application. You have to use as much instancing as possible. The security layer makes the calls the slowest part of the pipeline. That's why you see amazing things in shadertoy. When the whole shebang is in the shader it runs smooth.

Apple has been slowing down WebGL I think. See eg people complaining in https://developer.apple.com/forums/thread/696821 and https://discourse.threejs.org/t/horrible-3d-three-js-perform...

80% of the browser mobile market belongs to Google, plenty of customers, even better when looking at the desktop market.

Usually a good excuse why the tech doesn't get uptake.

The unreal citadel demo was running in a browser without flash in 2014: https://blog.mozilla.org/en/mozilla/mozilla-and-epic-preview...

3 years to catch up with 2011 tech, and a decade later nothing better to show.

My hypothesis is that monetization on the web is harder so there are not as many resources spent on games in browsers. If anyone is willing to spend a lot of time on the game they are probably willing to install it, people arent conditioned to pay up front for websites, the UX around microtransactions isn't at all smooth.

These are mostly business issues. If the business problems would be solved, the games would be built, despite any technical limitations of the web platform (which are not much different than limitations on low-end Android mobile devices).

Nobody has figured out so far how to make money with high quality games on the "open web" to get the same return on investment like simple ad-driven 2D games running on closed platforms like Facebook which can technically be cobbled together by 3 dudes in their mom's basemement (exaggerating a bit here of course).

E.g. no matter how you approach it, the Citadel demo wouldn't have led to a web game that would make the same profit relative to the development cost like a simple ad-driven Tetris style game.

No they aren't, at least low end Android devices support GL ES 3.2 and have proper debugging tools.

After a decade Web 3D keeps having spectorJS as the only alternative.

Naturally there are also some masochists that enjoy debugging the browser 3D stack on RenderDoc, while trying to figure out what belongs to their application.

If you use WASM+WebGL, you'd typically debug a native build outside the browser.

According to here GLES3.2 support on Android is currently sitting at 80%, while with GLES3.0 you would reach about 95%, and with GLES2 100%.

https://developer.android.com/about/dashboards#OpenGL

If I would try to ship a native app on Android I would still at least try to only use GLES3.0 features to get that extra 15%.

You enthusiastic charactization of Android debugging tools isn't exactly how I would describe the situation ;)

A kludge to work around lack of tooling for the past decade, and when doing that, no need to WASM anyway.

Even if we consider GL ES 3.0, native comes out winning, due to missing features on WebGL 2.0.

Not only has Android the GPU debugger from Google, that beats anything available for Web, each mobile GPU vendor has their own set of graphical debuggers.

Reply on news.ycombinator.com