Lag on SourceOP - Printable Version

+- SourceOP (http://forums.sourceop.com)
+-- Forum: SourceOP Plugin (http://forums.sourceop.com/SourceOP-Plugin-forum)
+--- Forum: General Chat (http://forums.sourceop.com/General-Chat-forum)
+--- Thread: Lag on SourceOP (/Lag-on-SourceOP-thread)

---

Lag on SourceOP - Retribution - Apr 03, 2008

well that don't help much, i'm trying help the laggers on COD4 not lag anymore

---

Lag on SourceOP - avy - Apr 03, 2008

sorry... most people use google.

Go to command prompt and type in the following:

tracert anywebaddress.com or ip

There are also a few extra things that you can add to the string but for the most part you wont need them. (ie, max number of hops, timeout wait limit etc.)

---

Lag on SourceOP - Retribution - Apr 03, 2008

ok thaks i found the trace route, no how do you find packet loss?

---

Lag on SourceOP - avy - Apr 03, 2008

packet loss is generally reported using the ping command...

ping anywebaddress.com or ip

The results should show up generally along these lines:

Packet loss is reported in the results as a percentage. So if/when I ping I generally ping with 25 packets just to get a decent percentage.

As before, there are additional options on the ping command.

ping http://www.google.com -t would continually ping google until you interrupt the process.

ping http://www.google.com -n 7 would ping google 7 times.

ping http://www.google.com -l 1024 would ping google with packets 1024 bytes in size. Default is 32 if I remember right and 8192 is the max.

enjoy.

---