Strange nex shot

[flea]

Hi,

I'm not sure if this is the correct forum category to post in, but if it isn't let me know and I will post in a different one.

I was recently looking through a demo of my opponent in a recent comp game and I saw a nex shot that appears to miss, then in the next frame magically splatter me into giblets.

I don't understand what is going on, or even if it is a side effect of network latency, my lame rendering gpu, or something else. It might appear differently on someone else's computer when the demo is played back, in which case just say "Nothing to see here."

But on my computer, the sequence of events seems to be;
- crosshair is well below my feet
- next frame the nex fires (hear sound)
- next frame i am giblets
- next frame the trail goes through my giblets

I've slowed the demo down to 0.1 , I don't know if it can go any slower than that.

If you would like to watch and let me know, this happens at 5:30 on the timer, or 14:44:43 on the clock.

Demo can be downloaded here:
http://shaggy.mkzelda.net/tourney/seaso ... l_rage.dem

Thanks for any ideas or suggestions as to what may be going on.

flea

[Sepelio]

This is merely the antilag system at work. It happens in all sorts of shots. Heres two more that show it

http://uk.youtube.com/watch?v=oRPaLdEYeQU

http://uk.youtube.com/watch?v=gEOCnlRBijs

[flea]

I'll have to take your word for it, as I can't see anything in those youtube videos.

Well, I don't have this problem in other games, so I guess I'll just have to go back to something I understand.

[Alien]

You should have used svn version with fixed antilag.

[flea]

You should have used svn version with fixed antilag.

Both clients were SVN, server was 2.4.2.

Are you saying that in SVN that wouldn't occur?

Thanks.

[divVerent]

In svn, it does occur, but less visible.

Basically, the issue is a question of "philosophy" when doing antilagging. If you check against other games, you'll see one of these behaviours:

• Shot gets displayed first, later the enemy gibs: client-side immediate display, but the actual shot is done later on the server.
  Looks great from first person view, looks pretty odd from another player's view (as the server can't "push" the shot back in time, it'll displayed to the other clients at the "gib time" and possibly there isn't even a line of sight between the players any more.
  
  This is what most "unlagged" mutators for other games do.
• Shot gets displayed when the server "executed" it. Enemy gibs immediately after the shot (+/- 1 frame, happens depending on network packet size). Basically, the "truth" is shown to everyone.
  
  This is what Nexuiz does.

Green had said he'll try to implement the first method (as an option). We'll see how it comes out.

[flea]

[*]Shot gets displayed when the server "executed" it. Enemy gibs immediately after the shot (+/- 1 frame, happens depending on network packet size). Basically, the "truth" is shown to everyone.

This is what Nexuiz does.

I'm sorry, but I have to disagree. Shot is played as a sound on the client when the server "executed" it, but often not displayed until 2-3 frames later.

In fact, look at this video
http://aussienexers.net/demos/amazing.avi
I recorded this from the same demo with cl_capturevideo on slowmo 0.1

Here is the sequence of events
- nex sound fires
- giblets
- NMY lands, turns, fires

In other words, I cannot trust my client to show me where the NMY *actually* is when he fires, or even when I return fire. How can I possibly aim at someone who is already two frames ahead of me?

flea

[Mirio]

if you watch it in slowmo 0.1 there is a little delay between the sound and the nex beam , but if you watch it with normal speed everything is ok. I think thats just normal if you watch it in slowmo
probably you should record it! if i watch i can't see anything.

[flea]

probably you should record it! if i watch i can't see anything.

Sry, wrong demo.
The above demo is from the NMY POV.

This demo(below) is from my POV. Even at normal speed I am giblets before the shot is displayed.

http://aussienexers.net/demos/2009-01-1 ... l_rage.dem

When it happened in the match I thought the NMY had actually shot while in mid-air, at an angle, which blew me away. But looking at both demos after the match, that wasn't the case at all, it's just that the display of model+nex trail was three frames behind the actual shot, and he was moving fast.

All I really want to know is if this is a result of something on *my* client, like crappy GPU or something, so I can possibly fix it. Or is it a nexuiz artifact that will/will not be fixed.

Thanks,

flea

[torus]

You should record it, and upload it to Youtube or something. Too time consuming to sift through a demo.