[Closed] demo/netcode screwed up?
one of both is fucked, if its netcode then u got serius problems, if its demos then its less of a problem, rather more of annoying.
Could you explain a little bit more the issue, since i could not get it with your post? What is the problem? The info at the left of the screen? Btw, what is that info? Sorry for my ignorance but i have never used it. Also, is the demo an mvd demo?
was that a missed-shot in the end? (Target: -1)
__________
epsislow
If its about the missed shot, it can be explained because of ping. Btw, who is the player making the rail shot?
Please, if you have nothing to add to the issue being discussed, dont post here, i would greatly appreciate it.
any chance having a demohaxx which "buffers" demo while recording so u can watch it like zero ping
You'd need to have serverside POV for that... discrepancies between a demo and what really happened are well known throughout the Q3 games, i don't know what's so amazing about this. *shurg*
OR MAYBE MARCUS IS CHEATING QUICK MAKE MOVIE GO
as far remember beast said the net code is untouched since 1.03 (if I’m wrong then please correct me)
and in 1.03 the situation with missed shots happened pretty often when enemies lagged, btw Marcus was always a bit hard to hit enemy because his packet loss
never had such situations in 1.03
meanwhile i got my own theories about that, however, we can get server side demos if we really want, there is a ioquake proxy mod for getting those demos, used in defrag.
anyways, if im right, netcode started being nuts somewhere in development of 1.04, and the only altering to netcode since start of 1.04 is the -10 msec netcode haxx that was removed.
Lol, never had such situations in 1.03? Are you kidding me? That happens in absolutely ANY unlagged game (please read this link, specifically the "prediction" section to get an answer to this shot).
You have no basis to say that. Ill say it for the n-th time: the hitscan code was untouched, and the ping differences among 1.04 and 1.03 in both scoreboard and lagometer are only visual and do not affect the way hits are processed in any way.
was a missed shot, occuring on demo playback of mvd/normal demo with q3mme and normal e+ 2.0A
screen taken on exact frame by q3mme
hurrenson: "This idiot is apparently not familiar with a rail/sniper style."