I’m not saying more isn’t doable, just laying out the difficulties of the challenge and why I think 100 is a bit of a magic number. An O(n^2) problem has to do 144x the work going from 100 players to 1200. It’s doable, but not trivial.
-
But the problem rapidly becomes the Kevin Bacon game: where do you actually cut long interaction chains?
Interesting! I've always thought k-clustering was a good solution too, but never had an opportunity to try. Although I tended to think geographically, because for movement updates and combat, that's mostly what you want.
-
-
The clusters effectively create something of a voronoi pattern too, and it seemed like a good opportunity for LODing updates. In a neighboring cluster? Get every 2nd update. Neighbor's neighbor? Every 4th update. And so on.
-
Although, I do think that it's better for all this to be on one process, rather than a process per k-cluster, just for the headache of replicating across server boundaries. Instead, I'd be interested in seeing a process own a subsystem.
- Näytä vastaukset
Uusi keskustelu -
-
-
Client/server latency hurts so bad there. If I climb a mountain and go into snipe mode I really don’t want a cylindrical AOI anymore. But I can’t dumb my object manager in favor of a 5-degree arc extending 1000 yds because I can’t pay two or three round trips when I stop.
- Keskustelun loppu
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.