Project Reality Forums

hi

ive been wondering if there is any kind of netgraph, lagometer in bf2. all i know about is the fps counter, shown by entering "renderer.drawfps 1" in the console. (what is the 2nd number of that one anyways?).

ive always had a pretty bad hitreg in bf2 and mods. lately i found out that its not only because of the bf2 engine (but ofc partly), because ive had pretty bad hitreg in cod4 mp from time to time. now im wondering if my provider (the most worthless provider in austria, im gonna change soon anyways) or anything else (modem etc) might have packet loss.

PS: though this has been discussed several times, does anyone know any other ways of improving hitreg? beside the ahk script "hitregfixer/tweaker"...

thanks and regards,
skull

Skull wrote:ive been wondering if there is any kind of netgraph, lagometer in bf2. all i know about is the fps counter, shown by entering "renderer.drawfps 1" in the console. (what is the 2nd number of that one anyways?).

The 2nd number in BF2's built-in FPS display is time between rendered frames in milliseconds. Practially, it's the result of the equation 1000/FPS.

Skull wrote:now im wondering if my provider (the most worthless provider in austria, im gonna change soon anyways) or anything else (modem etc) might have packet loss.

Packet loss can be verified using tools like ping plotter and similar. But it's important to note that router's main task is to relay payload, not to answer ICMP (a.k.a. ping) requests. Many routers have limitations on how many ICMP responses they send in second, which may lead to situation where it seems to lose packets even the valuable traffic is flowing fine.

According to my very limited experience, the most common problem with consumer internet connections lies within the last mile. The connection speed may be too high for the quality of the cables, which causes all kinds of instabilites.

Hitreg is hitreg unfortunately, aside from the settings the fixer tweaks, there is no way to improve or otherwise fix it. The upside to that is that everyone else is playing with the same broken hit system you are.

You can use a pingtest to check your packet loss without using the windows command prompt one, like clueless said, it's really only good for making sure you have a connection, not the quality of that connection. Do it a few times, get a feel for it etc.

Good luck.

some people like to blame deviation on "hitreg"


I have never had a problem with lag, and I'm using the crappiest cable you can get. You just have to be good.