has nothing to do with your problem,
snaps is no longer configurable
cl_packetdup

seta cg_smoothClients "0.5"

*facepalm*

How about rather than offering the useless facepalm comment you actually explain why that value is not good.

1) Unless they changed it and re-added it, smoothclients was serverside in qlive and thus it wouldn't matter if you had it in your config or not
2) How would you have 1/2 of a smoothclient?

1.) I didn't know if it was client-side or server-side
2.) I don't know how you could have half a smoothclient... I have just seen it in stermy's config, and another pro's, but I dont remember who...

it's a boolean command. 1 on 0 off.

but it's locked 0 serverside anyways :p

This is in Stermy's most recent cfg... I don't know whether its supposed to be whole number values or not, but he has it at .5 as well.

See #6

@ j0sh and blade

Stermy and noctis both are guilty of having non-ql cvars in their ql configs.

cg_smoothclients is definitely not effectual in quake live.

pb_sleep does not activate when in a config. You have to type it in manually to get it to work, or bind it to a key (preferable). Try this out for yourself, you have pb_sleep 500 in your autoexec, you load the game and type pb_sleep and it will say 60. It also resets after each map change.

However there is a way to fix this, after you type pb_sleep 500 in the console, type pb_writecfg . The value will then be saved. It writes to pbcl.cfg located in documents and settings/%user%/application data/id software/quake live/home/pb/pbcl.cfg

It's not likely to reduce your lag by much if anything at all though.

what other cvars besides smooth clients?
(which wasn't always serverside in ql btw.)

com_blood 0 (ineffectual in ql)

cg_nopredictitems 1 (no such cvar, cg_predictitems already in config)

cg_drawFragMessage "1" (just needs an s on the end)

with com_blood 0 you can't shoot corpses when playing bots, so there is some effect ;p

yeey!

with this at 0 I couldn't shoot dead bodies when in a server either, not just bots

thats impossible :)

well, after this last update I actually had to put com_blood 1 back into my cfg, and I couldn't gib them until I did, so....

not calling you a liar or anything, just sayin' =)

traceroutes are always a great help to figure out the problem.
since the pings on other servers than the QL servers stayed the same, i suspect peering / routing problems.

what pb_security does ?

Unfortunately your problem lies in routing and not in settings. Which sucks because it is entirely out of your hands unless you have some close friend at your isp who somehow can specifically handle stuff on their side.

Even then I am not entirely sure anything can be done.

I had the same problem several months ago, found out that theres a problem with tracing, server side. So I contacted server provider for QL (which is i3d for Europe, not sure if its the same for USA, just google it out), sent them a few Winmtr results and the whole issue was fixed within few weeks.

i have the same problems with a ping oscillating around 30 where i usually get 11 up til 70

Alright, back to this topic. Heres my tracert:

http://i48.tinypic.com/11hs6xd.jpg

Whats the next step I should take based on these results?

#3 was right.

it would help if you'd say which ip is which server because i doubt anyone would like to look those up just to help you. from the looks of it you're getting re-routed from nyc -> chicago -> nyc server.

where do you live? what kind of line are you on - university? if you are write a mail to your sys admin. atleast over here these are nice people :d

Sorry about that. First server is a Chicago, second server (and the tracert) is a NY. I live in Boston, on a very fast university connection (http://i50.tinypic.com/i3uzao.jpg). Will try writing to our sys admin.

the route is obviously fucked, you get routed through chicago from boston instead of going straight to NYC.

ffs make a tracert to server and give us screenshot.

old post is old.