Client performance characteristics? Speaking very broadly... I can't imagine a game that'd need that much data unless it involved a lot of streaming assets (audio, video, etc) or really, really naive netcode.
Maybe instead of leaving drive by comments like this you can explain this to the overwhelming majority of people in this thread who think it's bananas.
> Now if you're the author, can you tell me what the space game does?
A larger more detailed world with a higher player count, networked using quake style netcode techniques ala. Counterstrike, Titanfall, Apex Legends with snapshots and delta compression, client side prediction and lag compensation.
In short, FPS netcode scaled up to 1000 players, but applied to a space game, not an FPS, because the world doesn't need another FPS right now...
This thread absolutely has not been full of reasonable and non-assuming questions.
1. "I can't imagine a game that'd need that much data unless it involved a lot of streaming assets (audio, video, etc) or really, really naive netcode"
2. "If you're sending that much data constantly, you're either syncing too much stuff too often, or you're not using compression when you should be"
3. "overwhelming majority of people in this thread who think it's bananas."
Sorry folks, but if you want to have a positive discussion with me about game netcode this is not the way to do it.
The article already started off saying the bandwidth itself was a problem due to egress costs, but that's not the only issue. Thunderfork already answered what else is wrong with it. Now if you're the author, can you tell me what the space game does?
I can :)