WebAssembly is coming for games next.
Near native performance, players can join with just a link, and no 30% cut that developers have to deal with.
Near native performance, players can join with just a link, and no 30% cut that developers have to deal with.
On top of that, building things that work consistently across browsers and across time is an extremely cursed problem.
Insomniac Games, makers of the new Spider-Man games, spent several years trying to port all of their development tools and workflows to be web-based and work in Chrome. And then, when they got there, it turned out to be terrible. Google would update the browser and key tools would break and nobody would know why. The tools folks had to work in Javascript, while the majority of the engine was still in C++.
The call was eventually made to migrate the tools back to native exes, which was another multi-year process, but nobody missed the Chrome tools. Clicking a bookmark in a browser turns out to be about as difficult as clicking a desktop icon, and the stability is significantly improved.
Maybe we should stop caring for AAA games then? What happened to gameplay instead of "this new game has 10% more detailed graphic assets"?
As if I said/meant that gameplay-based games didn't exist (as opposed that the industry and market has a heavy AAA/get newest GPU/ emphasis).
Not to mention that AAA light on gameplay and full on assets also hire gameplay programmers. It's not about gameplay programmers being busy, or gameplay-heavy games existing.
It's about having many more gamers stop chasing graphics to the detriment of gameplay - or in fact, stop chasing graphics, period.
And viewers in general would gain much more subtle understanding of the world, appreciation of art, mature emotions and storytelling, exposure to global cultures (not just heroes-in-spandex-Hollywood-commercial monoculture) and lots of other things besides, if they didn't watch Marvel movies and watch arthouse cinema instead.
Or, as we call it here, just "cinema" (it doesn't need a qualifier, we call the rest "Hollywood crap" instead).
"The technology can never compete", but it gets better every year.
The new Microsoft Flight Simulator is amazing, and they took that same rendering and can stream it to the browser (though not as a game as far as I understand) with Project Anywhere https://developer.nvidia.com/blog/streaming-simulation-and-t...
I'm not saying that WebGL is ready to take on AAA games today, but calling it "pure fantasy" is naive. People will never use a browser on their phones, the internet will never compete with television, electric cars can't take on gasoline, the list goes on and on.
Although I do see a future of Gaming on browser. Not everything has to be AAA 3D Games. I want retro 2D Games. Games that were even possible with good old Flash.
Also, the original blog isn't only about WASM, that's just one of the technologies making this sort of thing possible.
Canva was built pre-WASM, so photoshop in the borwser, may be better with WASM, but I'd suggest it isn't a requirement.
The bad news is that it's not the tech that is holding back web based game dev. It's the users. Market research and testing has shown that users dislike "just playing" a game in the browser. This is particularly true in the AAA segment that webassembly and its perf gains would best serve.
Players who play the high profile games that web assembly would allow you to make games for (think Fortnite, CS:GO, etc) all want to play games from a trusted download from a trusted store, not some random website. Please note, random is used very loosely here to mean "any store/website that isn't Apple Store, Play Store, Xbox Live, PSN, or Steam".
I foresee that we'll need some major player with a big game like Fortnite, Roblox or Mojang to spearhead using web deployed games before we'll see anything happen in this space. The existing "install to disk and play" is working just fine and game devs don't really see any reason to change that.
The other major thing is that most "slightly" big games (even smaller mobile ones) have assets in the minimum size of 4-10 GB of data. Even if you can render the game in browser, you have to download those assets. Yes, of course you can "load only what you need" but for many many games (source: my wife is a game designer and I'm a game programmer/web dev) that still entails at least 1 GB of data that would need to be loaded and is difficult to cache client side in the browser.
> Players who play the high profile games that web assembly would allow you to make games for (think Fortnite, CS:GO, etc) all want to play games from a trusted download from a trusted store, not some random website.
No doubt this is partially thanks to the numerous game-like ads that link to exceptionally cheaply made web games. I remember a time in the late 00s and early 10s when browser based games were starting to flower, but then the spammy stuff took over and their popularity dropped like a rock.
I would hazard a guess that the overhead of navigating to a specific site and the clunkiness inherent to browsers being a 1024-in-one multitool doesn’t help matters. It’s nicer to just fire up Steam and have all your games neatly listed, all free of extraneous browser chrome and whatnot.
Mostly prototyping and “spike” research into the key architecture bits to make sure everything will meet my needs.
Discord link: https://discord.gg/zUSZ3T8
People just don't want to invest/search for random new games on random websites.
For games people want to play, and already have heard about, it wouldn't matter if they are on a website or a "trusted store". If Fortnite was made available to play only from a website starting tomorrow nobody would have a problem using it from https://www.fortnite.com as opposed to Epic's game platform.
And for games sold by big companies, it also wouldn't matter. It's about trust (which Valve or Epic has), not about web vs a launcher/store.
If devs can get that trust, then getting users to play the game on the web is not a problem.
>but for many many games (source: my wife is a game designer and I'm a game programmer/web dev) that still entails at least 1 GB of data that would need to be loaded and is difficult to cache client side in the browser.
You also need to download/cache that 1GB or 10GB if you use Valve or whatever.
As for caching it client side in the browser, you can do it as well, either as browser cache (browser vendors will just add the technologies for that), or as locally downloaded assets with direct access granted from the browser (the article already talks about using a new API for mmapping-style access to files outside the browser).
That said, I think the niche of casual remote party games would probably work very well here. During the height of the pandemic my friends and I started doing a lot of "remote game nights" with various different kinds of games. However since most of them rarely played games, owned macs and weren't very technically inclined, the games that had the least friction were generally the browser based ones.
Since party games by nature tend to be great at organic advertising and benefit the most from quick easy installs, I think there is a big opportunity here that not many have taken notice to yet.
We use Steam, Xbox Live, PSN, etc not because we wouldn't prefer to use our own store, but because no one cares about anything else.
The reality of you selling your game at a profit without the help of one of these app storefronts is improbable. Keep in mind that even if you somehow become successful in this regard, these storefronts have a vested interested in making sure you and your technologies fail.
Edit: apologies if I seem dire, I'm actually on your side and WISH that the world was a free market without all these gatekeepers. Myself, my partner, and many of my close friends constantly battle with these "gate keepers" as game devs/designers and I wish they would go away, but the market (users) love (to use) them even when they hate them.
Sure but that situation doesn't change by simply distributing a webassembly package through a website. Or rather, that situation is no different than if you distribute a desktop binary through your website. In both cases you are eschewing the storefront.
The real challenge with webassembly as it applies to games (at least large ones) is the asset size. AA - AAA games are 20-100 GB and that can't just live in browser cache.
Also, to be honest building a complex game and shipping it to the web is kinda crap shoot for other reasons. Games are power hungry, and don't want to be limited by browsers. Also, a browser is a massive application that sits around consuming resources that a AAA native game could use.
But of course, I imagine games will be developed differently to take advantage of the web (smaller games, streaming in levels / textures as needed, etc).
I mean, no. I definitely wouldn't want to endure the waiting time I have every time I play some MMO if I'm playing a single player game.
Combined with compression, you can get players into desktop-quality games in WASM in seconds on most computers.