Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Orpheon]

And everyone else calls it prediction because his term is ambiguous, questionable, and estranged.

Also, if you want to go by definition, what I'm doing is estimating the value (=state) of a function I don't know all parameters of (the other players input), so I approximate it with a (simpler) function outside the sampled values on the base of those sampled values.

That is pretty much the definition of extrapolation.

[nightcracker]

And everyone else calls it prediction because his term is ambiguous, questionable, and estranged.

No it's not. What you do is based on the previous data guess (or better, extrapolate) the next position. Extrapolation is exactly what we're doing.

[Orpheon]

And everyone else calls it prediction because his term is ambiguous, questionable, and estranged.

No it's not. What you do is based on the previous data guess (or better, extrapolate) the next position. Extrapolation is exactly what we're doing.

Also NC, do the polygon collision dangit.

[NAGN]

i have a question, why do you need an image library while you have pygame?

I don't see how pygame is relevent to the imaging library

the imaging library is for the building of the mask extension, and otherwise it might as well be part of the standard library since its so universal. but it isn't.

[NAGN]

also NC, I found the proper article

http://trac.bookofhook.com/bookofhook/trac.cgi/wiki/Quake3Networking

seems it's been moved, but he updated a few things

[Phantom Brave]

Orpheon, if you're fast-forwarding other people, you're doing something seriously, seriously wrong.

[Intel Guard]

lemme explain the dynamics; the op of this thread and moderator is having a discussion with someone and you interrupt because you seen to believe a forum thread directly affects development. We have enough regular moderators, we dont need any in the back seat.

but its tiscooler

[Orpheon]

Orpheon, if you're fast-forwarding other people, you're doing something seriously, seriously wrong.

Not doing so but fast-forwarding yourself creates an inconsistent state, which is probably the worst thing that can possibly happen.
Not fast-forwarding yourself basically means no extrapolation, which is also sort of dumb.

One doesn't see the jumps if all goes well because the buffering takes over, but you can't avoid warping at some point.

[Phantom Brave]

You're not supposed to fast forward /anything/. That's unavoidably buggy and flawed. If you have something moving in a  curve it'll extrapolate a bunch of tangents, if someone jumps or fires at you at point blank you can't predict that, then once you get the shot or jump they're suddenly in the future, etc. You're supposed to /rewind the client state/ to compare it to the newest state from the /server/.

[trog]

i dont know networking but please dont do the tf2 delay on firing projectiles thing

[Phantom Brave]

cl_interp 0.033

[Phantom Brave]

I figured out how to lag compensate projectiles anyway so if they do interpolation it's possible to make it not ruin rockets etc

[trog]

yes but then you have to add the option to change all the net settings

edit: ok cool

[Orpheon]

You're not supposed to fast forward /anything/. That's unavoidably buggy and flawed. If you have something moving in a  curve it'll extrapolate a bunch of tangents, if someone jumps or fires at you at point blank you can't predict that, then once you get the shot or jump they're suddenly in the future, etc. You're supposed to /rewind the client state/ to compare it to the newest state from the /server/.

The client state is (in normal cases) at the same time as the packet state, and far behind the server state.
Extrapolating a curve makes a curve, not tangents, I don't know where you get that from. Other people's inputs are not predictable, true, that's the problem.

I figured out how to lag compensate projectiles anyway so if they do interpolation it's possible to make it not ruin rockets etc

How?

[Phantom Brave]

Every single time you step a projectile, rewind player position by how much the attacker was lagging when they fired the projectile. Alternatively, just by how much they're lagging at the very moment, but that's harder and fininicky because of the second thing. In order to make collision realistic for the person being hit, extrapolate the projectile position on the client side by how much the attacker was lagging. Just store the projectile's "lag" while you sync it.