new awesome technical feature, apparently there are people who think high ping is better so they added this

:(

Very strange issue. It looks to me like your bandwidth is being over saturated by the game.

Try adjusting cl_maxpackets, rate, etc. Also could look into some of them cheap net tweaks for your OS.

How does your bandwidth fair on speed tests?

Hey:)

I got fiberpower, so it's a zillion Mbit.
My network settings are fine, I ping 31ms on de servers in cpma (or any other game) with or without net_restart:)

Could you please elaborate a little bit why do you think it's a bandwidth saturation problem, do you see that in the lagometer?
I was thinking about what you wrote, but just can't figure out what you meant:(

This is exactly what happens to me when I'm running heavy torrents. I don't play actual games when running torrents but I do in pre-game when waiting for someone to come in.

What happens is my normal ping will suddenly skyrocket and remain high for a period of time. This happens presumably when there is either a spike in my downstream usage, or upstream usage.

These problems are not easy to diagnose, are you sure it happens on every single QL server you join? If so, and as like you say you have no problems in CPM then it does absolutely indicate a QL related problem. The net-traffic shouldn't be fundamentally different enough from that of CPM to have such a problem appear though.

If only you could test a QL server ip in CPM.

You say when you are running torrents, you can instantly double your ping with a /net_restart, and halving it with an other net_restart? Are you sure? Please double check this because I just can't believe that.

The reason why I created this thread, is that my ping doubled, and I think this extra latency is not happening because I suddenly routed around Europe, but because it's created artificially or accidentally. But there is a problem with it, and sometimes it's happening twice when it was only "intended" to happen only just once per connection.

It's not acting like a longer distance route. How do I know this? Well, tbh it was obvious right at the first game.
When my ping was 30-40ms to Germany, (because of the hopelessly messed up net-interpolation of QL), I had to aim behind the NME (a lot). On NL, UK, PL and FR servers, where I pinged 40-60ms, this effect was much smaller, and on servers like Spain or Russia (60-80ms), it was so little, I almost had to aim right at the NME model.
Basically the latency generated by the distance to the servers were neglecting the lagging-hitbox effect.

With my doubled ping (60-70ms), I still have to aim behind the same amount on DE servers just like when I had 30-40ms.

The worst is, and why this whole thing is simply beyond my comprehension, is that it's not something what QL only adds graphically onto the lagometer, but what I really feel during the games, and something what can be traced clearly in my route as well.
If my ISP simply discontinued peer2peer with i3d.net, and I forced to use a longer route, why do I need to still aim the same amount behind the NME, just like before?

I understand that the following may sound very stupid, but somehow, somewhere, my packets are running circles in some kind of a giant buffer for 20-30ms before continuing the journey towards the QL servers, and somehow - when this effect accidentally triggered twice, I can reset it with a simple net_restart.

I'm not an Internet masta or anything, nor do I understand and know everything about ISP routing stuffz, but I was building networks for companies with 100+ ppl and also I was running games servers since Doom, and I honestly never saw anything like this before, that's why I asked if somebody else maybe have a clue what's going on.

It's late night, smooth Internet time;), so I just made a new tracert, and hmm, well... I wonder about what the hell hop 7 is:(

Tracing route to quakelive-hosted-by.i3d.net [91.198.152.121]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 12 ms 11 ms 12 ms catv-89-135-217-94.catv.broadband.hu [89.135.217.94]
4 27 ms 28 ms 25 ms 84.116.240.2
5 44 ms 26 ms 28 ms de-fra01a-rd3-xe-4-1-0.aorta.net [84.116.130.189]
6 29 ms 28 ms 25 ms de-fra01a-ri2-xe-2-2-0.aorta.net [213.46.179.14]
7 50 ms 50 ms 50 ms 4.68.62.209
8 51 ms 50 ms 54 ms LINK-11-GMB.edge4.Frankfurt1.Level3.net [195.16.162.2]
9 51 ms 51 ms 51 ms quakelive-hosted-by.i3d.net [91.198.152.121]

And here is a random DE Q3 server

Tracing route to exy.it.cx [95.156.192.76]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 45 ms 12 ms 30 ms catv-89-135-217-94.catv.broadband.hu [89.135.217.94]
4 29 ms 27 ms 24 ms 84.116.240.2
5 27 ms 48 ms 48 ms de-fra01a-rd3-xe-4-1-0.aorta.net [84.116.130.189]
6 78 ms 38 ms 25 ms de-fra01a-ri2-xe-0-2-0.aorta.net [213.46.179.110]
7 68 ms 28 ms 47 ms xe-5-0-0.fra20.ip4.tinet.net [77.67.73.105]
8 57 ms 25 ms 28 ms xe-1-2-0.fra21.ip4.tinet.net [89.149.183.73]
9 30 ms 28 ms 31 ms gw.ip4.tinet.net [77.67.76.82]
10 29 ms 24 ms 29 ms exy.it.cx [95.156.192.76]

Tried with a new network card? A few years ago I was pwned by the nvidia chipsett integrated netcard-crap, that lagged just like that. I solved the problem by buying a cheap network card in a local shop.

How could my network card know if I'm using q3 or QL or any other game?

1, it's happening on all 3 PCs I have.
2, it's happening with or without my router
3, it's not happening in any other game (inc. q3)

I suspect the problem is at my modem/ISP (or somewhere in the route to i3d), but the first time I had this was right after an update. One Tuesday night I was playing and everything was ok - I went to bed - Update - I woke up and launched QL to see the changes while drinking morning coffee, and had this problem in the very first game.

So it's the coincidence of the year, or something is changed in QL and that's why this problem surfaced now.

Oh, my bad. I thought it happened to all games :S

Something smells like a config problem but can't explain why :)

If you got it after an update and they deprecated some cvar that you left out , maybe it does some freaky lag stuff in processing your net output.

It also seems funny about where your enemies/hitboxes are extrapolated and drawn on the screen on 30 ping and on 90 ping.
I guess they really bugged up the whole aim/tracking with something when they "fixed" hitboxes. I get perfectly normal mouse tracking response on my 48-50 ping.
On 55-58 I get latency feeling off 90 so I get what you're saying.

look up when was the update and whether they kicked something from config that you left in.

yo..it's smth with the hardware. i had same problem on normal 2mb i net. i had ping 50 constantly and then one day i got spikes and ping jumps i tried everything..modem was working fine,my net card was fine but then i found out that splitter got hit by lightning.(some part you plug on telephone line so you devide the interne and phone line or smth like that)..but if your q3 runs fine with constant ping i dont know why QL is fucked up..i mean maybe it's just because is quakelive. if everything is fine with QL you're either dreaming or you're dead:P:P thats my moto=)

imho it might have to do with the netcode, recently had immense spikes from my opponent: i was alone on the server with relativly nice net, opponent joins and lagometer goes in the shitters (140+ ping + spikes, only when he is around me, not when he is on the other side of the map)

its too cold for wireless to work at optimal speed

only worthless if......

everything works better on a cold open night sky. when its snow and frost and below 0, everything is slowed down, even your phone

I get the feeling that id's just using QL as a training ground for their interns inbetween fetching coffee and mopping the floors so these random bugs don't crop up in retail releases.