Comment by Rohansi
6 hours ago
> but if the user has to sit through a 20GB download anyway, then what's the point?
They don't have to unless the game makes them. Assets can be streamed in. This Half Life 2 port streams in each chapter so you are playing without having the entire game downloaded. World of Warcraft is over 100GB but you can start playing with only a fraction complete and it will continue downloading as you play
Half Life 2 is only ~4-6gb and was designed to run on video cards with 128-512mb of RAM, and it didn't even do texture streaming so you just need to have those assets at load time. Sure you can stream those low res textures at an acceptable rate. That's wholly different from streaming the textures for a modern game, which are at least an order of magnitude larger, and are expecting to stream in from NVME/SSD storage.
This website is also a proof of concept, it doesn't care if people are actually able to play it consistently. It can afford to just say "anyone with less than 100mbps internet gets a shitty experience, lol don't care" and nobody will complain, because it's a free tech demo. Not an actual product trying to sell copies and make money. And certainly not anything remotely modern, we are talking about an over 20 year old game here. Technology did, in fact, get a little bit faster and more capable over those last 20 years, you know
Performance of the game is much more important than download time
Its really common to sacrifice disk space for runtime perf
For gamers 100GB is not a big deal, CoD is like 200GB and its extremely popular
I disagree with your assertion that games running in a browser are not performant enough. WebAssembly being ~45% slower than native sounds scary, sure, but that's basically what you can expect from using any non-native language anyway. So if Unity is performant enough where all C# code has similar overhead then it should all be fine.
Plus not all games are AAA.
Unity doesn't use C# for everything. Notably the game engine itself is not C# but C++. C# is essentially just the scripting language.
You're also ignoring the overhead of WASM -> WebGPU -> native graphics API, not to mention how much harder it is to develop and debug that platform than it is a native one.
1 reply →