248
submitted 5 months ago by [email protected] to c/[email protected]
you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 1 points 5 months ago

You cannot break the speed of light with computational effort.

You're saying that you want to have a round trip from client to server and back happen in-between frames.

You cannot do that. Period. You will not ever have latencies that low.

Even if you frame lock it at 60fps that means you're calculating views, sending the data up the tube, checking it on the server, responding back with all the data about the new character that should appear and then rendering the new guy within 17ms.

That is physically impossible.

[-] [email protected] 1 points 5 months ago

That's why I already proposed tolerance for ~200ms with trajectory projections

[-] [email protected] 1 points 5 months ago

So you're going to take all the places a character could be in the next 200ms, do Ray casting on all of them and send that data to the server to check every 17ms?

While the server also does that for 15 other players at the same time.

Do you know what algorithmic complexity is? Big O notation? If so - that's a n³ * 15m³ problem space that you're expanding out across 200ms every 17ms, where n is player locations possible in x/y/z and m is the other players locations. Physics collisions are usually the biggest drain on a computer's cycles in game and in the worst case that's n² complexity.

You're talking insanely taxing here.

this post was submitted on 27 Apr 2024
248 points (98.1% liked)

Gaming

19765 readers
689 users here now

Sub for any gaming related content!

Rules:

founded 5 years ago
MODERATORS