The core.ini.sample that comes with the US version is quite different than
Alison's 1.1 version that I was using before. New stuff, and different
settings for the tings that seem to make a difference: 2/84/2/84, clock
adjust = 4; client and server packet frequency and size via memory?
No new info on VROC so far, so does anyone know?
--
Kevin Caldwell
Calgary, Canada
The clock_adj_delay line is not used with the new synch method...
Also add the following line under: [ Communications ] If you want
to see the bar graphs.
show_meters = 1
The rest of your Core.ini should remain the same...
Cheers,
Ron
Here's something I posted to a mailing list today on the topic:
Synch method 1 is the default for GPL 1.1 and 1.2, so strictly speaking,
this line can be omitted. Make sure you also uncheck the Use Old Synch
Method box in GSB or VROC.
This disables GPL's probing of the modem at startup. The modem is only
used by GPL for direct modem connections; ie if you want to have GPL
dial into another computer directly. It's not needed for Internet-based
racing, so disabling the modem makes GPL start up a little faster.
This is only needed if GPL can't find your IP address without it.
Usually people with analog connections don't need it, although some
people on AOL do need it. Cable modem users often need it.
In general, if you're racing through VROC/GSB, you don't need to worry
too much about core.ini settings, except for force feedback or other
special items. VROC and GSB set your core.ini settings for you. Even
the bandwidth on all clients is set to the value that is optimal for
most racing (84/3) unless the host chooses to allow your core.ini
settings to take over.
The core.ini file was essential with VROC 1/GSB 1/GPL 1.0 because it was
the only way to set bandwidth to values that allowed racing on the
Internet, and it was useful with GPL 1.1 because many people used it to
override the faulty Synch Method 1 in GPL 1.1.
Because of this history, I have the feeling that core.ini came to be
seen as a "magic bullet". This perception was strengthened in the early
days of GPL 1.1 because a core.ini was needed to address the problems
with SM 1 in GPL 1.1 by switching to SM 0. Later, the Use Old Synch
Method checkboxes were put into GSB and VROC, and it was no longer
necessary to use core.ini for this.
In GPL 1.2, with VROC 2/GSB 2, these concerns are no longer an issue.
By default, VROC and GSB automatically set the bandwidth for all clients
and servers, and for most people, SM 1 works far better than SM 0. The
few people who still seem to do better with SM 0 can still select SM 0
in GSB and VROC.
Bart Westra's core.ini files are excellent for perusing if you want to
understand the various things you can do with the parameters in
core.ini, but you don't need to slap in some core.ini file willy-nilly
just to race online.
Perhaps the most important thing to keep in mind is that if you are
racing outside of VROC/GSB, you'll want to set your bandwidth to a value
that will keep the data stream to a manageable size. We've found that
84/3 works best for racing if analog modems are involved.
It works best if the server and all clients use the same bandwidth
settings. That's why, by default, GSB and VROC automatically set all
clients to the server's bandwidth. You can tell what bandwidth settings
the host has specified in the Sever pane in GSB.
So essentially, except for specialty items like FF, alternate IP address
lookup, or replay memory override, if you're racing on VROC/GSB, a
core.ini isn't really critical or even necessary.
Alison
Remove the spam blocker NOSPAM to email me.
http://eaglewoman.maximumspeed.com
