> well i has to be said that this was discovered while macking the spotter for
> nazareth and mlwaukee. i have said before the easiest way to find the lentgh of
> the track is to edit the GFLAG value. this costs much time on testing and isnt
> very accurate.
> so i now found out the scale beetween real and sim.
> so if you have an 2.5 mi oval like indy the length of the track is 782
> and on an 1.00 mi oval like milwaukee its 313.
> so you can calculate each length you want. the last digit can change 1 up or
> down its not that accurate, just round the commas you get.
> happy editing!
> robert
> --
> <><><><><><><><><><><><><><><><><><><><>
> Robert Graf Racing
> Cole Trickle - Pepsi Pontiac #50
> <><><><><><><><><><><><><><><><><><><><>
The numbers you refer to are "not that accurate" su to the fact that
they are
just the most significant digits.
The unit in the track file is actually more like 1/500"
Therefore a 2.5 mile track would have a length of 79,200,000 units,
and a 1 mile track has a length of 31,680,000 units.
Now just like any REAL track the measurment of the track is not exactly
as listed in it's dimensions.
Example:
Talladega track in N2 measures out at 84,452,718 units.
This represents 2.6658 miles.
The N2 track length is stored in the taladega.dat file in the subfile
taladega.trk
as a long (32 bit) value at an offset of 8 within the subfile.
Related information:
In the replay files (*.rpl) only the most significant 24 bits of this
32 bit value
is reported for the linear position down the track so the replay has a
granularity
of 256/500" (this is the cause for some of the mis-reported speeds in
the replay
analyzers.)
Side Note: When playing via modem, the granularity is 32/500"