rec.autos.simulators

I set the minimum latencey in core.ini for my open server to be 300, yet
when I view the server from home the max latency is set to (I think)
3000000, and when I look at the core.ini on the server its set it self back
to 300.0000.  Any ideas why ?.  Also, I've set the maximum latency in the
player.ini file, which value is actually meaning full, the player.ini or the
one in core.ini ?.

S.

--
Dougal: God, I've heard about those cults Ted. People dressing up in black
and saying Our Lord's going to come back and save us all.
Ted: No, Dougal, that's us. That's Catholicism.

I believe that for some reason or another the open server setting in your
core.ini uses seconds while the actual value displayed in game and the
player.ini setting both use milliseconds.  So to set a 300ms latency limit
for an open server you'd need to use 0.300 seconds in the core.ini.

- Eric

I think the player INI gets priority since that is the actual "host" when
running a dedicated server. All I can suggest is to make sure you are
setting it under the [Server] section and not the multiplayer host section
as those are 2 different apps and are addressed seperately in the INI files.
Dunno, the [Server] section is nearer the bottom than the MPlayer Host
section and the line should read "max_latency=300" and above it the
"latency_limit_enabled" should be set to 1 in the correct player file
associated with the server instance. Our player folder, for example, is
named "Server_Dedicated" since when I created it I named it "Dedicated
Server". It really does work, sounds like you may be editing the wrong
"player" file or something. OR it is not saving when you edit it. Make sure
the file is not read only.

Thanks for the help, should reduce the 'Philadelphia Experiment' - esque
starts that we've been experiencing recently !.

S.