gaps in green line in lagometer


(=TAC=Chron) #1

i am having gaps in my green line in my lagometer. this just cropped up a couple of weeks ago. radar is nearly unplayable in some areas.

i is causing me some serious prediction error and gameplay headaches.

it almost seems that i am losing packets, but i am only 3 hops to my server.

any ideas on how to resolve this?


(DG) #2

gaps? as in nothing there at all? packetloss should show up as red bars, afaik there should only be no line if the ping is lower than the one-pixel chart scale equivalent.

http://www.gameadmins.com/modules.php?name=Sections&op=viewarticle&artid=5
The upper graph (blue/yellow) slides one pixel for every rendered frame. Blue lines below the baseline mean that the frame is interpolating between two valid snapshots. Yellow lines above the baseline mean the frame is extrapolating beyond the latest valid time. The length of the line is proportional to the time.

The lower graph (green/yellow/red) slides one pixel for every received snapshot. By default, snapshots come 20 times a second, so if you are running >20 fps, the top graph will move faster, and vice versa. A red bar means the snapshot was dropped by the network. Green and yellow bars are properly received snapshots, with the height of the bar proportional to the ping. A yellow bar indicates that the previous snapshot was intentionally suppressed to stay under the rate limit.

try opening a dos box and doing:
tracert ip.of.ser.ver

should give you an idea if one of those hops is fubar.


(Lekdevil.NL) #3

A gap in the green lagometer graph means that during that interval, your client was not processing the updates from the server. This is usually caused by another program or driver taking all of your CPU’s resources during that time. I’ve also seen it happen when overclocking my videocard too much; the card would basically “hang” for short periods, causing the disruption. It is not something that’s caused by the connection to the server (or you would have seen a red spike).

Try closing all programs running in the background, checking your overclocking (if applicable), entering \pb_system 1 when not connected to the server (if not done already), using different/newer drivers, stuff like that.

HTH.


(Kendle) #4

Also, if it’s the client missing CPU cycles, and you’re running WinXP, try disabling the Indexing service, as this is a known resource hog and doesn’t get on very well with PunkBuster enabled games.


(McAfee) #5

A communications disruption can only mean one thing, Invasion!

Maybe you should update drivers, etc.
What are your system specs?


(Boeiend) #6

indexing services?
what are that

i also experience the gaps, but most of the times only at start of the game
after a few mins is ok tough


(Azarael) #7

The indexing server is one of the processes that windows xp and maybe 2000? use. You can see the description and find out whether it is runing by checking Administrative tools->services.


(=TAC=Chron) #8

ROFL!!

xp2200
1GB ddr266
xp home
fx 5200 ultra 128mb

not overclocked at all.
only 34 processes in the task manager…

i could just set ET for high priority in the task manager (hwere it should be anyway)

turned off indexing.


(L2|B4tt3rY) #9

how would i go about doing this and where etc, im a PC n00bie :clap:


(^POTATO) #10

Go into Help and Support and type in indexing, then click on the one saying using indexing service.


(=ABS= SparhawK) #11

xp2200
1GB ddr266
xp home
fx 5200 ultra 128mb

Well apart from the truly horrible video card, the drivers aren’t very good.

If you have the latest drivers from nvidia there are issues, roll back to 45.23 dets.

If you still have problems use current video card as a frisbee and buy an Nvidia Ti4200 or if directX9 is wanted an ati 9600.

SH