I've been running on Hawaii with a Prac. Peri. 14.4 up until a couple of
weeks ago. My latencies were anywhere from 0.10 to 0.16. I had been
experiencing what I considered too many disconnects while racing, so I
went out and purchased a USR Sportster 28.8 thinking that might solve the
problem. With the USR I've been getting fewer disconnects (only one on
port 0:5 Wed night). However, no matter what init string I use or baud
rate I try I get a slow connection message with a 0.25 latency upon
entering a track. This happens every time without fail with the same exact
latency. There doesn't seem to be a problem racing as I've been close to
others on numerous occassions with no adverse effects. I would say that the
value is incorrect, but when I connect locally with my brother we get
latencies of 0.06 to 0.10, so I am assuming that it is functioning. My
long distance carrier is MCI, and I'm calling from the Houston area. Any
ideas, guys???? I'm at a loss. Any and all help would be appreciated.
Thanks.
Mike Bruno
JMB55
Quoted text (19 lines)
>I've been running on Hawaii with a Prac. Peri. 14.4 up until a couple of >weeks ago. My latencies were anywhere from 0.10 to 0.16. I had been >experiencing what I considered too many disconnects while racing, so I >went out and purchased a USR Sportster 28.8 thinking that might solve the >problem. With the USR I've been getting fewer disconnects (only one on >port 0:5 Wed night). However, no matter what init string I use or baud >rate I try I get a slow connection message with a 0.25 latency upon >entering a track. This happens every time without fail with the same exact >latency. There doesn't seem to be a problem racing as I've been close to >others on numerous occassions with no adverse effects. I would say that >the >value is incorrect, but when I connect locally with my brother we get >latencies of 0.06 to 0.10, so I am assuming that it is functioning. My >long distance carrier is MCI, and I'm calling from the Houston area. Any >ideas, guys???? I'm at a loss. Any and all help would be appreciated. >Thanks. >Mike Bruno >JMB55while back. They said that the latency reported when you first get to the
track is NOT reliable. To see the true latency (from the track menu "replay,
garage" etc...) press T. This will take you to the chat screen, then press
CTRL-Y. Your latency along with some other data will be reported. You can do
this as often as you like.
They also recommended this init string "AT&F%C0\N0". Those are zeros.
Good Luck,
Mike Radler


































