this post was submitted on 27 Apr 2024
314 points (97.6% liked)

Gaming

19801 readers
188 users here now

Sub for any gaming related content!

Rules:

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] huginn@feddit.it 12 points 5 months ago (40 children)

It's easy to just handwaive and say "Server side will fix it" but here's a major issue:

You have to render people in before they appear. How do you do that without the client knowing where people are?

[–] ProgrammingSocks@pawb.social 10 points 5 months ago* (last edited 5 months ago) (11 children)

If the trajectory and speed says either the client or another player will cross a wall soon where the player sees them THEN it could send the data to the client. You need some tolerance for ping up to maybe 200ms but that's it. Wallhacks could give you at most a flash of a couple specific people.

[–] huginn@feddit.it 3 points 5 months ago* (last edited 5 months ago) (10 children)

You need to account for every gap in the wall, nook and cranny and peephole for these sightlines. You'd have to bake so much detail into every calculation server side that it would effectively be rendering the entire map to host a single game.

[–] ColonelPanic@lemm.ee 5 points 5 months ago

There are many ways of doing this. I know the source engine uses visboxes, which are calculated once at map compile time. It takes a while to compile, but it means that clients can use the pre-compiled data to calculate parts of the map that are visible and the server can use them to determine what the player can see at a given time. I'm not sure whether it does that or not, but it would make sense to use that data.

load more comments (9 replies)
load more comments (9 replies)
load more comments (37 replies)