i havent played with it yet but i have major issues about having to aim miles behind the model, lets see if this helps :F

you mean because of this?

http://www.sendspace.com/file/innbsb

timenudge fixes nothing.

"so want to hear opinion of experienced players."

find out what suits you best ;)

I already like -20 value, but want to hear opinions of others as well. :)

-20 is nice, but they become extremely stuttery, as if they were moving around the map at 30fps.

-10 is better, except when they move at faster speeds, which is when you get the stutter again.

I was told in irc that it's an extrapolation bug, and can be fixed easily, so who knows.

I don't think a glitche that happens when feeding false data to the extrapolation can be called a "bug".

I'm pretty sure it's a bug, because I have to aim a mile behind against bots as well. It's QL:(

ps: and I also still have this one after (almost) a year! And it's a different OS, a different machine, a different modem, a different location..etc.. I have net_restart binded to a button now, and I used to press it when I see my ping skyrocketing mid-games.

edit: oh, almost a year old post, sorry about that:)

Cpma's (unrestricted) cg_nudge combined with xerp 1 works like a charm. They should allow lower values, but i guess the netcode wouldn't handle it.

Anyhow, you should be using it with projectiles only.

Thought with xerp set to '1' you're not supposed to use nudge?
Or alternatively, if you wanna use nudge your xerp should be set to 0 or -1?

Wrong. With xerp 1 the shots actually do register as if they would normally without any alterations. With 0 or -1 the jitter is worse and the shots just skip through the model and it basically becomes useless.

But I was trying to say that from what I remember reading, you shouldn't use nudge with xerp 1 b/c it screws up the calculations (which is why I believe they recommend using xerp 0 or -1 if you want to use nudge).

#23 still stands (as far as I'm concerned) and I've been using nudge varied from -50 to -100 (depending on my ping) with xerp 1 and it works better than with 0 or -1. Try it yourself.

I have tried xerp 1 with nudge and it was awful.
No idea how you can stand it. :/

With q3 i used to use -20, haven't tested in QL but i'll use whatever i can to help make shooting feel more instant :-)

I'll try various timenudge values as I cannot hit shit with shaft when it is on.

It works best for rocket/plasma anyway.

I tried binding different timenudge values to different weapons but I noticed that their is this annoying short "freeze" when changeing timenudge values midgame.

ive experienced that as well. im playing without it - i still hit well even with ping 40 thanks to the "not so bad" netcode. i cant stand the laggy shit tn produces :x

i'm pretty sure timenudge should not do anything with the 'unlagged' hitscan weapons... unless i'm missing something :>

the jitter seems to be worse than in q3 though, either that or i'm too used to ql's netcode by now.

-12 was value in osp where stuttering became noticeable.

and whats the advantages/disadvantages to using -11 ?

IT'S ONE WORSE DAMMIT!

but if you use -12 youll get stutter :(

Nah, I played with -15 and it was fine, but I had high ping (~100ms).
With -20 it was pretty bad, tho. :(

I remember negative timenudge values being much smoother in OSP and in RA3, infact, ATM it's feels even worse then useing xerp 1 in CPMA.

Will it be possible and if so how easy to fix or atleast reduce the stuttering negative timenudge values are causeing or does it intefere with quakelives horrible "unlagged" net codeing?

cl_timenudge and cg_smoothclients 1 were never as smooth in RA3/OSP as the combination of cg_laghax 1;cg_xerpclients 1 (i.e. cg_smoothclients 1 renamed) in CPM. You probably just got used to mentally ignoring the skipping in RA3/OSP.

if it still works like in q3 then it's basically lagged+smooth vs less lagged+stuttering as timenudge kinda cuts the buffering time that turns the single snapshots into a smooth motion

and I always prefered the smoother yet lagged version because I found it easier to aim on a smooth target if you know how to compensate for delay. so cg_truelighting 0 + cl_timenudge 0 (used to play on 65+ ping).

CPMA netcode is a different story, feels wank when coming from OSP but after a while it rapes stats-wise.

Wasn't the build-in 50ms lag removed? Does that mean with ping 15 and tn -20 I can look into the future? o_o

I suppose it is related to to your ping, but to duration of the server frame.

I swear there's only ever been a built in 5oms lag when spectating ?

you can look to thing which is prediction of future which means its not sure that it will happen, its just the most likely to happen -situation.

i might just put a positive value there so that ill stop hitting rails when shooting behind enemymodel

Wow clever idea! Your shaft will grace u for it! :O

Started using -20 for a little bit but found people that were warping were even worse so I use -10 now.

It's kinda like how I play various goldscr games like cs, dod etc where I use ex_interp 0.01. It makes stuff jitter, but you get used to it after a while and it feels like you're seeing an accurate representation of what's actually happening.

So, I dunno what timenudge does, but -10 feels good, and if it feels good, do it.

ex_interp 0.01 is the normal value, it shouldn't make anything jitter unless the server is bad or the jittering players are not using correct values for other settings :) For HLTV it's 0.1 though, I'm talking about when you're playing.

0.1 is default. 0.01 is something you'd need to autoexec.

I know, I didn't say default I said "normal" as in the norm in tournaments and among players who know something about interp :) And like I said, it's not your own use of 0.01 that makes things jitter it's the bad settings of servers/other players.

Yeah I know that, but even if you're using 25k/101 with 0.01 and everyone else is, the result is slightly more choppy then with 0.1 smoothing it out. I don't notice it anymore which is why I don't care. It just looks normal to me so whatever~

So players jitter with tn -10 but though I feel more confident with RG now :D

After moving back to SA and playing with 60 to 80 ping, the -20 is a blessing, making rail way way more responsive, and I can actually rocket jump. Not sure if I am going to use it for every gun though, I am going to play a bit longer and see what the best values are.

how does cg_timenudge alter your ability to rocketjump?

AFAIK it only predicts opponents most likely movement...

Placebo effect, in action

;-)

cant they just increase the servers to 100 ticks like the css servers? whats the issue ?

They could... but nobody has ever requested it. =p

what are they set to currently?

40 snaps / second

^ this. and as far as i know its more than enough.

we tried that in q3 and it sucked... lots of problems plus lots of traffic.

use -20 on lan to see 20ms ahead

Well its mostly no use since it propably does misspredict quite often -> more harm than favor

no, it does not. especially on lan.

it did in q3 osp for sure.

no, it was considered a cheat on lan comps cos it did not misspredict 'quite often'.

it wasn't a cheat when i played back in 2002 - 2003 but rather a frowned upon thing to use when u did /players some lan admins forced it to 0 some didnt. I dont know when osp officially made it 0 for lan.

erm what is this for?

In some Q3 version it worked smth like this:

http://forum.drc.su/yet-another-cl-timenudge-...t2301.html

Dunno how it is exactly works in QL, but looks very similar to what described there.

old but still...

By Strider

Someone already said a bit above of what cl_timenudge does but here's a more complete understanding of it.

The Q3 client likes to have two snapshots active. The latest one and the previous one and it uses them both to interpolate player movement.

Most servers default to 20hz (meaning a packet is sent out every 50ms). A server sends out a packet containing a snapshot of everything in the server (that is visible to you), players, rockets, items etc and the client receives it then another is sent out 50ms later and so on.

Once the client has received two packets, it starts to interpolate other players in the game from their old position (contained in the first snapshot) to their new position (contained in the second snapshot).

cl_timenudge <negative value> effectively changes that behaviour by reducing the time available for interpolation.

Since the interpolation time window is 50ms (on servers that use the default 20hz), you can effectively remove it by doing cl_timenudge -50 or you can half that time by doing cl_timenudge -25.

By removing all or part of the interpolation time, you are forcing the client to show the latest position of your opponents much quicker than it would normally. That means when you shoot at them on screen you have a better chance of hitting before they've moved far enough for you to miss.

tl;dr you all probably know and experienced what tn does...

ql servers run at (afaik) 40hz, so the window is reduced to 25ms. tn is restricted to +/-20 anyway.

why would you do +20?

used to put it on 200 on gtv wich for some reason made it smoother to spectate ;x

otherwise, no idea. but maybe to simulate a higher ping if ur used to it?

what he said, it will extrapolate between snapshots. never saw any use for it except for gtv.

can we now discuss what value I should use for cg_playerlean?

this :o

9000?

Probably slightly higher.

i always used 1 in q3 but believe 0 is better in ql, here's why...

because of the difference in hitbox size i could get away with using tankjr as my enemymodel in q3, i can't do that anymore in ql (using keel now). tankjr's leaning animation is different from keel's as he's less twisting his torso to the sides, more like twisting at his knees :)

when i look at the screen posted in the other thread the difference between hitbox and model is not something i want.

agree/disagree?

ok nice input thx. im trying out 0.5 atm. dunno what to say :x hardly ever notice the effect :D

saw a stream with calipt and 2gd, and calipt explained that most "good" players use some sort of copy paste config of noctis, and his last updated cfg had 0.5 value for playerlean, so there u go :)

noctis the magician, they just want to steal his faerydust and secrets!

Anywhere between 0 and 0.5.

0 is so funny I just laughed.

Isn't it weird that i don't notice any stuttering even if I use -20? It just feels like 0, like if it wasn't doing anything.

they fixed it , when it was stuttering it was bugged badly ( rly)
dunno why they didnt say that in changelog.

So it's working, but it doesn't stutter? Isn't that magic? In Q3 i remember -20 was terrible, the model stutered a lot. When I use -20 in QL i don't notice a difference compared to cl_timenudge 0. How is that even possible?

It actually does stutter somewhat, I guess you're just not paying attention that well. Also there are some additional negative effects like projectiles appearing out of nowhere and overall the game feels slightly more "weird".

I guess whether or not to use it depends on how much you like the smooth feel over the decreased latency.

Im paying attention, and I don't see stuttering.

It does. You can see it easily by just playing against bots.

I would not recommend timenudge below ping 50 really (except maybe for projectile weapons like plasma/rocket).

Also: As far as I remember, the timenudge jittering has been corrected a few updates ago?! The movement is affected (I don't know how but it is) when using timenudge which is another reason not to use it.

>plasma/rocket

I thought it was ideal for weapons like mg and shaft.

I would say no. But I need data to back up my assumption. Can any timenudge/netcode nerd help me out here? :D

it should not make any difference with hitscan weapons (they *should* be "unlagged" by server-side backwards hit reconciliation anyway).

if you played q4/xbm you probably remember cg_projectilenudge, tn helps a lot with rl/pg.

So timenudge was beneficial for hitscan weapons in the original Q3OSP netcode since it was not an "unlagged" netcode if I understand it correctly.

So should I bind tn 0 to all weapons but PG and RL then? what value should I use? I play with different pings, 25 in my country, 60+ outside.

ye, tn was beneficial for all weapons with no difference in q3. binding different tn values to weapons resulted in some lag and a short stutter in q3, no idea if it's the same in ql. i wouldn't do it that way :)

So what would u do, play with a balanced tn in all weapons like -10?

noctis does that

ye, either that or keep it at 0. i live in frankfurt and ping 6-7ms to the servers located here.

also someone told me cg_smoothclients is back, havent checked myself if it works tho

cypher uses 0

//thread

Alien can use anything he wants, even 65535, and he still owns you.

Cypher also use Razer mouse, but it doesn't mean that everybody should use that overpriced crap. :)

abyssus is one of the cheapest mice out there.

Cypher also use Razer mouse, but it doesn't mean that everybody should use that cheapest crap. :)

:)

can confirm this

and i can confirm that u can confirm! ;D

-20
confirmed
u can even play on us servers vs czm and get dissed for beeing a high ping bastard
i was get kicked for this 2 times in a row!!
2 weeks ago
:((

i have a ping of 55-60, should i use timenudge or is it without better ? any advice ?
another question is: if i use timenudge, do i need to turn off smoothclients ?



This are my actual Nettsettings:

seta cl_maxPackets "125"
seta cg_smoothClients "0.5"
seta rate "25000"
seta cl_packetdUp "1"
seta cl_timeNudge "-20"
seta cl_maxPing "800"
seta cg_predictLocalRailshots "1"
seta cg_predictItems "0"
seta cg_noPredict "0"

I ended up not using timeNudge at all.

//[--Network Settings--]
seta cg_predictitems "0"
seta cg_predictLocalRailshots "0"
seta cg_noPredict "1"
seta cl_maxpackets "125"
seta cl_packetdup "1"
seta cg_smoothclients "1"
seta cl_timenudge "-10"
seta rate "25000"
seta snaps "40"


my settings. -10 works well for me with ping 25.

not sure about smoothclients, though.

I just use -20 for high ping, does seem to help, and I did like +20 for low ping (10-20ms), but seems its been removed, so I use 0 for anything up to around 60ms.

i use -20 on lan and so i can see the future!

i use 0 unless i have 65ping or higher, 60 or below i've found it to be detrimental

I use some on 50+ ping. It helps me hit more LG

I use some on 50+ ping. It helps me hit more LG