dno about the ping issues
to counter campers, camp more!

Shouldn't lowpingers be able to react quicker and therefor dodge your lg better?
Ping 60 warpers with 40% lg are disgusting btw.

I play warsow and QL at 160 ms on average (140-330) and they only thing that really pisses me off about it is the dodging at high ping shooting is not so much of a problem since you can sort of get used to the delay when shooting but dodging is hell

^this. Rockets fly near you and still hit you in the face.

<3

If you play different pings all the time then there's is little you can do because the LG is so ping dependant.

you should think of it like driving a car, and how weather conditions change the physics etc, some drivers adapt better than others, so either learn to adapt better or simply play on one track (I.E. A fix ping range). Why do yu think pro players bootcamp? To simulate the LAN settings.

As for if22 stylee on ztn or any other map if someone plays defensive then they define themselves before the game starts, that means there are key points on the map you know they are more than likely to be before they even get there, which means you can at times line rails before you can see them, you can also trap them based on anticipating the campiest route that they might take.

IF they camp then you need to be campy too, or work extra hard on getting the first frag and put additional pressure on them, if their game revoles around camping, it will unsettle them.

You can't lose frags that you don't give away so even if you have to grind the first 4 minutes out, dont' commit to anything until you know you can win a certain situation. Get a frag up and they'll slowly panic. If someone has to camp to win they are usually a weaker player cos when you're better you can steam roll someone, so if they camp you, deep down they know you are probably a naturally better player than them. Use that mental aspect.

there's loads of potential counterpoints to what I said, but that's the game, there isn't a universal rule for success, most great games have that trait.

Tnx. nicely writen.. I just envy those guys with 20 ping sooooooo bad!!:S

hitscan is not ping dependant in ql, projectiles are.

lol

yes?

rockets/plasma are way harder to hit with 60 ping than with 20 ms

lg and much more so rail are less affected

rail is the best weapon with high ping by far and rl the worst

any weapon that uses hitscans are the same.. tracepoint( viewOrigin * vec3( weaponRange, 0, 0 ) );

they are not projectiles, if at that point or in its path, the bounds (mins/maxs) clips a entity, you get a entity list

for( ) {
ent->damage();
}

no, I could try to explain it to you, or could use that time to play militia. The second sounds more fun.

yes, i code all Q43A, i know the SDK inside and out, all hitscans in all engines are the same, except in Q43A because there are no hitscans, because they are shit

why dont you try Q43A, do quake4Ded.exe +set fs_game Q43A +exec serverconfig.cfg

dont need no other pack to start a dedicated or listen server, just the mod and quake 4

im 1337 fuck ya nans motherfuckers,. its all unified, SP MP listen dedicated, win32/linux its all in 1

windows or linux connects and they dont have mod locally, they will download it off your server, with both drivers in game666.pk4

cosy, and i would fuck your nan. if she got purple hair, i will atleast let her suck my dick

if you got quake 4 server on a game server hoster like multiplay/inx/ or other, you just upload q43a folder, go into your server control panel, set the fs_game, and restart server


fs_game does`nt work in inx CP, and support will take a week to patch q4 to 1.4.2, get them to add a custom serverconfig.cfg to the quake4-ded ... run cmd in q4-start or whatever

or just use rCon, you`ll have to hit your ftp of server, and find the password in whatever cfg is being used

spawnServer - start the server.
disconnect - shut down the server.
listCmds - list all console commands.
listCVars - list all console variables.
kick - kick a client by number.
gameKick - kick a client by name.
serverNextMap - immediately load next map.
serverMapRestart - restart the current map.
serverForceReady - force all players to ready status.

cmds :

disconnect
set fs_game q43a
exec serverconfig.cfg
if not in serverconfig.cfg : spawnServer

you all try Q43A

rl? what a joke

laugh all you want (and plus jamerio), it's still true.

Ok I forgot about plasma. But it is impossible for me to hit anything with lg if my ping is above 60ms. At least for me. Rail and rockets are "fine" under the given circumstances. As plasma isn't a top tier weapon and nearly no-one uses it in close combat as a main weapon I think it is ok to say that lg is way more affected by ping as rockets. (for me)
So that is why I loled at your comment :P and no I won't plus jamerio because he is a retard and doesn't know shit about anything.

yea, no idea what happened to plasma tbh. the weapon stats are the same as in q3, the netcode shouldn't be (much) different but the gun plain sucks nonetheless.

nomip.square projectiles, and i honestly feel like the projectiles traveled faster (not higher rate of fire)

thats not true...

I play with 90 ping and its extremely hard to get any sort of lock on with lg, especially if the guy is properly dodging it and not going straight in a line...

I have alot less of an issue when I somehow ping 65 once in a blue moon and although its a poor judge, its "surprisingly" even better when I fire up some bots for warmup.

Now, perhaps you meant this for the 0-60 range of pings which I can somewhat agree on. but above 75 ping things really start to go to hell.

edit: same applies for rail and mg of course. rail is the least that gets affected but the randomness of hit/miss on model occurs plenty.

you're right, iirc id stated the "unlagged" netcode works up to either 70 or 80ms.

playing bots means playing on a listen server though, not a dedicated one. that is completely different anyway and not a good way to judge the netcode at all.

the limit is 70 then judging from my experience. as for the listen server, its atleast close enough of a simulation to see how things would work on a dedicated one.

na, i disagree. even the physics are very different, not to mention the whole "new" netcode idea (server side backwards hit reconciliation) is done with when server=client.

I simply lack the experience with low ping dedicated servers then :/

u mean like this: http://www.own3d.tv/video/28704/DreamHack_Sum...Av3k__ztn_

???

actualy due to netcode/antilag/callitlikeyouwant you will hit more LG with 35-40 ping than with 5 ping.

He apparently experienced the opposite. Still no proof for either statement so far.

you are wrong :) I am playing always with 50 ms and in few server with 38-42. I feel same with 50 and 40, but I feel shit with 58 allready and 66 realyshit.
I was in lan, played with low ping, with worse settings I did realy better lg. I played with 25 ms on internet from swe too, it was realy better too.
This is all lamers bullshit about big ping is better! It's becose they don't know how to aim with LG/MG and lag helps this way.

SO TRUE! when i have 60 ping i can't dodge 20 ping rockets..it's like they chase me like those tomahawk missiles..:S they just seem faster and usually i just get bounced from one rocket to another and btw there is a huge difference if you have 49 or 56 ping..i cant hit anything when i have 56+ ping.. it's like a breaking point. under 56 it's fine..(for me atleast)

Lately I have noticed the same thing. It seems like the lowest the ping someone has the best dodger he is. This is weird net code. It should had been the lower the ping the better the aim and not the harder to hit.

best ping range for LG is from 25 to 35ms.

the lower your ping, the better it is for projectiles weapons, RL GL PG.

rail works like LG, but reload time is much longer, that's why sometimes it's counted as a miss when it should be a hit.

best ping range for LG 35-45. You don't need as much speed as with low ping to high crazy LG acc at thoose pings.

& i know you're aware about that.

stop trolling me pls.

No, the best ping range for lg is from ~25 to ~35ms. If you have like 20ms, it's still very ok, same for ~40ms, but it's OPTIMAL at ~30ms.

and from my own experience, i hit a bit more when i'm on french servers (~37-40ms on scoreboard) than when i'm on german servers (~47ms). Also, used to ping ~31-33ms on french server once, and it was smooth as hell.

btw, i have cg_truelightning set to either 1 or 0.8, when i aim, i don't try to compensate the ping by aiming at the sides of the model or anything like that, i just aim straight, as if i was on LAN.

^

Im currently pinging something around 45-50 on .de and 60-65 to .nl and even with that small difference im already noticing a decrease of at least 5-10% in accuracy for lg when playing on NL and overall accuracy is definatly worse, too. Low pingers are exceptionally hard to hit and projectiles at 60 ping.. pretty much useless . I used to have a better connection at my old apartment and was pinging around 20 and hit at least 5% better LG than with 45ms nowadays, too. Dont know why low pingers claim RG was harder (?) i was getting better accuracies for that, too. Sure, there are people who even hit well with 80 ping, i for my part cant do that, especially because i know how it is to play with low ping. oh yeah, i definatly want to confirm that bullshit when a 15ms player fires a rocket and it looks like it misses you by a mile and then you catch it with your face or other situations like when you see someone fire a rocket at you and it basically hits you the same split second. I have to admit, back then with 20 ping i thought people are whiners when they claim it sucks to play with 50ms, but it obviously makes a huge difference.

tl;dr from low pinger view: whine about high ping, LG is nothink online, excuses for being bad and not hitting a thing with projectiles.
tl;dr from my view: even with the so called unlagged netcode ping makes a huge difference and benefits low pingers.

btw, wasnt smoothclients the option to enable/disable the unlagged thing? considering its serverside now and disabled, what exactly makes the game unlagged now?

afaik they built an improved smoothclients/xerpclients into the netcode

How does this affect timenudge then?

i have no idea tbh, i used timenudge in q3 but i find it to be very different in ql

why is the car of my neighbor (Porsche Carrera GT) so much faster than my cheap car? I just dont get it. Its soo unfair

The thing is, considering the game is (supposed to be) unlagged, any ping lower than 80 should give you the same conditions/experience and not benefit a certain ping range (not even saying the lowest ping = best). Apparently this is not the case. Theres also no official statement to clear up what exactly has been done to the netcode (s. post 26). Tbh, it even felt better back when smoothclients was still an option.

c1, both cars are supposed to drive at the same speed, or at least give the driver that impression. with a speed limit of 80 it doesnt matter if you sit in a lada or a porsche gt driving 80km/h.

speed limit or what ever... the porsche will always be the faster car since the accelation is supior to any usal cheap car and (I hope) there is no speed limit in ql. How do want to break physics? The faster guy will always be faster

As long as the old car is capable of driving 80km/h it doesnt matter if there are faster cars.
As long as your connection allows a ping lower than 80ms it _shouldn't_ matter if there are faster connections / lower pings, given that the game is meant to be unlagged up to 80ms. No doubt that a lower ping under these circumstances can still be beneficial but not as drastic as it is at the moment.

tl;dr car example is bad and so is the netcode.

Btw, back to my original question: If QL has built in ways to compensate the lag (or whatever the fuck you wanna call it, xerp, unlagged..meh), doesnt that conflict with timenudge?

If QL has built in ways to compensate the lag doesnt that conflict with timenudge?

Only in your perception of game.

Timenudge governs amount of time client waits for a next snapshot from server to start interpolating players moves. If timenudge value is negative then client on each rendered frame extrapolate a bit players movements and correct this with data from next snapshot.

Unlagged code works completly on server side. Each packet from client contains timestamp. When server needs to check hit registration it rewind back a game history to the point when gametime equal timestamp from client`s packet and makes a hittest. I.e. server predicts client`s knowledge about game situation and uses this data to check hit.

ping is just a number

l2adjust