Note: the attached files are for use with Indy Car Racing II from Papyrus.  This 
program was originally designed for use with NASCAR Racing from Papyrus, but has
been altered to work with ICR2.  Since I don't know too much about ICR2 or Indy
Car racing in general you'll find that the documenatation files are still explained
using NASCAR terms and examples.

*********************************************************************************


The program EVENICR.EXE works just like the Program ICRRND.EXE except for the changes
outlined below.  To learn about ICRRND.EXE, please see the ICRDOC.TXT file.

I like to set up the power, traction and drag ranges in the DRIVERS2.TXT file so that the
cars don't all run in a bunch on the short tracks.  This seems to be more lifelike.  The 
problem is that if I use these same ranges for Talladega the cars don't run as close as 
they do in real life.  So, to bunch them up a little more, the ranges for all the cars need 
to be a little closer.

EVENICR.EXE has some code that will help you do this without maintaining two sets of 
DRIVERS2.TXT files.  The way it works is just like the ICRRND.EXE program except:

1) It will ask you if you want to even out the cars for a super speedway race - Y or N.
2) If the answer is 'N' no changes are made and the program runs just like ICRRND.EXE.
3) If the answer is 'Y', it then asks you for a range from 10 to 99.

This figure (10 - 99) represents the % the difference the cars settings will be narrowed by,
based on the average of all settings in the DRIVERS3.TXT file.  So, if you enter 60, each
car's variation from the average will be narrowed to 60% of its original amount.

Here's an example:

Initial settings in DRIVERS3.TXT -
Car 96 - Power: 300 600  Traction: 450 750  Drag:  25 200
Average- Power: 415 540  Traction: 415 540  Drag: 100 175
If you enter 25 when prompted for a range, the difference between the settings and the hard
coded averages for ALL cars, including yours, will be narrowed to 25% of what the variation
originally was.  The calculation for the low end of the power range is as follows:
415 - 300 = 115   115 *.25 = 28  415 - 28 = 387.  The 415 is the Power average of all cars 
from DRIVERS3.TXT and the 300  was the original value from DRIVERS3.TXT for that car.  The 
result was 387 that will be the new setting in DRIVERS2.TXT.  So, the variation was 115 from
the average, but now it is only 28 from the average.  28 is 25% of 115.  (The actual number
is 28.75, but this program truncates the the decimal to make it an integer).

The final result of all numbers for this driver will be: 387 546 418 561  92 177.

If you had entered a value of 50, the result would be:   357 570 432 645  62 187
Compare this to the original values:                     300 600 450 750  25 200
And compare this to the average of all cars:             415 540 415 540 100 175

So, the lower the value you enter at the prompt, the closer all the cars will be brought 
toward the average and the closer they should perform in the race.

4) If the answer is 'Y' to the aggression question,then you are asked what the lowest
   setting should be (100 - 999) is acceptable.

Here's an example of this.  If a car's aggression settings are 250 and 600, and you say
the lowest value you want is 700 it'll use the following formula to compute the new
settings: 1000 - 700 = 300 -> 300/1000 = .3 -> 250 * .3 =  75 -> 700 +  75 = 775.
          1000 - 700 = 300 -> 300/1000 = .3 -> 600 * .3 = 180 -> 700 + 180 = 880.
So, the new settings will be 775 and 880 for that car.  Each car is computed individually.

I tried this out at Talladega using 900 as the lowest setting.  It still wasn't close to
realistic, but the AI cars did pass a lot more.  In fact, I came through turn 4 slow and an
AI car went on the outside of me through the tri-oval.  I was sure he'd lift, AI cars always
do, but he didn't.  I was pleased as punch right up until we smacked the wall.  I did notice
a lot more yellow flags in that race so I figure they fight it out with each other more too.


A drawback to using this program vs. the ICRRND.EXE is that it prompts you every time you 
run it.  So, if you want it to run at bootup you'll have to baby-sit the computer to input 
the prompts.

One more item of note is that before this evening out process happens, any adjustments that 
you set up to made at random (see ICRDOC.TXT will have been made.  So, if Dale Earnhardt 
was going to have a bad day set up wise, he still will.  He'll just run a little closer to
the crowd than he otherwise would have.

Hope it works out for you.

"Dependent people don't make independent decisions."