this post was submitted on 27 Apr 2024
304 points (97.5% liked)
Gaming
20057 readers
43 users here now
Sub for any gaming related content!
Rules:
- 1: No spam or advertising. This basically means no linking to your own content on blogs, YouTube, Twitch, etc.
- 2: No bigotry or gatekeeping. This should be obvious, but neither of those things will be tolerated. This goes for linked content too; if the site has some heavy "anti-woke" energy, you probably shouldn't be posting it here.
- 3: No untagged game spoilers. If the game was recently released or not released at all yet, use the Spoiler tag (the little ⚠️ button) in the body text, and avoid typing spoilers in the title. It should also be avoided to openly talk about major story spoilers, even in old games.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You do something called raycasting to determine visibility beforehand, and don't render anything not visible.
lol raycasting isn’t optimized for server side deployment, it would increase the poly count of the mesh tenfold, which would in turn increase average ping and fps. Couple that with the client side rendering problem and I don’t know anything about development just kidding
Your suggesting the server maintain a real time render for every single player and somehow manage to get the data back to them in less than 17ms so that they don't have empty frames that suddenly become people?
Because that's a ludicrous requirement in terms of latency (ping is totally reasonable at any value under 100ms) and server capacity.
Because your solution sounds like it would cause popping constantly and be a major burden on the server, which is already the largest overhead on a released game.