no idea if its a change due to mod update, but can it be that we have more shoots in same frame then way back in 1.03? because i cant remember shoots being in same frame at all in 1.03 while lately i seen them happen quite often, somebody rails and get railed same time.

wouldnt wonder if shoots are just recorded on a specific frame (as sv_fps 30, one frame would be 33msec which is a lot.) and depending on interpolation it can truely do some odd stuff towards hitting.

Yesterday I had the biggest blind rail fire since I play quake. I would just shoot and the rail would act as if it had a lid to stop the fire going, this happened while even firing 2 shots one after another. Also fired a lot of rails that were going through my enemies. This is the most pissing bug in this new version, idk why developers don't put an end to this one, there must be a way to do it.

i dont know about u but i didnt had not even 1 railscan i can remember .. and i alsao tested with Ali the range of the rail using xcm_tricks2 and using big fovs like: cg_fov 3 + sensitivity .1 + cg.railTrailTime 100000 (which is a bit similar to the above test) and the railshots were straight on the target ... we didnt use plusN/ plusC.cfg ... we used another server cfg (but still e+ 2.0a) .. so i guess: maybe its the server cfg or your cfg ?

and it also never happened to me to rail some1 and not hear the rail of hit unless i had ofc >200 ms ping or loss >40%
____________
epsislow

wrote:

no idea if its a change due to mod update, but can it be that we have more shoots in same frame then way back in 1.03? because i cant remember shoots being in same frame at all in 1.03 while lately i seen them happen quite often, somebody rails and get railed same time.

wouldnt wonder if shoots are just recorded on a specific frame (as sv_fps 30, one frame would be 33msec which is a lot.) and depending on interpolation it can truely do some odd stuff towards hitting.

during game i often get the feeling that this hit evaluation once per snap also happens for other (one ofc an instant hit one) weapons.. like "player a killed player b with bfg" "player b killed player a with shotgun"...

and to get weirder i even think that (or better "feel" and i know that is very uncertain) when in e5 sometimes i push fire, switch weapons and fire again the second shot is delayed as if the game waits for the next snap to place the shot in... 

call me stupid if you think otherwise.. but something feels weird sometimes

wrote:

Nolte009 wrote:

i am wondering why nearly every map i play i get at least 1 rail hit (sound & all) and my enemy doesn't die. because i hear rail hit, i look away for next enemy and i die

Seems possible in plusN config - 600 rail damage covers soft limit (H+A) only.

it is not about surviving the shot by enemy, but that client see the situation as hit when server does not

i often hearing that i have hit somebody, then trying to move to the next enemy but after a second i realize that the enemy that should be dead is still alive

more often i hear that my rail have hit enemy but servers later send the informations that i have got killed.. it's extremely annoying