N4 multiplayer core.ini wierdness

Hadn't seen this mentioned yet (or missed it if it was), but I noticed that the following line was mis-configured in the communications section of my core.ini: net_use_mdm_bandwidth_for_tcp_ip=1 ; Use modem bandwidthfor TCP/IP Seemed to me that was implying that it was over-riding my LAN network settings in favor of the modem ones. Not sure why it was set that way, since all I did was do the 'find other connection methods' bit to have it detect that I was using a NIC to connect to my cable modem and not a dial-up modem. Anyway, changed that to a zero and cured my lag problems racing online. Was seeing about a 50% bar on lag and dropped that to the green/yellow borderline area and don't see it spike above about 15-20% or so now. Naturally that'll vary when connecting to a bandwith limited server, but everything was really smooth on the Papy Loop servers. Just wanted to throw that out there and see if anyone else had run into this also and see if anyone has come up with any optimized packet sizes other than the default like was eventually figured out for GPL. -John

I have been having a terrible time in N4 Mulitplayer with a cable modem hookup. Just last night while I was on I didnt have a single ping under 333 and had a high of...get this...2395! This has been an ongoing problem for me. Well I went to my core.ini like you said and mine said the same thing. I followed your directions and lo' and behold...VIOLA!! Went straight to N4 Multiplayer and of all the races posted, I only had three above 194 and bettter than three quarters of the races were at 111 or lower with a whole slew in the the 75 to 85 range. Thanks, I was going crazy trying to figure out why a rock solid VROC connect would go so bad in N4. Any one else with cable modem who has had problems. Try this fix. Mike

Mine was set to 1 also and my connection is dsl. Weird.... "John Harwood" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (26 lines)

> Hadn't seen this mentioned yet (or missed it if it was), but I noticed > that the following line was mis-configured in the communications > section of my core.ini: > > net_use_mdm_bandwidth_for_tcp_ip=1 ; Use modem > bandwidthfor TCP/IP > > Seemed to me that was implying that it was over-riding my LAN network > settings in favor of the modem ones. Not sure why it was set that > way, since all I did was do the 'find other connection methods' bit to > have it detect that I was using a NIC to connect to my cable modem and > not a dial-up modem. > > Anyway, changed that to a zero and cured my lag problems racing > online. Was seeing about a 50% bar on lag and dropped that to the > green/yellow borderline area and don't see it spike above about 15-20% > or so now. Naturally that'll vary when connecting to a bandwith > limited server, but everything was really smooth on the Papy Loop > servers. > > Just wanted to throw that out there and see if anyone else had run > into this also and see if anyone has come up with any optimized packet > sizes other than the default like was eventually figured out for GPL. > > -John >

Very glad that solved your problems as well, Mike! Now if we just knew why it's defaulting that way for some folks (I'd assume not for everyone or this would have come up already), that would be interesting, or if there is any additional tweaking to squeeze out a little more speed... :-) -Jon On 22 Feb 2001 21:19:13 GMT, [email hidden] (Race1530) wrote:

Quoted text (15 lines)

>I have been having a terrible time in N4 Mulitplayer with a cable modem hookup. > Just last night while I was on I didnt have a single ping under 333 and had a >high of...get this...2395! This has been an ongoing problem for me. > >Well I went to my core.ini like you said and mine said the same thing. I >followed your directions and lo' and behold...VIOLA!! >Went straight to N4 Multiplayer and of all the races posted, I only had three >above 194 and bettter than three quarters of the races were at 111 or lower >with a whole slew in the the 75 to 85 range. > >Thanks, I was going crazy trying to figure out why a rock solid VROC connect >would go so bad in N4. Any one else with cable modem who has had problems. >Try this fix. > >Mike

On Thu, 22 Feb 2001 22:15:00 GMT, "J Craig" <[email hidden]> wrote: >Mine was set to 1 also and my connection is dsl. Weird.... > Think we're beginning to see a pattern here... Wonder how many other folks had it set this way? I'm sure that throws the timing of a broadband connection all to hell, hence the lag. Very odd indeed... -John

It worked like that in GPL and no one had any problems with it. I have the "use_mdm_bandwidth_for_tcpip=1" setting and it works fine. Reducing the bandwidth requirements allows them to get 43 drivers on a server. Actually, in GPL we reduced it even farther to 2/84 settings instead of 3/84. I think that if everyone uses "=0", you'll find some of the smaller servers will get throttled due to the bandwidth requirements. Jason. John Harwood wrote:

Quoted text (12 lines)

> > On Thu, 22 Feb 2001 22:15:00 GMT, "J Craig" <[email hidden]> > wrote: > > >Mine was set to 1 also and my connection is dsl. Weird.... > > > > Think we're beginning to see a pattern here... Wonder how many other > folks had it set this way? I'm sure that throws the timing of a > broadband connection all to hell, hence the lag. Very odd indeed... > > -John

-- Jason Monds http://www.proracingclub.com - Pro Racing Club! (N3, GPL, Fun Run Sims) http://www.racersdomain.com - Race hosting. (Please remove 'no extra spork' when replying)