got a question for some server admins or ppl who know …
What does anti-lag do and how does it work,
A friend of mine says hes getting hit by “ghost bullets” even after he killed that person :???:
Any got the awnsers im lookin for ?
got a question for some server admins or ppl who know …
What does anti-lag do and how does it work,
A friend of mine says hes getting hit by “ghost bullets” even after he killed that person :???:
Any got the awnsers im lookin for ?
Read this. It’s the Unlagged FAQ, which isn’t exactly the code that’s in ET, but close enough.
thnx that has cleared it up a bit,
but those ghost bullets,
those are actually bullets wich have hit him? i mean from another player who has shot him ?
There are two things you might think are ghost bullets.
dying after you are out of view of the person who killed you. This is an artifact of antilag, described in the unlagged FAQ. Essentially, they were aimed at on their screen when they shot, you just got the effect a bit later.
you often see tracers where they are not supposed to be. These do not hurt, they are just graphic glitch. Supposedly fixed in the next version of etpro.
You know there is a bug in the RtCW anti-lag, where if your ping is VERY
low (I don’t have the exact figure) it completely screws up, and its
possible to shoot and shoot and not hit anyone !!!
I had to change the code slightly in the latest version of WildWest, so that
players with a ping under 15 don’t do a historical trace… this fixed the
problem 
Dunno if this problem exitsts in ET though.
btw reyalP, you in a new clan ?? I noticed a name change at planetwolf forums.
Hewster
It would be nice if you could check in with rain or bani and see if this is still the case in ET.
btw reyalP, you in a new clan ?? I noticed a name change at planetwolf forums.
Hewster
Yup, finally decided to try playing in a real clan
http://www.naked-warriors.com/
It would be nice if you could check in with rain or bani and see if this is still the case in ET.[/quote]
I never noticed this bug in RtCW, personally, but we did fix something in etpro (before 2.0.0) that might’ve caused something like this to happen… We gave several of our fixes back to SD, and most of the fixes (including the antilag fix) made it into the 1.02/2.56.
That said, I’ve still never experienced it myself (but I’m not fortunate enough to have a sub-15ms ping very often, unless I’m testing something locally!)