NR2003 INI FILES

new

Admin Administrator Posts: 293	NR2003 INI FILES Aug 16, 2017 18:19:13 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Admin on Aug 16, 2017 18:19:13 GMT Anything INI , research and development.

holeshot
Junior Member

Career Honda motorcycle tech, state drag race championship builder, world land speed record builder.

Posts: 60

NR2003 INI FILES Aug 17, 2017 3:36:22 GMT

Quote

Post by holeshot on Aug 17, 2017 3:36:22 GMT

The track.ini file: Adjusting the ai:

NR2003.exe runs the show. *
papy_ai.ini defines the parameters for a host of operations. *
race.lp tells ai the path to run.
NR2003.exe interprets info from the recorded race.lp lap, then imparts driving instructions to ai. **
The rest of the lp's allow and/or restrict where ai vary from the race.lp. ** track.ini defines track properties & allows fine tuning of some ai properties as they relate to the specific track conditions & race.lp. **
[ track ] & [ ai_track ] are for "cup", [ track_(series) ] & [ ai_track_(series) ] are for the series or mod designated
[ track ] & [ track_(series) ] are for the player & ai, [ ai_track ] & [ ai_track_(series) ] are for the ai only
The ai ratings determine how well an ai can implement the properties of the track. *

* affects all tracks
** affects one specific track

Tracks less than 1/2 mile: ai work flawlessly at some & marginally at others. Pitting/pitroad errors/penalties are prevalent.

ai are inherently bad/out of control:
1. ai weren't developed for this track specifically
a) the race.lp doesn't reflect a real racing line
b) the race.lp wasn't driven in a manner that allows the exe to translate it properly to the ai, i.e. uneven/erratic throttle, oversteering & sliding
c) there are no secondary lp's (min/maxrace, min/maxpanic) or they are copies of, minrace=minpanic and maxrace=maxpanic
d) one or more of the secondary lp's are on the wrong side of the race.lp (misnamed)
e) there is only a pit0.lp, and minpit0 and maxpit0 are copies of pit0 (note: pit lp's MUST run through the pits)
f) the track.ini was copied from another track & no adjs were made to properties of the track or lp's
g) In the track.ini, any line and value that is in <[ track ]> and <[ ai_track ]>, the "cup" sections, will automatically be applied to every series in the track.ini, unless other series section has the same line and it's own value. If you want different attributes for each series, add each "cup" track.ini line to each series and apply the appropiate value.
h) the track.ini doesn't contain sections developed for the series (exe) you're running, (The ai will use the cup sections of the track.ini if the specific series sections are not in the track.ini, and the ai will use the fast.cup.sim setup if there is no fast.(series exe).sim setup available.)
i) using a modified papy_ai.ini

ai wreck a lot:
1. ai_wall_offset = 20; at 100 there's full, instantaneous ai to ai contact; at anything less than 100 there is some morphing (increasing as you get to zero where the ai can drive through each other with no contact) so it gets progressively harder to make serious contact. I find 20 looks like normal contact when it occurs, but reduces (not eliminates) incidents.
2. ai_drafting_distance = 1.07 and/or ai_dlat_pad = 0.7; average cup values; pta and gtp can use slightly lower values; increase these values in 0.05 increments, but if you get to 1.85 and 0.85 and the trouble continues, the problem lies elsewhere.
3. ai ratings; higher maximum ratings in the "drivers" section, especially "track type" ability. On tracks that exhibit a lot of close racing (short tracks, plate tracks), if an ai has a minimum rating of 50 or less for Vehicle/Chassis, Driver/Track-type, Driver/Consistency, an ai will have a good chance of initiating a collision.
4. minrace/maxrace lp's; needs wider spacing from the race.lp and/or wider spacing between the two min/max lp's
5. minpanic/maxpanic lp's; needs wider spacing from the min/maxrace.lp's
6. using a modified papy_ai.ini

Special consideration for "Plate" tracks (or a track where you (and ai) drive flat out, i.e. you never lift the throttle for a corner):
1. ai_wall_offset = 8 - 20; at 8 there is some visible morphing, maybe a fender width or a little more. I didn't find less than 8 to significantly yield any less accidents to justify the morphing.
2. ai_drafting_distance = 1.10 - 1.5 and/or ai_dlat_pad = 0.85 - 1.5
The higher the value for either line will reduce the ai's ability to pass. You can never completely eliminate accidents unless you want to have a "follow the leader" scenario.
a) Start with lower values. Run a race. If accidents subsided, stop there or lower values to encourage passing.
b) Work with the ai_dlat_pad value next. Increase the value in 0.10 increments. If you achieve results with a value 1.5 or less, stop.
c) Next, work with ai_drafting_distance. Increase in 0.10 increments. If you can achieve results with a value 1.5 or less, stop.
d) Further increases will adversely affect the ai's ability to achieve any passing. If you continue, confine increases to ai_dlat_pad. Higher ai_dlat_pad vals with wider minrace & maxrace lp's spacing (& min/max panic lp's, to stay beyond the min/maxrace lp's).
e) ai ratings determine how well ai can implement properties of each track. If ai has minimum Vehicle/Chassis rating less than 60 &/or a Driver/Track-type rating less than 60, this ai will have a good chance of initiating a collision at least once during EVERY race when the exe has randomly selected a ratings value below 60. Almost absolute certainty for tracks that exhibit "pack-racing", such as plate tracks.

ai don't wreck enough: A track with well done lp's and track.ini will normally have less incidents. Plate tracks, or similar "flat out" tracks, will have more due close proximity, nose to tail & side by side.
1. Reduce ai ratings. If only minimum value is reduced, ai will be more prone to lesser ability ( or bad driving) when random selection favors the low end of the ratings. If random selection favors the high end, the ai will wreck less. Lowering min & max values should increase chance of collisions. Use lower ratings in these categories: 1) Vehicle/ Chassis, 2) Driver/ Track type (ability), 3) Driver/ Consistency. Try a value of 45 or less as a minimum value.
2. [ ai_track ] (or [ ai_track_(series) ] ai_wall_offset = 100, 100 = full-contact AI collision detection
3. Decrease [ ai_track ] (or [ ai_track_(series) ] ai_drafting_distance
4. Decrease [ ai_track ] (or [ ai_track_(series) ] ai_dlat_pad
5. Increase [ ai_track ] (or [ ai_track_(series) ] ai_squeeze_pcnt. Increase judiciously, 0.05 increments (or less).

ai never wreck when hit:
1. ai_inverse_slipcurve_k ; reduce until ai break loose as easily when you bump them as you get loose when they bump you; has added benefit that ai won't have a superior cornering ability over you.

ai spin out for no reason:
1. ai_inverse_slipcurve_k = too low
2. less than optimal fast.(series).sim setup
3. Mismatched race.lp line
4. When it occurs just before or along the pits, bad track.ini value(s) as it relates to pitting. May be related to bad pit lp's, alone or in conjunction with track.ini.
5. Seldom the problem, but_ bad track segment, track section, x section

ai rollover:
1. Track grip level too high (track_asphalt_grip, track_concrete_grip, track_paint_grip, etc.)
2. Curb too high or too steep of an angle
3. Combination of #1 & #2

ai jumping cars:
1. When ai are placed on a track, they are "dropped" onto a designated location, either pitstall or starting grid. When more than one car (including the player) is designated to occupy the same location, those car(s) will pop, explode, fly off when the second car is "dropped" onto the occupied space. Check track.ini for like or similar (within 3m) pitstall or starting grid locations & rectify with new values.
2. Track grip level too high (track_asphalt_grip, track_concrete_grip, track_paint_grip)
3. Combination of high grip level & anomaly of the track. There's a work-a-round, but it's time consuming to achieve and the raceability is marginal.

ai don't pass enough:
Passing (on any track) is hard to do if cars have equal ability, even top rated cars take several laps to get by. If a top car can't get past a backmarker in less than 2 laps, you've got issues.
1. verify that ai have decent ratings for all track types.
2. ai_drafting_distance = 1.07 &/or ai_dlat_pad = 0.7 (average starting points), decreasing will help passing (possibly incurring more collisions, use <ai_wall_offset = 20-30> for less incidents).
3. ai_squeeze_pcnt = 0.05 - 0.30 (could be poor lp's, this is easier to try first); Starting range, too high (above 1.5- 2.0) causes the ai to wander aimlessly, especially off the track. If raising to 0.30 doesn't show significant results, go for new lp's.
4. minrace/maxrace lp's; min/maxrace lp's that encompass legitimate secondary racing lines; to help avoid incidents, min/maxpanic lp's that allow escape lanes, especially where the preferred racing lines are narrow or converge to a preferred narrower racing line (e.g. the transition from a wide straight to a corner or esses).
5. ai_panic_decel = 7.5; too high a value could cause early checkup by the car behind, even when there's no problem ahead).
More extreme:
6. If #2 & #4 have been implemented with less than desired results, try ai_squeeze_pcnt = > 0.30
7. ai_line_modifier = 1.01-1.05; increasing this line tells ai they have more grip than they actually do, allows them to go faster than what the exe says is the ideal speed for the actual grip available. Increasing this makes ai racier & quicker through corners, lower laptimes, so to maintain the same laptimes the <ai_grip_modifier> or opponent strength will have to be lowered as well.

ai don't pass where I want them to:
1. new minrace and maxrace lp's
2. all the solutions for "ai don't pass enough"

ai pass too much:
Do the opposite of "ai don't pass enough", & narrow the distance between race.lp & minrace & maxrace lp's.

ai don't run where I want them to:
1. make new lp's [min lp is always on the right (relative to the race.lp or pit0.lp), max lp is always on the left; the direction of track, CW or CCW, has no bearing]
Place the location of lp's to allow ai to run where you want, and to restrict ai from running where you don't.
a) ai run on the race.lp 99% of the time *; you need, at least, a different race.lp.
b) to pass, ai run up to, and as far out as the wheels will remain in contact with the minrace and maxrace lp's **
c) under duress or crowding, ai will run out to the minpanic & maxpanic lp's ***
d) at least two pit lp's are needed to have ai as error free as possible on pitroad; the minpit0.lp or maxpit0.lp (whichever is closer to the pitstalls) should be a lane close to the pitstalls (i.e. within one car width), the pit0.lp should be 1 to 1 1/2 car widths from that; while on the pitroad where the pitstalls are, the ai rarely (if ever) use the pit lp closest to the track, however, they may use that pit lp when leaving the racing surface for the pits or re-entering the track from the pits.
e) Use track.ini to control when ai must follow the pit lp's; [ pit_lane_0 ]merge_from_pit_line_dlong, merge_to_pit_line_dlong, merge_to_pit_line_length, lane_merge_dlong
f) during the pace lap, the two lines of ai follow the minrace.lp and the maxrace.lp, most of the time. However, when the maxrace.lp (for example) is close to the race.lp and the minrace.lp is not, the pacing line will follow the maxrace.lp and the minrace.lp pacing line will move toward the race.lp.

* There's always a preferred racing line on a track. Since NR2003 doesn't allow for changing track conditions (why not?, mod?), that line will always be the same. As far as ai are concerned, the preferred/optimal racing line is race.lp, ai will follow that line unless overriding instructions allow them to vary from it. The overriding instructions can be from the track.ini, lp's, or ai ratings.
There are a couple of exceptions:
1) When the exe determines the speed & grip are at a tenable level, ai will shorten the distance between point A & B even if race.lp swings wide, & if race.lp pinches the angle, ai will swing a little wider to maintain speed. +>
+> Exception for "Plate" tracks (or a track where you & ai drive flat out): Heres exception #1. The exe determines that the speed & grip are acceptable for a more direct path than race.lp, so ai will tend to stay on the most direct route through the corner, which is the maxrace.lp (on CCW oval), especially if there are other ai around & on race.lp. There's always that overriding rule to follow the race.lp, so as soon as there's enough clearance, ai will tend to go back to the race.lp as the track straightens.
2) When the track centerline is not actually in contact with the racing surface, the ai can be pulled toward (or repelled from) the track centerline as far as the minrace.lp or maxrace.lp (depending on the location of track centerline and the direction of travel, CW or CCW) will allow.
** Excluding "rim-riding" (not easy, impossible), there are really only two bonafide "secondary" racing lines. One on or outside of the preferred line & drive a little deeper into the corner & use a late apex & a corner exit below or up to the preferred line. The other would be on or inside of the preferred line & take the corner with an early apex & a corner exit back out to or beyond the preferred line. Having minrace & maxrace lp's wider than one lane beyond these alternate racing lines is unnecessary, & decrease the distance of the inside mxxrace.lp (maxrace on CCW oval) from the race.lp as they approach a corner to lessen the two cars into one space syndrome.
*** Wider minpanic & maxpanic lp's will handle the "running out of room" problem, until you get to a corner. The ai rarely use this space, only for "panic" situations when braking space is insufficient & for accident avoidance. However, guard against making them too much wider than the min/maxrace as they approach a corner because they eventually are going to rejoin the racing line and you don't want them crowding in at the corner entry. On the inside line of the corner, the panic line should be a half car width or less from the mxxrace.lp (maxrace on CCW oval) line.

I want ai passing on the inside, passing on the outside, etc.
Single file: The action you want is not the action the track creator was looking for, ai will (more or less) always follow the race.lp unless they are looking to pass. Passing on the outside, i.e. the outside line is the dominate line, isn't impossible. For ai the fastest way around an oval is on a racing line as close as possible to the inside of the track. ai will try to run this line anytime the location of the lp's will allow it, regardless of grip level. It doesn't matter how much greater the grip level of the outside line is, ai will use the inside line if the lp's will allow it. On a track with an inside line grip level of 0.80 (a grip level the Player will perceive as ice) & an outsine line grip level of 3.50 (a grip level the Player will perceive as being on a rail), ai will "choose" the inside line if the lp's will allow it. The reason ai will "choose" an 0.80 grip level over a 3.5 grip level is because ai & Player operate with a different physic's model. In simulation mode (without Driver's Aids), Player is constrained to real world physics, ai are held in check by the exe. ai are designed to stay on track & go foward. They don't drift, at maximum lateral G's they simply become unglued & usually slide off the track surface. They sometimes re-aquire grip, but at a big loss to momentum before regaining speed.

ai speed... too fast, too slow:
ai's speed is determined by race.lp, track.ini, & ai ratings. ai's speed does not vary from a particular mod or carset model when the exe is cup, gns, cts, or pta. Modified exe's (aka illegal exe's) will yield different results, the Gen6 model will perform the same as the original cup model, but the cars using owr05 will perform differently than the cars using owr07 (pta.exe) while using the same race.lp, track.ini, & ai ratings. You dial in ai laptimes via track.ini line:
[ ai_track ] or [ ai_track_(series) ]
ai_grip_modifier; Adjust this value to control the ai's laptimes. Decrease the value to increase the ai's laptime, adjust to 4 decimal places. You'll want to verify/adjust: ai_accel_modifier
ai_drag_modifier
before the final
ai_grip_modifier
val.
ai_drag_modifier; Only adjust this value when the ai have a different top speed (in non-drafting situation) than player on the longest straight, it is not the parm used to slow or speed up the ai's laptime. Increase val to reduce ai's top speed. While you're checking ai's top speed, check their acceleration. Verify/adjust before modifying ai_drag_modifier. Take a mph reading at a particular spot a fair distance from a corner but before they reach top speed & compare that to your speed at that point. The ai's speed may be 1-2 mph faster than yours & still be okay.
ai_accel_modifier ; Only adjust when ai accelerate faster or slower than Player, its not the parameter used to slow or speed up ai's laptime. Increase val to have ai accelerate faster. This is for acceleration from corners & does not have significant effect on starts/restarts. Verify/adjust this val b4 modifying ai_drag_modifier.

ai qualifying:
An assumption to the fact an adjustment is needed, the ai are running laptimes within the range of the Player. The Player needs to adjust the "Computer Opponents / Strength %" before determining that the ai are too fast or too slow.
[ ai_track ] or [ ai_track_(series) ] ai_qual_modifier = 1.00 1.00 should yield a qualifying result that is +/- the best laptime an ai is capable of running with no draft assistance. A value greater than 1.00 will lower the laptime, a value less than 1.00 will increase the laptime. "ai_qual_modifier" is fairly sensitive to change, try modifying in 0.01-0.05 increments.

On ovals, a special qualifying setup may be employed by the Player that actually produces a faster laptime than is readily attained with a race setup. A value greater than 1.00 is usually called for.
On RC's the setup is compromised for many track variables and a qualifying setup is usually nothing more than slightly increased tire pressures and a tick less wing. A qualifying laptime is quite often higher than a racing lap, so a value less than 1.00 is more likely needed.

ai run into the back of me:
1. You say ai "rear end" you in braking zone. Do you "rear end" ai in the braking zone? Get ai to slow at the same rate as you. They should start braking at about the same time, but usually they'll start a tick or two later. With the same priority as hitting the brakes, you want them to get off the brakes & roll the corner at roughly the same place. Adjust ai_decel_modifier value (raising the value reduces the time the ai are braking) and get it to where you're not having to brake before you want to (not including the stack ups on the first couple of laps). That's as good as it gets by only adjusting track.ini.
3. At some tracks with a long fast straight leading to a relatively slow corner, ai brake in a shorter distance than the player. If you adjust the ai_decel_modifier for that long straight-corner, you'll be running into the back of ai at every other corner. Adjust ai_decel_modifier for the rest of the track, then you'll have to modify the ptf(?) to help on the long straight-corner. Create a track section(s) that about covers the braking zone, but end just short of the turn in point. Assign a track surface different than the normal racing surface. If the racing surface is "asphalt" (the ptf designation, not the mip visual), make the braking zone "concrete", or vice versa. Whatever the racing surface grip value is, add 0.05 to that for the braking surface value. You can also use paint for the braking surface, but a slightly higher value will be needed, probably 0.10 higher than the racing surface. The player will be able to begin braking a little later and slow at a faster rate than before, but ai will show negligible, if any, improvement.
4. NOT A SOLUTION: ai_dlongpad_scale.
The given definition: This pads the braking of the AI so that they don't suddenly stop when going into a turn or trying to pit. The smaller the number, the more scaling that takes place. With a value above 0.30, the ai will brake more &/or sooner than race.lp would indicate. With less than 0.30, no effect. I use 0.30. If you try & use this line to control the long fast straight leading to a relatively slow corner problem, you'll be running into the back of ai at every other corner.

At some tracks with a very long fast straight leading to a relatively slow corner (Lemans Sarthe, for instance, at the end of Mulsanne straight). If there is enough of a gap between ai at the corner & ai approaching the corner, the approaching ai will not see the cars ahead and will begin braking at the normal, clear track distance, and run into you and/or other ai as if you weren't there. The best you can do is use a higher ai_panic_decel value, a higher ai_squeeze_pcnt, & generously wide minpanic & maxpanic lp's & hope ai see the traffic soon enough and take avoidance action. You can also use ai_wall_offset = 0.00, but I find total morphing objectionable.
"Wiggling" the race.lp on the approach to the corner reduces/eliminates the consequences of this "blindness".

ai cars just blindly pile into a wreck:
There are two different scenarios to consider, (re)actions that can be helped & (re)actions that can't be overcome, not completely.
1. Things that can be done:
a) ai_panic_decel = 5 - 20 ; ai react sooner & with more intensity to cars ahead, ai will slow &/or change lanes. Too high can cause early checkup by the car behind, even when there's no problem ahead.
b) ai_squeeze_pcnt = 0.05 - 0.50 ; ai_squeeze_pcnt allows ai to deviate from the ususal constraints of Race.lp. Any value > 0.00 can be detrimental to racing, cause ai to take alternate line even when there is no viable passing opportunity available. Too high causes ai to wander aimlessly, even off the track.
2. When the "pile up" essentially blocks the racing surface, there's not much of a chance of avoiding the "piling on" effect, especially when ai are in a pack. Then you have the situation where the ai blindly pile into a wreck that has occurred "well in front" of them. This seemingly "blind to the cars ahead" scenario is a re-occurring problem on tracks where there is a long top speed straight leading into a very slow corner. The ai have no trouble slowing properly for the corner by themselves or in a pack, i.e. ai begin braking soon enough & reduce speed effectively to navigate the turn. ai behind approach the corner as if there are NO cars in front of them & brake for the corner using "normal", un-obstructed track braking procedure. As if the ai ahead are not recognized as being there, ai ram right into the traffic ahead because they did not start slowing soon enough. "Wiggling" the race.lp on the approach to the corner reduces/eliminates the consequences of this "blindness".)

ai slow/checkup entering the corner:
The reason:
1) A poorly made race.lp is the usual cause.
There was an unnecessary throttle lift during the lp creation.
There is a wiggle or misalignment in the race.lp.
The lp location is less than optimal for negotiating the corner.
The lp location tracks on a surface designation that has a reduced grip value or the ai_inverse_slipcurve_k value is too low.
2) Too high an ai_dlongpad_scale value is the other cause. ai_dlongpad_scale = 0.3 is the only value I use. While the definition of the properties of this parameter, "This pads the braking of the AI so that they don't suddenly stop when going into a turn or trying to pit. The smaller the number, the more scaling that takes place", "pad" and "scaling" is not defined. The common belief seems to be that a high value is beneficial, but the greater the value the more the ai is likely to checkup. I have not found any practical use for a high value (there are other ways to get the ai to slow up if necessary).
ai_dlongpad_scale = 0.03 keeps the ai from checking up unnecessarily, and a lower value doesn't appear to have an additional effect.
3) Too low a value for ai_decel_modifier, especially if combined with a ai_dlongpad_scale value greater than 0.30.

"I make LP's to make the AI run my style...", "Now I... want... to make the AI run more realistic":
You may have competing wishes, your style vs. realistic ai. Realistic ai would mirror real racing, and the object of racing is to get around the track as quickly as possible. Your racing line or style may not be the quickest way around. Only when you're knowledgeable about racing lines, braking, throttle control, and optimal setups, can you begin to run the quickest laps. Once the "best" racing line is established, the race.lp, you then determine the secondary racing lines, the line inside and/or outside of the preferred racing line. Once you have determined these secondary racing lines you create the minrace and maxrace lp's which will restrain the ai to these extreme inside or outside boundaries. Your style may vary. You can either continue running "your style" or adapt to a possibly faster line and/or driving style. The shortest way around any oval, the inside line, is the fastest way. This is a fact in the real world and in NR2003. However, there is a problem inherent in the properties of NR2003. In the real world, certain track/car conditions may yield a faster lap when running a higher racing line. In NR2003, with a track configured to have better grip in a higher line, the Player may run faster on that higher line than they can on a lower line. Suffice to say ai don't run with the same properties as the Player. ai are enhanced to stay in control, so they can maintain car control with less grip than the Player. If they are allowed (by the lp placement) to hug the inside line, they will, and therefore be faster than a higher line with superior grip. On a superspeedway (or any track where there is no throttle lift) the outside line will never dominate. On non-SS tracks this is still mostly the case, but with extremely low grip values (unrealistic for the Player's use) on the inside line, the higher line may be faster. However, the ai will still try to run the inside line when it's deemed okay by the exe, they will become loose, lose momentum, and eventually return to the higher line, not very realistic.

ai crash entering the pits:
1. make new pit lp's
2. adjust the track.ini values to control when the ai must follow the pit lp's; [ pit_lane_0 ]merge_from_pit_line_dlong, merge_to_pit_line_dlong, merge_to_pit_line_length, lane_merge_dlong
3. In the track.ini, use slower pit speed limit, [ pit_lane_0 ] speed_limit_MPH = xx

ai crash exiting the pits:
1. make new pit lp's
2. adjust the track.ini values to control when the ai must follow the pit lp's; [ pit_lane_0 ]merge_from_pit_line_dlong, merge_to_pit_line_dlong, merge_to_pit_line_length, lane_merge_dlong
3. In the track.ini, use slower pit speed limit, [ pit_lane_0 ] speed_limit_MPH = xx

pit penalties entering:
1. Incorrect [ AppRuleEnterPits ] values in the track.ini
a) apply correct values
b) deleting this section of the track.ini should remove any pit entry penalties
2. adjust the track.ini values to control when the ai must follow the pit lp's; [ pit_lane_0 ] merge_to_pit_line_dlong, merge_to_pit_line_length

pit penalties exiting:
1. adjust the track.ini values to control when the ai must follow the pit lp's; [ pit_lane_0 ] merge_from_pit_line_dlong (must be at least as far down the track as lane_merge_dlong), lane_merge_dlong (ai must stay on "apron" subsurface until this distance is reached), deleting this line will remove the pit exit penalty

pit penalties speeding:
1. pit speed must be maintained from just before the first pitstall on pitroad to just after the last pitstall on pitroad. (deleting [ pit_lane_0 ] speed_limit_MPH in the track.ini will remove pit speeding penalties)
2. Sometimes the construction of the track skews the dlong values. By noting where ai slow to pit speed, and then viewing the dlong values in the ptf (opened in sandbox), by trial & error adjust the location of the start of pitroad by placing a line, cone, etc., to mark the correct location for the player.
3. Due to the construction method, tracks shorter than 1/2 mile may exhibit pit speed application and verification anomalies which cannot be corrected.

ai pit under caution on 1st lap:
Ai pitting under caution after only one lap is a NR2003 shortcoming. There is really nothing that can be done to overcome it.
The ai pitting strategy takes a lot of trial and error just to get ai to pit in a window commensurate with the Player.
Trying to get ai to pit differently for cautions is even more difficult and not all cars will conform even then. Plus, it tends to screw up regular pitting strategies.
Trying to get ai to buck the game's tendencies when it comes to pitting under caution is an exercise in futility.

ai cars_game won't load the full roster:
1) On the "Single Race" page, be sure you have selected a roster with enough cars, "Computer Opponents/Roster:" .
2) On the "Single Race" page, be sure you have selected the quantity of cars desired, "Computer Opponents/Number:" .
NR2003 will only allow the quantity of ai cars per the track.ini, [ track ] max_starters = XX (minus one for the Player).
3) On the initial "Nascar Racing Page", select "Opponent Manager". Select a Roster. Be sure "Total Drivers" and "Active" (drivers) contain the required number of cars. NR2003 will only load one car per number. If there are cars with duplicate car #'s, go to the section on the right, Driver/#, change the car number so each car has a number not assigned to any other car. The number may be up to three digits.

how do you do a standing start:
Standing start method, NORMAL:
1_
Apply track.ini changes to <[ starting_grid_0 ]> (full pace). This leaves one pace lap in a normal configuration. ai appear to start a normal pace lap, but as the pace car crosses half track distance, the green flag order is given. There's a very short lag (less than 1 second) before ai take off racing, but the player can just mash it as soon as you see the ai move.
WARNING: The NR2003.exe considers the polesitter to be on the inside of the track and does not allow passing on the inside before the S/F line. On a CW track, the inside is the right side, on a CCW track, the inside is the left side. If you are in the pole-side line, you cannot pass any car in your line on the "inside" (as described), but you can pass anyone in the other line on the "inside". If you are in the other line, you cannot pass anyone on the "inside" (as described).

2_
The pace car cannot start beyond the half way point from the S/F line. One meter less than half usually works.
<stall_pace = xxx.00(half distance - 1) x.00 x.00>
I've never had the field catch the pace car on the track using realistic (normal) pace speeds on a RC track up to 6 miles long.
3_
[ ai_track ]
pace_merge_to_pit_line_dlong = xxx.00 Arbitrarily, 100 meters less than half.
I never had a problem with this value being farther down the track until Monaco F1. Having a value less than half track length commits the pace car to "pit in" when it starts, so it releases the field to a start condition (I guess).
4_
<[ starting_grid_0 ]> or <[ starting_grid_1 ]>
<stall_0 = xxx.00 x.00 0.00>
<stall_1 = xxx.00 x.00 0.00>
etc.
Align grid close to the S/F line. Allow a 8 - 10 meter clearance from the S/F line as a cushion so no ai cross the S/F line before the green flag flies.

Standing start method, INSTANTANEOUS:
1_
Apply track.ini changes to <[ track ]> <starter_decision = XX00 XX01>. Add an arbitrary value, say 1500, to the actual track length and use the new value as the "starter_decision".
The ai race (and spotter yells green flag) as soon as the pace car starts. The ai still do that twist turn as they start, so you only advantage to this method is the fraction of a second it takes to actually see (or hear from the spotter) a green flag.
The drawback to this method is you lose the option to have a different (full or short) pace lap.
WARNING: The NR2003.exe considers the polesitter to be on the inside of the track and does not allow passing on the inside before the S/F line. On a CW track, the inside is the right side, on a CCW track, the inside is the left side. If you are in the pole-side line, you cannot pass any car in your line on the "inside" (as described), but you can pass anyone in the other line on the "inside". If you are in the other line, you cannot pass anyone on the "inside" (as described).

2_ same as NORMAL
3_ same as NORMAL
4_ You can have the starting grid anywhere you want (with either version), but you can't pass on the "inside" until the S/F line, and you don't want the ai to catch the pace car before it gets to pit road because they'll slow to stay behind the pace car.

pace.lp:
There is no such lp recognized by the exe in NR2003. The pace car uses the pit0.lp (or pit1.lp). Furthermore, the pit0.lp is not speed (nor steering, nor throttle, nor braking) sensitive during the reflap process. In other words, it doesn't matter how its driven, 100mph or at a crawl, only that you lay down at least a lap (as for all the lp's), drive through the pits, and that the ends are pretty close in line when you save it.

ai path on pace lap and yellows:
As mentioned elsewhere, during the pace lap, the two lines of ai follow the minrace.lp and the maxrace.lp, more or less. It depends on how far apart the minrace.lp and maxrace.lp are, and the location of the race.lp. The ai will usually track on the m__race.lp that's closest to the race.lp, and the other line will be 4m - 8m away. If the minrace.lp and maxrace.lp aren't there, both lines will try and occupy the race.lp. If the minrace and the maxrace lp's are named incorrectly, i.e. the minrace is on the left and the maxrace is on the right, after the pace lap begins, the ai will start swapping to the opposite sides of the track (and creating mayhem) in order to follow the correct lp (that's now on the other side of the race.lp). Also, misnamed (misplaced) min/maxrace lp's generally cause the ai to stay anchored to the race.lp.

ai_pacing_distance & ai_bunching_distance:
If the ai ai_pacing_distance and ai_bunching_distance have the same value, the ai will start the race pretty even and ready to race. When the two lines use different values and a full 43 car field, and the ai_bunching_distance is a greater value than the ai_pacing_distance, the ai will still be trying to get to bunching distance when the green flag flies unless there's a pretty long straight before the S/F line.

The end

Last Edit: Aug 17, 2017 3:38:21 GMT by holeshot

(8^{|)

holeshot
Junior Member

Career Honda motorcycle tech, state drag race championship builder, world land speed record builder.

Posts: 60

NR2003 INI FILES Aug 17, 2017 3:40:52 GMT

Quote

Post by holeshot on Aug 17, 2017 3:40:52 GMT

Track.ini keys

Track.ini is a text file with track-specific parameters. There are 200 + - parameters that can be changed.

Tutorial: www.nrtracks.com/nr2k3/make_ai_adjustments.html

[ track ]
track_name = MICHIGAN INTERNATIONAL SPEEDWAY
track_name_short = Michigan
track_city = Brooklyn
track_state = MI
track_length_n_type = 2-mile D-shaped Oval
track_misc_info_1 = Turns banked 18∞
track_misc_info_2 = Frontstretch 2,229 feet banked 12∞
track_misc_info_3 = Backstretch 2,242 feet banked 5∞
track_num_turns = 4
track_length = 2.000m
track_altitude = 0.0
track_type = 3 ; long oval
; Normally tracks are designated like this.
; 0 = short track
; 1 = mile oval
; 2 = medium oval
; 3 = long oval
; 4 = super speedway
; 5 = road course

chassis_type = 2 ; speedway
; Chassis types:
; 1 = super speedway
; 2 = speedway
; 3 = short track
; 4 = road course
; 5 = superspeedway, no restrictor plate.

default_event_laps = 200
default_qual_laps = 2
track_base_month = 6
; month has major effect on race-day weather, if realistic weather is used.

max_starters = 43
; Should be same as number of pit stalls (see the section [pit_lane_0] below).

track_tire_heat = 0.86 ; > modifies amount of heat going into the tire at a given track
track_tire_wear = 0.88 ; > 1.0 means more wear, i.e. 2.0 is twice normal wear, 0.5 is half normal wear
; Needs adjustment from time to time.
; For example, reduce the value, if track has been recently repaved.

track_tire_wear_loss = 0.24 ; percentage of grip lost at full tire wear
; what % grip is lost if tires are totally worn out.
; Affects both human player and computer opponents.

track_tire_wear_exp = 1.15 ; > 1.0 bigger fall off late run < 1.0 bigger fall off early run

track_asphalt_grip = 0.93 ; > 1.0 = more grip. Shouldn't have to chg more than +- 0.05

track_concrete_grip = 1.00 ; >
; Concrete surface type might have been used by track creator for the second groove.
; Indistinguishable from asphalt surface on the track unless MADE white

track_north_angle = 350 ;

; Starter decisions:
; 1st val is earliest poss grn flag dlong, should be after pace car pit entry point
; 2nd val is latest poss grn flag dlong. Must be b4 start line, after 1st val
starter_decision = 2900.00 3100.00

; [track_gns]
; [track_cts]
; [track_pta]
; [track_irc]
; [track_gtp]

; [track_arca]

[AppRuleCutCourse]
qual_only=1 ; only enforce checkpoints during qualifying session

[ configuration_0 ]
; Format: dlong, start dlat, end dlat, time penalty (sec), 0 (required)
; 2 checkpoint minimum
checkpoint_0 = 2890.00 -4.00 21.50 0 0 ; prevents cutting grass (qual only)
checkpoint_1 = 3170.00 -4.00 21.50 0 0

[ cup ]
record_lap_time = 37.667
record_holder = Dale Earnhardt, Jr.
; These are shown in lower left part of screen after track is loaded.
; [ gns ]
; [ cts ]

[ weather ]
track_base_temp = 66.7 ; track average temperature on April 1 in deg F
track_temp_range = 4.5 ; one standard deviation from average in deg F
track_temp_swing = 20.0 ; This is temp difference between July and April
track_wind_speed = 8.1 ; average wind speed at the track in MPH
track_wind_speed_range = 5.0 ; one standard deviation from average in MPH
track_wind_direction = 270 ; compass heading in degrees from which wind is most likely (in this case from Northwest)
track_cloud_prob = 0.65 ; probability of cloud cover, 0.0 to 1.0
; I have done some testing on these weather parameters and how the NR2003 uses them.
; track_base_temp is mid temperature of the year (half way between January and July).
; The actual temperature during the race is dependent of the track_base_month value set above.
; track_temp_range is used to calculate random fluctuation of temp on given day.
; So, the track_temp_range should be the value of 1 standard deviation from normal day-to-day temp variation between different years.
; My two experiments with weather settings
; EXPERIMENT 1. The effect of track_base_month
; SETTINGS: track_base_temp=45, track_temp_range=0, track_temp_swing=35
; RESULTS: track_base_month: temp for race-day in NR2003
; 1: 10 ; lowest value = track_base_temp - track_temp_swing
; 2: 15
; 3: 27
; 4: 45 ; mid-point value = track_base_temp
; 5: 62
; 6: 75
; 7: 80 ; highest value = track_base_temp + track_temp_swing
; 8: 75
; 9: 63
; 10: 45 ; mid-point value = track_base_temp
; 11: 28
; 12: 15

[CrowdSound]
num_sources = 4
pos_0 = -233 333 4
pos_1 = -216 333 5
pos_2 = 155 -394 2
pos_3 = -41 -396 1

[ ai_track ]
pace_merge_from_pit_line_dlong = 400.000
pace_merge_to_pit_line_dlong = 2725.0000
pace_speed_limit_mph = 65

ai_accel_modifier = 1.20 ; acceleration grip efficiency
; Decrease this value if you cannot accelerate as fast as AI cars on the straight.

ai_decel_modifier = 0.88 ; braking grip efficiency
; Decrease this value if the AI cars slam into you in breaking zone.ai_fuel_use = 0.96 ; > 1.0 = ai_grip_modifier = 1.06 ; > 1.0 = more grip ai_drag_modifier = 1.05 ; > 1.0 = more drag, which is slower ; I set both grip and drag always to 1.00. ; This makes the AI cars behave similarly with human player (same curve speed , same top speed on straight).; If needed, straight line speed can be modified by changing ai_accel_modifier above.ai_line_modifier = 1.00 ; dangerous hack, don't use unless you are a trained professionalai_qual_modifier = 1.000 ; > 1.0 = faster during qualifyingai_wall_offset = 100 ; 100 = full-time AI collision detection

ai_tire_wear_left = 0.39
ai_tire_wear_right = 0.48
; Tire wear needs to be reduced if AI cars slow down significantly after few laps.

ai_arcade_tire_wear = 1.01 ; (used in addition to the above left/right modifiers)
ai_arcade_fuel_use = 0.97 ; > 1.0 = more fuel consumed (used in addition to fuel_use above)
ai_arcade_grip_modifier = 0.9
ai_arcade_drag_modifier = 1.189
strategy_lap_time_wear_loss = 3.618
; Decrease if AI cars are pitting too frequently for tires.

strategy_lap_time_fuel_use_gain = 0.270 ;
strategy_base_pitting_cost = 29.228 ; time lost to a stop & go pitstop
ai_pacing_distance = 1.9 ; car
ai_bunching_distance = 1.75 ; car
ai_drafting_distance = 1.3 ; car
ai_panic_decel = 2.8 ; G's of extra deceleration inducing panic
ai_dlongpad_scale = 8.0 ; scales padding in braking zones (smaller = more scaling)
ai_dlat_pad = 1.1 ;
ai_squeeze_pcnt = 0.0
ai_inverse_slipcurve_k = 0.68 ; slip angle AI need to corner. smaller = increased drag, affects how easily the AI start sliding.
[ AppRuleEnterPits ]
pit0_entrance_point0_dlat = 77.98
pit0_entrance_point0_dlong = 2960.03
pit0_entrance_point1_dlat = 62.11
pit0_entrance_point1_dlong = 2962.04

[ pit_lane_0 ]
; AI stuff
merge_from_pit_line_dlong = 1350.0 ; dlong at which cars leaving pits merge to race line
merge_to_pit_line_dlong = 2000.0 ; dlong at which cars entering pits merge to pit line
merge_to_pit_line_length = 460.0 ; length of merge window
pit_lane_end_dlong = 269.4 ; dlong where pit lane proper ends
pit_lane_start_dlong = 2962.0 ; dlong where pit lane proper begins
slow_pit_line_dlat_offset = 5.0 ; track-specific dlat_offset of 2nd slower pit line (0 if N/A)
stall_exit_goal_dlat_offset = -5.0 ; goal dlat offset (+ left) for the pit stall exit cubic line
stall_exit_goal_dlong_offset = 7.0 ; goal dlong offset (ahead) for the pit stall exit cubic line
begin_stall_entry_offset = 21.0 ; offset at which to begin entering the pit stall
begin_stall_approach_offset = 100.0 ; offset at which to begin approaching the pit stall
lane_merge_dlong = 1268.00 ; Dlong which you must remain on the apron when exiting the pits

; race control stuff
lane_on_right = 0 ; 0 if on left, 1 if on right
lane_has_wall = 1 ; 0 no wall, 1 has wall
speed_limit_MPH = 55.0

; pace car
begin_pacestall_entry_offset = 20.0 ; offset at which to begin entering the pit stall
begin_pacestall_approach_offset = 45.0 ; offset at which to begin approaching the pit stall
pacestall_exit_goal_dlong_offset = 8.0 ; goal dlong offset (ahead) for the pit stall exit
pacestall_exit_goal_dlat_offset = -3.0 ; goal dlat offset for the pit stall exit
stall_pace = 277.83 70.24 -0.25

; special stalls
stall_qual_exit = 265.00 73.02 -0.25
; regular stalls
stall_0 = 265.00 73.02 -0.25
stall_1 = 253.35 75.73 -0.24
stall_2 = 241.63 78.33 -0.23
stall_3 = 229.86 80.81 -0.22
stall_4 = 218.02 83.16 -0.21
stall_5 = 206.13 85.39 -0.20
stall_6 = 194.19 87.49 -0.18
stall_7 = 182.19 89.47 -0.17
stall_8 = 170.15 91.32 -0.16
stall_9 = 158.06 93.05 -0.15
stall_10 = 145.93 94.64 -0.14
stall_11 = 133.76 96.11 -0.13
stall_12 = 121.55 97.46 -0.12
stall_13 = 109.31 98.67 -0.10
stall_14 = 97.04 99.76 -0.09
stall_15 = 84.75 100.71 -0.08
stall_16 = 72.43 101.54 -0.07
stall_17 = 60.09 102.23 -0.06
stall_18 = 47.74 102.80 -0.04
stall_19 = 35.37 103.23 -0.03
stall_20 = 23.00 103.52 -0.02
stall_21 = 10.61 103.69 -0.01
stall_22 = 3214.37 103.73 0.00
stall_23 = 3201.96 103.63 0.01
stall_24 = 3189.56 103.41 0.03
stall_25 = 3177.17 103.05 0.04
stall_26 = 3164.79 102.55 0.05
stall_27 = 3152.42 101.92 0.06
stall_28 = 3140.07 101.16 0.07
stall_29 = 3127.75 100.26 0.09
stall_30 = 3115.45 99.24 0.10
stall_31 = 3103.17 98.08 0.11
stall_32 = 3090.93 96.78 0.12
stall_33 = 3078.73 95.36 0.13
stall_34 = 3066.56 93.81 0.15
stall_35 = 3054.44 92.13 0.16
stall_36 = 3042.36 90.31 0.17
stall_37 = 3030.33 88.37 0.18
stall_38 = 3018.35 86.30 0.19
stall_39 = 3006.43 84.11 0.20
stall_40 = 2994.56 81.79 0.22
stall_41 = 2982.75 79.34 0.23
stall_42 = 2971.00 76.77 0.24

[ starting_grid_0 ]
; 2x2 unstaggered grid
; polesitter on left
stall_pace = 273.48 64.45 -0.25
stall_0 = 265.00 68.91 -0.25
stall_1 = 265.00 63.91 -0.25
stall_2 = 256.79 70.86 -0.25
stall_3 = 256.79 65.86 -0.25
stall_4 = 248.55 72.76 -0.24
stall_5 = 248.55 67.76 -0.24
stall_6 = 240.28 74.62 -0.23
stall_7 = 240.28 69.62 -0.23
stall_8 = 231.98 76.42 -0.22
stall_9 = 231.98 71.42 -0.22
stall_10 = 223.64 78.15 -0.21
stall_11 = 223.64 73.15 -0.21
stall_12 = 215.27 79.78 -0.20
stall_13 = 215.27 74.78 -0.20
stall_14 = 206.87 81.31 -0.19
stall_15 = 206.87 76.31 -0.19
stall_16 = 198.43 82.76 -0.18
stall_17 = 198.43 77.76 -0.18
stall_18 = 189.97 84.14 -0.17
stall_19 = 189.97 79.14 -0.17
stall_20 = 181.50 85.50 -0.17
stall_21 = 181.50 80.50 -0.17
stall_22 = 173.00 86.84 -0.17
stall_23 = 173.00 81.84 -0.17
stall_24 = 164.49 88.12 -0.16
stall_25 = 164.49 83.12 -0.16
stall_26 = 155.95 89.32 -0.15
stall_27 = 155.95 84.32 -0.15
stall_28 = 147.39 90.44 -0.14
stall_29 = 147.39 85.44 -0.14
stall_30 = 138.81 91.49 -0.13
stall_31 = 138.81 86.49 -0.13
stall_32 = 130.21 92.53 -0.13
stall_33 = 130.21 87.53 -0.13
stall_34 = 121.61 93.52 -0.12
stall_35 = 121.61 88.52 -0.12
stall_36 = 112.98 94.44 -0.11
stall_37 = 112.98 89.44 -0.11
stall_38 = 104.33 95.27 -0.10
stall_39 = 104.33 90.27 -0.10
stall_40 = 95.67 96.03 -0.09
stall_41 = 95.67 91.03 -0.09
stall_42 = 87.00 96.74 -0.09

[ starting_grid_1 ]
stall_pace = 1758.48 1.96 0.00
stall_0 = 1750.00 3.96 -0.00
stall_1 = 1750.00 -0.04 -0.00
stall_2 = 1741.52 4.01 -0.01
stall_3 = 1741.52 0.01 -0.01
stall_4 = 1733.05 4.09 -0.01
stall_5 = 1733.05 0.09 -0.01
stall_6 = 1724.57 4.19 -0.01
stall_7 = 1724.57 0.19 -0.01
stall_8 = 1716.10 4.25 -0.00
stall_9 = 1716.10 0.25 -0.00
stall_10 = 1707.62 4.27 0.00
stall_11 = 1707.62 0.27 0.00
stall_12 = 1699.14 4.26 -0.00
stall_13 = 1699.14 0.26 -0.00
stall_14 = 1690.67 4.28 -0.00
stall_15 = 1690.67 0.28 -0.00
stall_16 = 1682.19 4.31 -0.00
stall_17 = 1682.19 0.31 -0.00
stall_18 = 1673.71 4.31 0.00
stall_19 = 1673.71 0.31 0.00
stall_20 = 1665.24 4.30 0.00
stall_21 = 1665.24 0.30 0.00
stall_22 = 1656.76 4.29 0.00
stall_23 = 1656.76 0.29 0.00
stall_24 = 1648.29 4.26 0.01
stall_25 = 1648.29 0.26 0.01
stall_26 = 1639.81 4.22 0.00
stall_27 = 1639.81 0.22 0.00
stall_28 = 1631.33 4.21 -0.00
stall_29 = 1631.33 0.21 -0.00
stall_30 = 1622.86 4.25 -0.00
stall_31 = 1622.86 0.25 -0.00
stall_32 = 1614.38 4.26 0.00
stall_33 = 1614.38 0.26 0.00
stall_34 = 1605.90 4.22 0.01
stall_35 = 1605.90 0.22 0.01
stall_36 = 1597.43 4.13 0.01
stall_37 = 1597.43 0.13 0.01
stall_38 = 1588.95 4.05 0.01
stall_39 = 1588.95 0.05 0.01
stall_40 = 1580.48 4.03 -0.00
stall_41 = 1580.48 0.03 -0.00
stall_42 = 1572.00 4.04 -0.00

[ SPCC ]
num_named_sections = 6
name_0 = 456.00 842.00 T1
name_1 = 842.00 1260.00 T2
name_2 = 1260.00 1967.00 BSTR
name_3 = 1967.00 2367.00 T3
name_4 = 2367.00 2747.00 T4
name_5 = 2747.00 456.00 FSTC

(8^{|)

holeshot
Junior Member

Career Honda motorcycle tech, state drag race championship builder, world land speed record builder.

Posts: 60

NR2003 INI FILES Aug 17, 2017 3:44:55 GMT

Quote

Post by holeshot on Aug 17, 2017 3:44:55 GMT

The cars: (this data compiled from external sources, not verfied by Tester_05)

Including chassis 0, & plus all four physics, 24 unique cars. Extra HP during certain weather conditions is hard-coded into EXE.

Chassis:
0 = mystery car, huge tq & drag.
1 = superspeedway w/restrictor plate.
2 = speedway.
3 = short track.
4 = road course.
5 = superspeedway w/o restrictor plate
***********************************************
TEST SPECS: Talladega, clear skies, 70 degrees, no wind. Top speeds in MPH, drag number rounded to nearest second.

TEST DATA:
Chassis 0 - High drag coefficient of .82 vs .53, huge torque, top speed 192. Psi 42 all around, tires never wear unless pits set 4x & slam brakes. Idle: 800 RPM, other chassis idle at 1000. Bad mileage. Same HP for all chassis.
Cup - 745 HP, top speed 189, 5 drag
GNS - 745 HP, top speed 187, 5 drag
CTS - 745 HP, top speed 180, 7 drag
PTA - 745 HP, top speed 192, 5 drag

Chassis 1 = superspeedway with restrictor plate; low drag, low HP, top speed around 185. Fixed spoiler, rear shocks & rear springs, left side track bar can't be higher than right. Psi at 28/48 at ovals, 48 all around at road courses, stable at high speeds, low grip at low speeds.
Cup - 370 HP, top speed 189, 9 drag
GNS - 342 HP, top speed 181, 9 drag
CTS - 550 HP, top speed 181, 6 drag
PTA - 625 HP, top speed 212, 7 drag

Chassis 2 = speedway; Medium drag, downforce on nose, rear feels light. Psi at 28/48 oval, 48/48 road course, stable but 'twitchy', sensitive steering.
Cup - 635 HP, top speed 208, 7 drag
GNS - 623 HP, top speed 206, 8 drag
CTS - 562 HP, top speed 186, 6 drag
PTA - 625 HP, top speed 210, 6 drag

Chassis 3 = short track; Medium drag, even downforce, more side force. Psi at 22/34 oval, 34/34 road course, stable, easy to recover.
Cup - 637 HP, top speed 203, 7 drag
GNS - 622 HP, top speed 202, 7 drag
CTS - 562 HP, top speed 185, 6 drag
PTA - 625 HP, top speed 207, 6 drag

Chassis 4 = Road course; Medium drag, even downforce, more side force. Psi at 22/34 oval, 22/22 road course, stable, easy to recover.
Cup - 640 HP, top speed 204, 7 drag
GNS - 622 HP, top speed 203, 7 drag
CTS - 562 HP, top speed 185, 7 drag
PTA - 625 HP, top speed 207, 8 drag

Chassis 5 = superspeedway without plate; unrestricted. Low drag, stable at high speeds, low grip at low speeds. Psi 28/48 at oval, 48/48 road course, left side track bar can't be higher than right.
Cup - 706 HP, top speed 232, 11 drag
GNS - 622 HP, top speed 226, 11 drag
CTS - 574 HP, top speed 190, 7 drag
PTA - 625 HP, top speed 212, 6 drag

PTA car least effected by chassis #

Chassis 4 tires go yellow at 220 & red at 240, chassis 1/5 have to be at 240 to go yellow & 270 to go red.
***********************************************
Copy your setup to Fast.CTS.sim or whichever physics you are using & put it in track folder you are running so AI runs your setup. AI always use Fast.CTS.SIM, Fast.Cup.sim, Fast.Gtp.sim, set up in the track folder.
***********************************************
Tracks:
0 = short track
1 = mile oval
2 = medium oval (1~1-1/2 mile)
3 = long oval (2 mile)
4 = super speedway
5 = road course
***********************************************
NR5: Plate racing: “track type” to “4”, “chassis type” “0”. New tech specifications in Garage screen & none of your previous setups will work. You will need BullRing’s Gen6 mod, any Nationwide COT mod, & a 2014 CTS mod, all three physics sets are changed. You will also need relevant carsets & updated 2014 tracks. This download consists of the modified executable file (that’s literally all this mod is) & a few different car setups to get you started at a few different tracks. Put the setups in your Player folder & NR5.exe in main directory. Run NR5.exe. You’ll know if you did it right if you get a different splash screen.
***********************************************

(8^{|)

holeshot
Junior Member

Career Honda motorcycle tech, state drag race championship builder, world land speed record builder.

Posts: 60

NR2003 INI FILES Aug 17, 2017 4:20:55 GMT

Quote

Post by holeshot on Aug 17, 2017 4:20:55 GMT

The readme file nobody reads, I've rearranged it, valuable data to the top:

(There MAY be WAY more than papy tells us)
COMMAND LINE GAME .INI SETTINGS: The command line overrides will not be saved to the .INI file.

-ko”numeric_id:section_name:key_name:value”

…where…

numeric_id is the ID of the .INI file that contains the value to be overridden. The mapping is as follows:

0 = CORE.INI,
10 = APP.INI
20 = PLAYER.INI
40 = TRACK.INI
50 = ADDRESS.INI
(JJ - Find # for papy_ai.ini?)
(Where's #30?)

section_name is the name of the section within the .INI file in which the key exists. [PLAYER], for example. The brackets ([, and ]) should not be specified.

key_name is the name of the key, lastPlayer, for example.

To launch & automatically switch to one of multiple players, you would override the lastPlayer key in the [Player] section of APP.INI. If you had two players, John Smith & Fred Jones, you could create separate shortcuts to launch the game for each:

“C:\Papyrus\NASCAR Racing 2003 Season\NR2003.exe” -ko”10:player:lastPlayer:Smith__John”

“C:\Papyrus\NASCAR Racing 2003 Season\NR2003.exe” -ko”10:player:lastPlayer:Jones__Fred”

The first command line would launch NR2003 with the player John Smith. The second command line would NR2003 with the player Fred Jones.

<<< There ARE some car paint files that SLOW my screaming PC to 1-5 fps, not compressed?>>>
TEXTURE COMPRESSION IN THE PAINT SHOP: Paint Shop will save files using DXTC (DirectX Texture Compression). This reduces the texture memory requirements for the car textures by a nearly >>>4:1<<< margin, allowing more high detailed car textures to fit in the same amount of memory. If you would prefer that the Paint Shop not compress the car textures when they are saved, edit the save_textures_with_compression line in your PLAYER.INI, changing the 1 to a 0:

[Paintkit]
save_textures_with_compression=1 ; Enable texture compression on saved textures.

DRIVING CONTROLS KBRD SHORTCUTS:
ESC–ESC mnu (Use Arrows, ENTER to Navigate)
F1-F9 – Pit Service Controls (Use Arrows, SPACE to Navigate)
F1
F2
F3
F4
F5
F6
F7
F8
F9

PageUp & PageDown – Change Driving Views
PauseBreak – Pause Game
PrintScreen – Take Screen Shot
F – Toggle Framerate Counter
G – Toggle Gauges in Ext Driving Views
H – Display Keyboard Shortcuts
M – Toggle Mirror Detail Level
N – Toggle Car Interior Display in Mirror
O – Toggle Trackside Object Detail Level
S – Toggle Speed/Gear/Flag Indicator
V – Change Focus to Next Driver (Car must be stopped)
CTRL+V – Focus Back to Player Car
SHIFT+V – Change Focus to Previous Driver (Car must be stopped)
CTRL+I – Toggle Lap Info Messages
CTRL+L – Check Leader Position
SHIFT+R – Return to Pit
SHIFT+T – View/Reset Tach Telltale
F11 – votes yes (issues !yes chat command in response to multiplayer poll)
F12 – votes no (issues !no chat command in response to multiplayer poll)

REPLAY CONTROLS KBRD SHORTCUTS:
C – Change to Next Camera
V – Change Focus to Next Driver
CTRL+N – Unfocus CurrCam frm Driver
CTRL+V – Change Focus Back to Player
SHIFT+C – Change to Previous Camera
SHIFT+V – Chg Focus to Previous Driver
Keypad1 (END) – Fast Fwd to End
Keypad4 (Left Arrow) – Rewind
Keypad5 – Play/Pause
Keypad6 (Right Arrow) – Frame Advance
Keypad7 (Home) – Rewind to Start
Keypad8 – Slow Motion Mode
SHIFT+Keypad4 – Rewind
SHIFT+Keypad6 – Fast Forward
Keypad. (Del) – Switch to Live Feed Mode
S – Disp Stndngs (Full-screen rply only)
Space – Toggle On-screen Display of Replay Controls

(may not function properly if NumLock is enabled on your keyboard)

OpenGL renderer may not work on all cards and/or system configurations. Leaving the game’s “Show Intro/Exit Sequences” option enabled may help eliminate some initialization problems on subsequent game launches. If you continue to experience problems using the OpenGL renderer it is recommended that you instead use the game’s default DirectX renderer.

16-BIT VS. 32-BIT COLOR: Because of the large amount of textures used it is recommended that 32-bit color only be used on video cards with 64 MB or more texture memory. Even for 64 MB cards 16-bit color will likely result in significantly better performance.

TEXTURE MEMORY DETECTION: As part of the 3D Configuration test will attempt to detect the total amount of texture memory available. As you increase the video resolution more memory is required for the frame buffer resulting in less for textures. Manually edit the “TextureSetSize” value, in bytes, in REND_D3D.INI or REND_OGL.INI. Increasing this value above the detected value may prevent the game from dropping mip levels as more textures are loaded, but setting too large of a value may result in SIGNIFICANT performance hits as textures begin to swap in and out of memory.

ANISOTROPIC FILTERING: A problem with the way polygons are drawn is as you look at the polygon at low angles the texture tends to get very blurry. You can see this as the armco, fences, road surface & grass are usually at very low angles. Anisotropic filtering can help the texture look better at these low angles. If your video support this feature, you will be able to enable Anisotropic Filtering by selecting “Extreme” from the Texture Filtering Quality drop-down of on the game’s Graphics Options screen. The configuration test will detect the maximum levels of anisotropic filtering that your video card supports. This will be recorded in the “AnisotropicLevel” value in the game’s REND_D3D.INI or REND_OGL.INI. Valid values are powers of 2, where 1 or 0 = none, 2 = 1 level, 4 = 2 levels, 8 = 3 levels, 16 = 4 levels, etc. GeForce1 and Geforce2 cards can do 1 level of anisotropy (2^1=2) which is reported as “AnisotropicLevel=2”. GeForce3 cards can do 3 levels of anisotropy (2^3=8) which is reported as “AnisotropicLevel=8”. Setting this value too high is harmless.

MOUSE ISSUES: Animated mouse cursors can create cursor anomalies. If you encounter problems, restore your windows mouse cursor to its default settings. Some users may encounter problems using the hardware mouse cursor, it is recommended that you re-run the 3D Configuration Test and check the “Use Software Cursor” checkbox to use the game’s software mouse cursor instead.

< 3D sound CRASHES ALL of my PCs>
SOUND ISSUES: If you have no sound in the game, go to the Audio tab of Win Multimedia, select the proper playback device. You may also want to disable the “Use only preferred devices” option if enabled. There are a couple of CORE.INI variables which improve the quality of sound on some sound cards. The default values are as follows:

[Sound]
allow_buffer_recreation=1
enable_3d_interpolation=1
force_default_buffer_size=0

You can set allow_buffer_recreation to 0 to disable sound buffer re-creation, which may slightly improve performance at the cost of quality. When 3d sound is enabled, positions of newly played sounds take some time to reach their destination. This may result in sounds being played loudly for a brief moment, even though they *should* have a low volume given their distance from the listener. The enable_3d_interpolation setting can help to work around this problem. If a system properly (instantly) sets the 3d position of a sound, then this solution, when enabled, might make the sound seem to “fade-in”, so setting this to 0 would be called for in those systems. The force_default_buffer_size setting default sound buffer read-ahead size to a given value, defined in 1/36 second increments, which may help sound issues.

MS GAME VOICE OR OTHER VOICE CHAT PROGRAMS: NR2003 will run at highest priority. If you experience problems using MS Game Voice or other similar programs you may need to run at a lower priority by adding a “-kh0” (that’s dash K H Zero) command line parameter to the shortcut: “C:\Papyrus\NASCAR Racing 2003 Season\NR2003.exe” -kh0

DIRECTINPUT JOYSTICK DRVR: DirectInput joystick/wheel and you can’t calibrate it in game, exit the game & ensure that the device is properly set up and calibrated in the Win Game applet.

OPTIMIZED JOYSTICK DRIVER: NR2003 includes an optimized joystick driver, may provide more precise joystick input than can be obtained with DirectInput, but is only compatible with standard PC joysticks, joysticks which are designed for DirectInput, such as USB or ForceFeedback controllers, will not work with the Optimized driver.

KEYBOARD DRIVING CONTROLS: If you were to assign throttle to the B key, that you would not be able to type the letter [b/B] in a chat message while you were out driving. Each time you pressed the B key, you would engage the throttle. You can enable this feature in the Advanced Controller Options dialog on the game’s controls screen.

SPEED SENSITIVE STEERING: NR2003 uses speed-sensitive steering ratio such that at low speeds your steering ratio will be set to somewhere between 7:1 and the ratio defined in your car setup. You can disable this feature in the Advanced Controller Options dialog on the game’s controls screen.

CAR SETUPS: are stored in individual track directories located in “Papyrus\NASCAR Racing 2003 Season\Players\Player__Name\Setups”.

SCREENSHOTS: press the PrintScreen button on your keyboard to take a screenshot.

IMPORTING TGA IMAGES INTO THE REPLAY EDITOR: you will be able to import .BMP images into Replay Editor, if you wish to use .TGA files instead (useful as 32-bit .TGA files have an alpha channel which allows for translucency and transparency), you may edit the rpy_editor_bitmap_extension line in your CORE.INI, changing the ‘BMP’ extension to ‘TGA’ as shown below:

[Replay]
rpy_editor_bitmap_extension=tga ; bmp and tga are valid

IMPORTING SOUNDS INTO THE REPLAY EDITOR: Standard 22kHz .WAV and compressed .OGG files are supported for sound playback, default will only import WAV files. .OGG files (MP3-like compression), edit rpy_editor_sound_extension line in your CORE.INI, changing the ‘WAV’ extension to ‘OGG’ as shown below. More information on encoding .OGG files using the included OGGENC.EXE utility can be found on the OGG Vorbis website: www.vorbis.com/index.psp

[Replay]
rpy_editor_sound_extension=wav ; wav and ogg are valid

COMPUTER OPPONENTS SELECTION: If the number of active drivers in the roster exceeds the number of pit stalls, the list eligible computer opponents is weighted with preference given to those drivers with higher stats. Your current roster has 50 active drivers but you only elect to race against 20, the game will select the 20 ‘best’ computer opponents for you to race against.

There is some variance to this selection, exiting the race weekend and re-entering the same track may give a slightly different set of 20 computer opponents. If you want to ensure that you are racing against the same field for each and every race, be sure that the number of active drivers in the roster does not exceed the maximum number of selectable computer opponents on the race setup screens. In Championship races this same weighted selection of computer opponents occurs prior to each race. If there are more active drivers than the maximum number of selectable computer opponents, some drivers will not make the field for the races. Who makes the field and who doesn’t will be different for each race of the season, so even though you may only have 42 computer opponents selected on the Championship Season race setup screen you will likely see more than 43 drivers (42 selected computer opponents plus the player) listed in the Championship standings (up to the total number of active computer opponents in the roster). If you want to ensure that you are racing against the same field for every race, be sure that the number of active drivers in the roster does not exceed the maximum number of selectable computer opponents on the race setup screen.

CONTROLLING REPLAY MEMORY: NR2003 Season will try to use a much free memory as is available. To force a larger value for longer replays, or force it to a smaller value if performance is suffering, edit “replayMemoryOverride” value in [Replay] section of CORE.INI. This value is in KB, so for a 64MB replay buffer you would set this value to 65,536 (64MB x 1024KB/MB). When NR2003 is run as dedicated server a minimum 512KB of replay buffer is used to maximize performance & minimize the load on the server. To save replays from a dedicated server you will need to override this value.

OFF-LINE LEAGUE SUPPORT IN EXPORTED STANDINGS: enable a flag in PLAYER.INI…

[Misc]
off_line_league_info=0 ; Export extra info

Changing this to 1 will cause the additional information to be included in the exported standings. The following additional information will be exported…

(a) There will be an additional column, titled “TAG”, for each driver in the race standings. This tag is computed from the .CAR file used by that driver, and will change if that car is changed. When a league member submits exported standings, the TAG value for all of the drivers should match the TAG value for the ‘approved’ .CAR files.

(b) The AI Strength setting is now exported.

(c) The number, type and length of the weekend’s sessions are exported. For example, “2Q1LR50L” means the weekend had 2 sessions; Qualify for 1 Lap, then Race for 50 Laps.

(d) The options for the weekend are exported. This will be a string of characters with one character for each of the following options:
0/2/3 – Damage model (0=None, 2=Moderate, 3=Realistic)
Y/- – Yellow flags enabled/disabled
F/- – Fixed setup enabled/disabled
A/- – Driving model (A=Arcade, -=Simulation)
I/- – AI used? (I=yes, -=no)
S/- – Automatic AI speed control? (S=yes, -=no)
D/- – Double file restarts enabled? (D=yes, -=no)
H/- – Hardcore mode selected? (H=yes, -=no)
M/- – Mechanical player breakdowns? (M=yes, -=no)
L/- – Full pace lap enabled? (F=yes, -=no)
W/- – Realistic weather enabled? (W=yes, -=no)
1/2/3/4 – Pit stop frequency (1=1x, 2=2x, 3=3x, 4=4x)

Example: “0Y-AI-D-M-W2” means “damage model is set to None, yellow flags are enabled, fixed setup is disabled, the driving model is Arcade, AI are included, Automatic AI speed control is disabled, Double file restarts are enabled, Hardcore mode is not selected, player Mechanical failures are enabled, shortened pace lap is selected, realistic Weather is enabled, 2x pit stop frequency”. Note that not all of these options are applicable to single-player races.

(e) A signature value that is computed from the track geometry and the TRACK.INI file. If the league member has altered the track geometry, or has altered the TRACK.INI, this value will be different.

A utility program is included that allows a league administrator to verify that the exported standings file has not been edited. Place this program (VAILDATE.EXE) in a directory in your path, or copy it into the directory that contains the exported standings files you wish to verify. Run the program, giving it a command line parameter telling it what files should be validated. Example:
C:\Papyrus\NASCAR Racing 2003 Season\exports_imports> validate *.html
<test11.html> valid.
<test12.html> valid.
<test13.html> Invalid. File has been modified.
<test14.html> valid.

MULTIPLAYER ISSUES:
CONNECTING TO SIERRA.COM RACES:
If you are receiving “Connection Time-Out” messages when attempting to connect to Sierra.com multiplayer races or see no ping times displayed for any of these races you may need to select a different TCP/IP device in the “Connect Via:” drop-down list in the Sierra.com login box. Note that if you have a dynamic IP address it may first be necessary to enable the “Find Network Addresses Another Way” option using the CONFIGURE button at the bottom of the main multiplayer screen before the proper TCP/IP device will be listed.

MULTIPLAYER BEHIND A FIREWALL OR ROUTER: The following UDP ports will be used: 32766 for the net_server_port, 32767 for ping port, and then sequentially numbered ports for each allowed client connection (max of 42) starting at 32768.

To run from a machine with a private IP address behind a Linux firewall, you need to use a combination of IP masquerading and IP autoforwarding. The following rules for the default 42 client port range can be used:

ipfwadm -F -a accept -m -S a.a.a.a/m.m.m.m -D 0.0.0.0/0
ipautofw -A -r udp 32766 32809 -h a.a.a.a -v -u

Where a.a.a.a is the address of the machine behind the firewall, and m.m.m.m is the netmask. If you run a server behind the firewall, clients should connect to the IP address of the firewall.

Users with Linksys or other such Internet connection sharing routers should not need to change any configuration settings to connect as clients. To host a race from behind a router you will need to forward the default UDP port range of 32766-32809 from the router to the internal or LAN IP of the server. When connecting, clients should use the external or WAN IP address of the router.
If you have a router or firewall and would like to allow multiple users on your LAN to connect to the same multiplayer server, you will need to have each of the clients behind the router use a different net_server_port in their CORE.INI files (one client would make no changes and use the default port, while each of the others would need to specify a unique net_server_port). If you are hosting a server from behind the router by forwarding the default UDP port range to the LAN IP of the server, no clients on your LAN will be able to connect to multiplayer races since all of the incoming packets would be forwarded to your server. If you want to allow these clients to connect to races while your server is running, forward & configure the server to use a non-standard UDP port range (see below for details).

MULTIPLAYER TCP/IP CONFIGURATION:
If you connect to the Internet using a modem, and wish to play over the Internet, connect to the Internet before starting. If you do not intend to play over the Internet, there is no need to connect before playing the game. If you do not see a TCP/IP connection listed on the multiplayer screen, you must use the CONFIGURE button at the bottom of the Multiplayer screen and enable the alternate method of determining your machine’s IP address. You will need to restart the game for this setting to take effect. If you use this alternate method, and your only TCP/IP connection is via a modem, and you have your Internet properties set to automatically connect to the Internet, and you’re not connected to the Internet when you start, Dial-Up Networking will start up when you launch. This may cause NR2003 to not function properly, and/or your machine may connect to the Internet.

DISABLING USER CONNECTION AND DISCONNECTION MESSAGES: In multiplayer races you will receive chat messages when other players connect and disconnect. Disable them by editing the following line in your PLAYER.INI (located in your Players\Player__Name directory), changing the 1 to a 0:

[Misc]
showJoinLeave=1 ; Show player join/leave messages

DIRECT CONNECT ISSUES: A bug in the drivers for some graphics tablets can cause them to become corrupt when NR2003 looks for serial ports on your computer. Because of this potential problem, direct serial connections have been disabled by default. If you wish to enable direct connect serial port connections use the CONFIGURE button at the bottom of the Multiplayer screen. You will need to restart the game for this setting to take effect.

PRIVATE CHAT MESSAGES: You can issue private chat messages to any one of the players connected to the server. Begin your message with “/”, followed by the name of the player (or #car_number), followed by the message. For example:

/#12 Hey, John. What’s up?
/smith What’s up?
/j.smith What’s up?
/jo.smi What’s up?
/john.smith What’s up?

The message will only be sent to the person you identify (or you will be given an error message if the program couldn’t figure out who you meant). When received, whispered chat messages will appear in a different color font so as to be easily distinguished from normal chat messages.

USING MULTIPLAYER AUTOCHAT: In addition to typing in chat messages, you can define up to 10 autochat messages through the editor on the Player Info screen. These will be saved in the [Autochat Messages] section of your PLAYER.INI. While driving these are accessed by the 1 through 0 keys (not on the number pad). To have messages automatically sent, end them with a dollar sign “$” (i.e. Pass High$). All others will be queued up allowing you to add additional text onto the end of the message. These can then be sent by pressing ENTER like normal chat messages. Note that if you have in-car chat disabled in the Options menu you will be unable to send autochat messages.

MULTIPLAYER CAR SELECTION: NR2003 allows a single occurrence of a car number at a track, you will automatically be placed in another car number if you have chosen a car number that is already in use by another player who connected to the server before you.

ADDING AI OPPONENTS TO A MULTIPLAYER RACE: You may have up to 42 connections to a multiplayer server for both human & AI opponents. In order to allow the addition of AI opponents to the server, you must first reduce the number of allowed TCP/IP or IPX connections to less than 42 human opponents. Once this is done you will be able to fill out the field with AI opponents.

COMMUNICATION METERS: Game play is directly affected by the latency, reliability, and consistency of the connection between you and the game server, so it’s important that the program give you a good sense of these factors. NR2003 includes a graphical display that allows you to monitor the status of your communications with the server when you are a client. These meters can only be displayed while in the car, and can be toggled on/off by pressing CTRL+C. They are turned off by default.

The bar graphs are as follows:
(L) Instantaneous latency from 0.0 seconds (the bar is empty) to 1.0 seconds (the bar is full height). This is the amount of time that it takes for a message to go from the server, to your client, and back to the server.

(Q) Quality from 100% (the bar is empty) to 50% (the bar is full height). The more data that is lost or garbled during transmission from the server to you, the lower the quality of your connection, and the higher this bar will go.

(S) The time skew (difference) between your client and the server. If your current time is behind where you expect the server to be, this bar will be below center. If it is at the bottom, then you believe that you are 1.0 seconds (or more) behind the server. If your current time is ahead of where you expect the server to be, it will be above center. If it is at the top, then you believe that you are 1.0 seconds (or more) ahead of the server. If the bar reaches the top or bottom, then your client will re-synchronize itself with the server (it will smash its clock).

Ideally, no bars should be visible whatsoever. That is, you have 0.0 seconds of latency, 100% of data from the server is getting to you, and your client believes that it is at the same point in time as the server. In practice, this will not happen.

The (L)atency bar will almost always be visible since it is not possible for data to get from server to you instantaneously. The higher the latency, the longer it takes for data to get from the server to your computer, and so the older it is when it gets there. The older the data is, the more “predicting” your client has to do about the positions of other cars on the track. The more that it has to predict, the more likely that it will predict incorrectly, and the more the other cars will jump around when it realizes its error. It is not uncommon for the (Q)uality bar to be completely empty (indicating little or no data loss), but it is also not uncommon for a few percent of the data to be lost or garbled during transmission, showing as a small (Q)uality bar. If the bar starts to grow steadily, then something bad has happened on the route through the Internet between you and the server (or the server has crashed). If the route doesn’t clear up quickly, you will soon be disconnected. If it does clear up, there will probably be short period of mayhem as the route settles down, and old data that has been stuck in transit is flushed. If the latency is varying a bit, it can be difficult for your client to determine what point in time the server is currently at, and a small (S)kew bar is likely to appear. If the (S)kew bar grows continuously until it hits the top or bottom, your client will smash its clock to re-synchronize itself to the server. If it does this, then either the connection between you and the server is very poor, or either your machine or the server machine is extremely overloaded, and your client can no longer stay in step with the server.

EJECTING DRIVERS: Any admin or boss (remote or local) may remove a player from their server by using the “!eject” command. Ejected drivers will be able to reconnect once the server is reset or returns to the track select screen. The command should be entered as a chat message. The format of the command is “!eject player”, where player can either be the “#” symbol along with the player’s car number, or the players name. For example:

“!eject #12”
“!eject smith”
“!eject j.smith”
“!eject john.smith”

BANNING DRIVERS: Any admin (remote or local) may also ban a player from their server by using the “!ban” command. For non-Sierra.com races this will eject the driver from the race and prevent them from reconnecting until the server is reset. For Sierra.com races, the driver is ejected and automatically added to the server’s muzzle list which will prevent him from ever reconnecting. Again the command should be entered as a chat message. The format of the command is “!ban player”, where player can either be the “#” symbol along with the player’s car number, or the player’s name. For example:

“!ban #12”
“!ban smith”
“!ban j.smith”
“!ban john.smith”

VIEWING DETAILED SIERRA.COM RATINGS: You can view a detailed Sierra.com points history by clicking on a Sierra.com ID in the “PLAYERS”, “INVITE” or “MUZZLE” lists, hitting the “Profile” button, and then holding down the left-shift and left-control keys while the PROFILE dialog box is displayed. The number between () is your current rating at the track type, and the numbers between [] are your point totals for your last 9 races. The other numbers are RR=races run, RC=races completed, LA=laps available in those races, LC=laps completed, and IC=incident count. Your LPI (laps per incident) rating is LC divided by IC. Note that this “left-shift + left-control” trick also works on the Entry List tab of race weekend screen to display the current ratings of all the users connected to the race.

RATINGS UPDATE MESSAGE AFTER COMPLETION OF RACE: After the server has completed its ratings updates, clients still connected to the server will receive a system chat message informing them of the ratings outcome of the completed race. The message is of the form…

Incidents(i), Points(p): New Rating(r), Average(a). Up@(u) Down@(d)

This means that you were assessed (i) incidents, and received a total of (p) points for this race. The word New will only appear if your rating changed as a result of this race. You now-current rating (r) is given, and your current average skill points (after dropping the two lowest) is shown as (a). (u) and (d) show the average point levels at which your rating will increase or decrease. Also, you will be informed if ratings were disabled for the race, or if there were too few drivers or the race was too short to qualify for ratings updates.

THE POLLING AND VOTE SYSTEM:
Multiplayer servers now have the option of allowing any connected user to call a poll to allowing them to vote on certain admin commands. Only one poll is allowed at a time. A ‘yes’ vote is automatically entered for the person initiating a poll. All other users can vote on the poll using chat commands “!YES” or “!NO”. Only those users who were connected to the server at the time the poll was initiated are allowed to vote. At the completion of the vote’s timer any non-votes are counted as no votes, and the final outcome is broadcast to all users. To prevent hogging the polling system, a user is not allowed to initiate a new poll for a short time after having conducted a poll. The poll is entered as a chat message “!poll pole_type player” where player can either be the “#” symbol along with the player’s car number, or the player’s name. The chat command “!list_polls” will return a complete list of available polls. For example:

!poll eject player [<comment>]
!poll yellow [<comment>]
!poll black player [<comment>]
!poll clear player [<comment>]
!poll lap+ player [<comment>]
!poll lap- player [<comment>]
!poll track track_name

Two new driving controls have been added to quickly vote YES or NO in response to a poll. Note that these hotkeys are only available while driving in-car:

F11 – votes yes (issues !yes chat command)
F12 – votes no (issues !no chat command)

DISABLING THE CHAT FILTER: The game will filter all incoming chat for offensive language. You may choose to disable this feature by editing the following line in your PLAYER.INI, changing the 0 to a 1. Note that this will have no effect on your outgoing chat messages seen by other users, only the chat that you see displayed on your system.

[Misc]
disable_chat_filter=0 ; Disable chat filter

(8^{|)

holeshot
Junior Member

Career Honda motorcycle tech, state drag race championship builder, world land speed record builder.

Posts: 60

NR2003 INI FILES Aug 17, 2017 18:32:47 GMT

Quote

Post by holeshot on Aug 17, 2017 18:32:47 GMT

GrandPrixLegends is worth looking at, same publisher...

gpl_ai.ini

; *************************************

; MAIN AI PARAMETERS

; *************************************

[ behavior ]

attempt_outbrake_dlong_sep = 12.410400 ; max. dlong sep for attempting to outbrake car ahead (at designated waypoint)

auto_blocker_line_speed_pct = 0.74 ; % of race line speed below which car should automatically be considered a potential blocker

base_gearshift_hiatus = 0.010000 ; base time (in ticks) engine is disengaged for a gear shift

base_race_start_hiatus = 18.0000 ; base time (in ticks) of driver reaction at start of race

being_squeezed_speed_coeff = 0.85000 ; value adjusts dlong speed goal if being squeezed

crashing_recovery_alt = 0.600000 ; altitude threshold below which will attempt recovery from crashing mode

crashing_recovery_pitch_roll = 0.980000 ; safe pitch/roll velocity v. surface normal cosine for recovery from crashing mode

crashing_recovery_slip_angle = 0.349 ; slip angle threshold (~ 20 degrees)below which will attempt recovery from crashing mode

crashing_recovery_yaw_velocity = 0.050000 ; yaw vel. threshold below which will attempt recovery from crashing mode

dlong_speed_dropoff_coeff = 0.000000 ; value * (line yaw vel.)^2 * (dlat offset from line)^2 = line speed adj.

long_term_avoid_time_coeff = 0.80 ; adjusts avoid_time_coeff for long term decision making

long_term_check_min_speed = 0.620400 ; min. dlong speed in ms./tick for doing long term decision making

loss_of_control_coeff = 1.200000 ; adjusts parameters that determine whether loss of control has occurred

loss_of_control_speed_adj_scaling = 0.20 ; scaling factor for loss of control adjustment based on speed relative to 75 MPH

low_speed_override_threshold = 0.434280 ; dlong speed below which misc. low speed overrides will kick in.

max_practice_pit_wait = 360.000000 ; max. time in SECONDS car will wait in pit after reentering pit during practice

min_cornering_outside_pass_radius = 400.000000 ; min. radius in meters for which outside pass attempt in turn permitted

min_dlat_sep_back = 2.7000 ; distance in meters

min_dlat_sep_front = 2.70000 ; distance in meters

min_dlong_sep_back = 5.025240 ; distance in meters

min_practice_pit_wait = 180.000000 ; min. time in SECONDS car will wait in pit after reentering pit during practice

min_speed_dropoff_coeff = 0.750000 ; min. coeff for dlong_speed_dropoff_coeff formula

no_pass_zone_speed_pct_override = 0.1 ; % of race line speed below which car no pass zone waypoint is overridden,

passee_dlong_sep_coeff = 0.35 ; modifies desired dlong sep. when tailing designated passee

slow_lap_speed_adj_coeff = 0.900000 ; value modifies all speed-related goals for driving a slow lap

start_practice_dlong_sep = 100.000000 ; dlong sep to car behind required to consider starting practice lap

start_practice_pit_wait = 120.000000 ; baseline time in SECONDS car will wait in pit at start of practice session

straightaway_pass_closing_velocity = 0.022 ; dlong closing vel. to designated passee at which pass attempt initiated

straightaway_pass_dlong_sep = 10.0 ; dlong sep to designated passee at which pass attempt initiated

straightaway_pass_max_accel_pct = 0.925 ; % of our max_accel applying (due to dlong avoid) below which pass initiated

straightaway_pass_speed_coeff = 0.000000 ; value * Aggression if >= 1.0 modifies dlong speed for pass attempt in waypoint-marked straightaway

[ driver_modeling ]

; GLOBAL SCALING

global_driver_mod_scaling = 1.000000 ; scaling coefficient for all driver personality parameters loaded from DRIVER.INI

fast_global_hype_scaling = 0.900 ; scaling coefficient to transform normalized player time (when below 1.0) into global hype

slow_global_hype_scaling = 1.00000 ; scaling coefficient to transform normalized player time (when above 1.0) into global hype

novice_behavior_scaling = 1.7500000 ; scaling coeff for < 1.0 driver params for NOVICE difficulty

intermediate_behavior_scaling = 1.2500000 ; scaling coeff for < 1.0 driver params for INTERMEDIATE difficulty

pro_behavior_scaling = 1.0000000 ; scaling coeff for < 1.0 driver params for PRO difficulty

; PARAMETER-SPECIFIC SCALING

aggression_desired_sep_scaling = 1.000000 ; INVERSE_SCALE_COEFF(aggression,value) modifies desired dlong/dlat separations

aggression_trans_time_scaling = 1.000000 ; INVERSE_SCALE_COEFF(aggression,value) modifies goal transition times

aggression_yaw_k1_scaling = 1.000000 ; SCALE_COEFF(aggression,value) modifies yaw spring/damper k1

alertness_desired_sep_scaling = 1.200000 ; INVERSE_SCALE_COEFF(alertness,value) modifies desired dlong/dlat separations

alertness_lookahead_scaling = 1.000000 ; SCALE_COEFF(alertness,value) modifies lookahead time

experience_lookahead_scaling = 1.000000 ; SCALE_COEFF(lookahead,value) modifies lookahead time

experience_nom_traction_scaling = 0.500000 ; SCALE_COEFF(experience,value) modifies nom_traction_circle

hype_dlong_accel_scaling = 1.000000 ; SCALE_COEFF(hype,value) modifies dlong_accel

hype_nom_traction_scaling = 1.100000 ; SCALE_COEFF(hype,value) modifies nom_traction_circle

quickness_adj_traction_scaling = 1.000000 ; SCALE_COEFF(quickness,value) modifies adj_traction_circle

quickness_dlong_accel_scaling = 1.000000 ; SCALE_COEFF(quickness,value) modifies dlong_accel

quickness_gearshift_scaling = 2.000000 ; INVERSE_SCALE_COEFF(quickness,value) modifies base_gearshift_hiatus value

smoothness_adj_traction_scaling = 1.000000 ; SCALE_COEFF(smoothness,value) modifies adj_traction_circle

smoothness_trans_time_scaling = 1.500000 ; SCALE_COEFF(smoothness,value) modifies goal transition times

smoothness_yaw_k1_scaling = 1.000000 ; SCALE_COEFF(smoothness,value) modifies yaw spring/damper k1

; DRIVER ERRORS

base_brake_lock_chance = 10.000000 ; base chance in 100 that selected driver will lock brakes

base_missed_gear_chance = 10.000000 ; base chance in 100 that selected driver will botch gearshift

check_driver_mistake_interval = 2160.000000 ; base interval in ticks for choosing random driver to check for mistake

; RANDOM MODIFICATIONS

n_mods_per_interval = 0.500000 ; if mods to be applied apply this # per car on track

in_session_chance_aggression_mod = 10.000000 ; in session chance in 100 that given random mod affects aggression

in_session_chance_alertness_mod = 3.000000 ; in session chance in 100 that given random mod affects alertness

in_session_chance_experience_mod = 0.000000 ; in session chance in 100 that given random mod affects experience

in_session_chance_hype_mod = 2.000000 ; in session chance in 100 that given random mod affects hype

in_session_chance_qualifying_mod = 0.000000 ; in session chance in 100 that given random mod affects qualifying

in_session_chance_quickness_mod = 50.000000 ; in session chance in 100 that given random mod affects quickness

in_session_chance_smoothness_mod = 35.000000 ; in session chance in 100 that given random mod affects smoothness

in_session_driver_mod_interval = 21600.000000 ; interval (in ticks) between random, in-session driver mods

start_session_chance_aggression_mod = 0.000000 ; [unused for GPL] start session chance in 100 that given random mod affects aggression

start_session_chance_alertness_mod = 0.000000 ; [unused for GPL] start session chance in 100 that given random mod affects alertness

start_session_chance_experience_mod = 0.000000 ; [unused for GPL] start session chance in 100 that given random mod affects experience

start_session_chance_hype_mod = 0.000000 ; [unused for GPL] start session chance in 100 that given random mod affects hype

start_session_chance_qualifying_mod = 0.000000 ; [unused for GPL] start session chance in 100 that given random mod affects qualifying

start_session_chance_quickness_mod = 100.000000 ; [unused for GPL] start session chance in 100 that given random mod affects quickness

start_session_chance_smoothness_mod = 0.000000 ; [unused for GPL] start session chance in 100 that given random mod affects smoothness

[ magic ]

disable_random_modifiers = 0.000000 ; set to 1.0 to prevent random driver modifiers (0.0 = modifiers allowed)

dump_turn_map = 0.000000 ; dump the turn map using REPORT_MESSAGE

global_speed_override = 1.000000 ; start of session speed override for all AI cars (0.0 = stopped, 1.0 = normal)

improve_base_index_ahead = 3.000000 ; base index ahead at which to begin assessing dlat errors

improve_down_amt = 0.002500 ; % by which to decrease speed when decrease implemented

improve_down_threshold = 0.450000 ; dlat error (in meters) after which will decrease speed

improve_initial_increase = 0.0000000 ; % for initial across-the-board increase to line speed when learning begins

improve_initial_lookahead = 3.000000 ; initial lookahead in seconds for assessing dlat errors

improve_lookahead_increment = 0.200000 ; increment to lookahead for when lookahead propagation for flagrant error occurs

improve_max_waypoint_hype = 1.150000 ; max. waypoint hype that learning algorithm will apply to given index

improve_n_index_to_adjust = 10.000000 ; # indices to adjust for when lookahead propagation for flagrant error occurs

improve_up_amt = 0.00500000 ; % by which to increase speed when increase attempted

improve_up_threshold = 0.2000 ; dlat error (in meters) for which permit speed increase

line_to_improve = 0.000000 ; line to improve using learning algorithm

log_spreadsheet_tcircle = 0.000000 ; # log traction circle, spreadsheet format (0.0 = no, 1.0 = yes)

log_spreadsheet_telemetry = 0.000000 ; # log telemetry, spreadsheet format (0.0 = no, 1.0 = yes)

n_ai_cars = -1.000000 ; overrides # of AI cars set in UI (use -1.0 to ignore this override)

npt_override = 0.00 ; set to > 0.0 to override normalized player time

override_difficulty_hype = 0.0 ; override difficulty hype adjustment (0.0 = no, 1.0 = yes)

parameter_table_magic_number = 1234.000000 ; magic # for integrity check--DO NOT MODIFY

signal_induced_problems = 1.000000 ; have drivers raise hand if have induced problem/error (0.0 = no, 1.0 = yes)

startup_npt = 1.20 ; new player starting normalized player time

[ mechanical ]

base_brake_wear = 0.000000 ; wear (as max_decel coeff.) per kilometer (1000 ms)

base_fuel_consumption = 0.000000 ; wear (as traction circle coeff.) per kilometer (1000 ms)

base_fuel_drag = 0.001000 ; drag (meters/second added to external_dlong_accel) from fuel weight

base_suspension_failure_coeff = 0.600000 ; * traction circle = adj. traction circle

base_suspension_problem_coeff = 0.800000 ; * traction circle = adj. traction circle

base_tire_failure_coeff = 0.500000 ; * traction circle = adj. traction circle

base_tire_wear = 0.000000 ; wear (as traction circle coeff.) per kilometer (1000 ms)

brake_failure_chance = 1.000000 ; % chance any problem/failure involves brake failure

brake_problem_chance = 2.000000 ; % chance any problem involves brake problem

coolant_leak_chance = 2.000000 ; % chance any problem/failure involves coolant leak

driver_fuel_consumption_scaling = 0.000000 ; scales effect of quickness, smoothness, and aggression

driver_tire_break_wear_scaling = 0.000000 ; scales effect of smoothness and aggression

engine_failure_chance = 16.000000 ; % chance any problem/failure involves engine failure

engine_problem_chance = 23.000000 ; % chance any problem involves engine problem

front_tire_failure_yaw_k1_scale = 0.035000 ; see aiCar::ComputeYawSpringCoeff

fuel_leak_chance = 2.000000 ; % chance any problem/failure involves fuel leak

fuel_system_failure_chance = 5.000000 ; % chance any problem/failure involves fuel system failure

fuel_system_problem_chance = 7.000000 ; % chance any problem involves fuel system problem

mechanical_failure_chance = 5.000000 ; chance in 10000 (!!) per ACTIVE AI car for induced problem/failure each interval

mechanical_failure_interval = 540.000000 ; average interval in ticks to check for mechanical problem/failure (gets randomized)

oil_leak_chance = 10.000000 ; % chance any problem/failure involves oil leak

rear_tire_failure_yaw_k1_scale = 0.035000 ; see aiCar::ComputeYawSpringCoeff

suspension_cond_accel_scaling = 0.100000 ; max_accel *= SCALE_COEFF(suspension_condition,value)

suspension_cond_decel_scaling = 0.500000 ; max_decel *= SCALE_COEFF(suspension_condition,value)

suspension_failure_chance = 10.000000 ; % chance any problem/failure involves suspension failure

suspension_failure_yaw_k1_scale = 0.330000 ; see aiCar::ComputeYawSpringCoeff

suspension_mechanical_drag_coeff = 0.0025000 ; meters/tick^2 drag--see aiCar::ComputeMechanicalDrag

suspension_problem_chance = 15.000000 ; % chance any problem involves suspension problem

suspension_problem_pitch_adj_coeff = 0.100000 ; value * susp. condition adjusts pitch

suspension_problem_roll_adj_coeff = 0.100000 ; value * susp. condition adjusts roll

suspension_problem_slip_angle_adj = 0.150000 ; value * slip angle * k is added to suspension coeff.

suspension_problem_yaw_k1_scale = 0.050000 ; see aiCar::ComputeYawSpringCoeff

tire_cond_accel_scaling = 0.100000 ; max_accel *= SCALE_COEFF(tire_condition,value)

tire_cond_decel_scaling = 0.300000 ; max_decel *= SCALE_COEFF(tire_condition,value)

tire_failure_chance = 3.000000 ; % chance any problem/failure involves tire failure

tire_failure_mechanical_drag_coeff = 0.00300 ; meters/tick^2 drag--see aiCar::ComputeMechanicalDrag

tire_problem_chance = 4.000000 ; % chance any problem involves tire problem

tire_problem_slip_angle_adj = 0.150000 ; value * slip angle * k is added to tire coeff.

[ physics ]

alt_accel_k1 = 0.070000 ; k1 for altitude control spring/damper

alt_accel_k2 = 0.32000 ; k2 for altitude control spring/damper

;alt_accel_k1 = 0.121800 ; k1 for altitude control spring/damper

;alt_accel_k2 = 0.488700 ; k2 for altitude control spring/damper

drive_train_friction_adj = 0.250000 ; fudge factor for drive train friction coeff. use for max. engine accel

gear_shift_rpm_decrement = 195.000000 ; during gear shift decrement RPM each tick by this amount

idle_scaled_power = 0.080000 ; eng. power when engine idling scaled between 0 and 1

inertial_factor = 0.300000 ; adj. max_accel to simulate inertia--see aiAdvanceCarOnLine()

inverse_slipcurve_k = 0.166700 ; in (meters/tick^2)/radian; calculated by JDK for use with fnSlipcurve table by yaw pipeline

;inverse_slipcurve_k = 0.168700 ; in (meters/tick^2)/radian; calculated by JDK for use with fnSlipcurve table by yaw pipeline

max_lat_acc_from_speed = 0.0125000 ; value * speed = max. lat accel allowed

minimum_rpm = 1000.000000 ; min. engine rpm (e.g., when car idle)

nominal_downforce_coeff = 5700.657227 ;

coeff = v^2 / X.XXXG. = XXXMPH^2 / X.XXXG = 200MPH^2 * 7 / ONE_G

nominal_drag_coeff = 2638.590088 ;

?? coeff = v^2 / 0.XXXXG. = XXXMPH^2 / 0.XXXXG

pitch_accel_coeff = 2.000000 ; value * averaged_applied_tire_dlong_accel = radians of pitch

roll_accel_coeff = 3.000000 ; value * dlat_accel = radians of roll

rolling_drag_amt = 0.040000 ; value * external_N_accel = drag (in meters/tick^2) caused by tires et. al.

yaw_accel_k1 = 0.120000 ; k1 for yaw accel. spring/damper

yaw_accel_k2 = 1.000000 ; k2 for yaw accel. spring/damper

max_ws_interval = 108.000000 ; max time(ticks) to stop wheelspin

min_ws_interval = 54.000000 ; min time(ticks) to stop wheelspin

wheelspin_min_adj_coeff = 0.50000 ; max grip reduction from wheelspin

; *************************************

; FUZZY LINE PARAMETERS

; *************************************

[ follow_line ]

avoid_time_coeff = 0.100 ; value * est. time to collision = ticks before do obstacle avoidance

desired_dlong_sep = 14.0 ; default desired dlong separation in meters between us and car in front

dlat_accel_k1 = 0.0045 ; k1 for dlat accel. goal spring/damper

dlat_accel_k2 = 0.1202 ; k2 for dlat accel. goal spring/damper

dlat_lookahead = 0.000000 ; default lookahead in ticks for calculating dlat accel goal

long_term_lookahead = 108.000000 ; default long-term lookahead in ticks

short_term_lookahead = 17.000000 ; default short-term lookahead in ticks

cornering_avoid_time_coeff = 0.12000 ; cornering param

cornering_desired_dlong_sep = 13.5 ; cornering param

cornering_dlat_accel_k1 = 0.0086 ; cornering param

cornering_dlat_accel_k2 = 0.1432 ; cornering param

cornering_dlat_lookahead = 0.000000 ; cornering param

cornering_long_term_lookahead = 90.000000 ; cornering param

cornering_short_term_lookahead = 17.000000 ; cornering param

switch_to_cornering_dlat_velocity = 0.10 ; default dlat vel. (in meters/tick) at which use cornering fuzzy line params

[ basic_line_transition ]

avoid_time_coeff = 0.0875 ; value * est. time to collision = ticks before do obstacle avoidance

desired_dlong_sep = 13.5 ; default desired dlong separation in meters between us and car in front

dlat_accel_k1 = 0.0056 ; k1 for dlat accel. goal spring/damper

dlat_accel_k2 = 0.1254 ; k2 for dlat accel. goal spring/damper

dlat_lookahead = 0.000000 ; default lookahead in ticks for calculating dlat accel goal

dlat_trans_time = 4.000000 ; default time in ticks to achieve dlat goal

long_term_lookahead = 108.000000 ; default long-term lookahead in ticks

short_term_lookahead = 17.000000 ; default short-term lookahead in ticks

cornering_avoid_time_coeff = 0.105000 ; cornering param

cornering_desired_dlong_sep = 12.5 ; cornering param

cornering_dlat_accel_k1 = 0.00920 ; cornering param

cornering_dlat_accel_k2 = 0.152400 ; cornering param

cornering_dlat_lookahead = 0.000000 ; cornering param

cornering_dlat_trans_time = 3.000000 ; cornering param

cornering_long_term_lookahead = 72.000000 ; cornering param

cornering_short_term_lookahead = 17.000000 ; cornering param

switch_to_cornering_dlat_velocity = 0.10 ; default dlat vel. (in meters/tick) at which use cornering fuzzy line params

[ abrupt_line_transition ]

avoid_time_coeff = 0.06 ; value * est. time to collision = ticks before do obstacle avoidance

desired_dlong_sep = 13.0 ; default desired dlong separation in meters between us and car in front

dlat_accel_k1 = 0.0087 ; k1 for dlat accel. goal spring/damper

dlat_accel_k2 = 0.1224 ; k2 for dlat accel. goal spring/damper

dlat_lookahead = 0.000000 ; default lookahead in ticks for calculating dlat accel goal

dlat_trans_time = 3.000000 ; default time in ticks to achieve dlat goal

long_term_lookahead = 108.000000 ; default long-term lookahead in ticks

short_term_lookahead = 16.000000 ; default short-term lookahead in ticks

cornering_avoid_time_coeff = 0.0950 ; cornering param

cornering_desired_dlong_sep = 12.0 ; cornering param

cornering_dlat_accel_k1 = 0.0101 ; cornering param

cornering_dlat_accel_k2 = 0.1274 ; cornering param

cornering_dlat_lookahead = 0.000000 ; cornering param

cornering_dlat_trans_time = 2.000000 ; cornering param

cornering_long_term_lookahead = 54.000000 ; cornering param

cornering_short_term_lookahead = 17.000000 ; cornering param

switch_to_cornering_dlat_velocity = 0.10 ; default dlat vel. (in meters/tick) at which use cornering fuzzy line params

[ entering_pits ]

avoid_time_coeff = 0.250000 ; value * est. time to collision = ticks before do obstacle avoidance

desired_dlong_sep = 12.563100 ; default desired dlong separation in meters between us and car in front

dlat_accel_k1 = 0.002000 ; k1 for dlat accel. goal spring/damper

dlat_accel_k2 = 0.120000 ; k2 for dlat accel. goal spring/damper

dlat_lookahead = 1.000000 ; default lookahead in ticks for calculating dlat accel goal

dlat_trans_time = 0.000000 ; default time in ticks to achieve dlat goal

long_term_lookahead = 108.000000 ; default long-term lookahead in ticks

short_term_lookahead = 36.000000 ; default short-term lookahead in ticks

cornering_avoid_time_coeff = 0.250000 ; cornering param

cornering_desired_dlong_sep = 12.563100 ; cornering param

cornering_dlat_accel_k1 = 0.003000 ; cornering param

cornering_dlat_accel_k2 = 0.140000 ; cornering param

cornering_dlat_lookahead = 0.000000 ; cornering param

cornering_long_term_lookahead = 108.000000 ; cornering param

cornering_short_term_lookahead = 36.000000 ; cornering param

switch_to_cornering_dlat_velocity = 0.1 ; default dlat vel. (in meters/tick) at which use cornering fuzzy line params

[ approaching_pit_stall ]

avoid_time_coeff = 0.450000 ; value * est. time to collision = ticks before do obstacle avoidance

desired_dlong_sep = 12.563100 ; default desired dlong separation in meters between us and car in front

dlat_accel_k1 = 0.002000 ; k1 for dlat accel. goal spring/damper

dlat_accel_k2 = 0.120000 ; k2 for dlat accel. goal spring/damper

dlat_lookahead = 0.000000 ; default lookahead in ticks for calculating dlat accel goal

dlat_trans_time = 1.000000 ; default time in ticks to achieve dlat goal

long_term_lookahead = 108.000000 ; default long-term lookahead in ticks

short_term_lookahead = 54.000000 ; default short-term lookahead in ticks

cornering_avoid_time_coeff = 0.250000 ; cornering param

cornering_desired_dlong_sep = 12.563100 ; cornering param

cornering_dlat_accel_k1 = 0.003000 ; cornering param

cornering_dlat_accel_k2 = 0.140000 ; cornering param

cornering_dlat_lookahead = 0.000000 ; cornering param

cornering_long_term_lookahead = 108.000000 ; cornering param

cornering_short_term_lookahead = 36.000000 ; cornering param

switch_to_cornering_dlat_velocity = 0.1 ; default dlat vel. (in meters/tick) at which use cornering fuzzy line params

[ leaving_pits ]

avoid_time_coeff = 0.250000 ; value * est. time to collision = ticks before do obstacle avoidance

desired_dlong_sep = 12.563100 ; default desired dlong separation in meters between us and car in front

dlat_accel_k1 = 0.002000 ; k1 for dlat accel. goal spring/damper

dlat_accel_k2 = 0.120000 ; k2 for dlat accel. goal spring/damper

dlat_lookahead = 1.000000 ; default lookahead in ticks for calculating dlat accel goal

long_term_lookahead = 108.000000 ; default long-term lookahead in ticks

short_term_lookahead = 36.000000 ; default short-term lookahead in ticks

cornering_avoid_time_coeff = 0.250000 ; cornering param

cornering_desired_dlong_sep = 12.563100 ; cornering param

cornering_dlat_accel_k1 = 0.003000 ; cornering param

cornering_dlat_accel_k2 = 0.140000 ; cornering param

cornering_dlat_lookahead = 0.000000 ; cornering param

cornering_long_term_lookahead = 108.000000 ; cornering param

cornering_short_term_lookahead = 36.000000 ; cornering param

switch_to_cornering_dlat_velocity = 0.10 ; default dlat vel. (in meters/tick) at which use cornering fuzzy line params

[ line_improvement ]

avoid_time_coeff = 0.07000 ; value * est. time to collision = ticks before do obstacle avoidance

desired_dlong_sep = 8.0 ; default desired dlong separation in meters between us and car in front

dlat_accel_k1 = 0.00500 ; k1 for dlat accel. goal spring/damper

dlat_accel_k2 = 0.155000 ; k2 for dlat accel. goal spring/damper

;dlat_accel_k1 = 0.00300 ; k1 for dlat accel. goal spring/damper

;dlat_accel_k2 = 0.13000 ; k2 for dlat accel. goal spring/damper

dlat_lookahead = 0.000000 ; default lookahead in ticks for calculating dlat accel goal

long_term_lookahead = 108.000000 ; default long-term lookahead in ticks

short_term_lookahead = 16.000000 ; default short-term lookahead in ticks

cornering_avoid_time_coeff = 0.1100000 ; cornering param

cornering_desired_dlong_sep = 7.5 ; cornering param

cornering_dlat_accel_k1 = 0.009000 ; cornering param

cornering_dlat_accel_k2 = 0.200000 ; cornering param

;cornering_dlat_accel_k1 = 0.004000 ; cornering param

;cornering_dlat_accel_k2 = 0.100000 ; cornering param

cornering_dlat_lookahead = 0.000000 ; cornering param

cornering_long_term_lookahead = 96.000000 ; cornering param

cornering_short_term_lookahead = 14.000000 ; cornering param

switch_to_cornering_dlat_velocity = 0.10 ; default dlat vel. (in meters/tick) at which use cornering fuzzy line params

[ entering_pit_stall ]

dlat_trans_time = 108.000000 ; default time in ticks to achieve dlat goal

[ leaving_pit_stall ]

dlat_trans_time = 108.000000 ; default time in ticks to achieve dlat goal

; *************************************

; CAR CLASS PARAMETERS

; *************************************

[ GP ]

braking_efficiency_coeff = 0.80000 ; value * adj_traction_circle = max. decel

;braking_efficiency_coeff = 0.700 ; VALUE USED FOR LEARNING ALGORITHM

nominal_max_accel = 0.006806 ; accel. in meters/tick^2 (1G = 0.007562)

;nominal_traction_circle = 0.0109649 ; same units as accel. (meters/tick^2) -- 1.45 * ONE_G

nominal_traction_circle = 0.0111540 ; same units as accel. (meters/tick^2) -- 1.475 * ONE_G

(8^{|)

holeshot
Junior Member

Career Honda motorcycle tech, state drag race championship builder, world land speed record builder.

Posts: 60

NR2003 INI FILES Aug 17, 2017 18:34:25 GMT

Quote

Post by holeshot on Aug 17, 2017 18:34:25 GMT

The GPL driver.ini has an entry for EACH driver with the following keys:

[ driver_1 ]

team_number = 5 ; team_number

team_order = 1 ; team_order

car_number = 5 ; car_number

first_name = Jim ; first_name

last_name = Clark ; last_name

home_town = Kilmany, Scotland ; home_town

nationality = 12 ; nationality

helmet_color = 1 ; helmet_color

bump_order = 19 ; bump_order

aggression = 1.030000 ; aggression

alertness = 1.030000 ; alertness

experience = 1.010000 ; experience

hype = 1.002000 ; hype

qualifying = 1.020000 ; qualifying

quickness = 1.050000 ; quickness

smoothness = 1.000000 ; smoothness

global_hype_scaling = 0.05 ; global_hype_scaling

starting_grid_seed = 3.0 ; starting_grid_seed

chance_brake_failure = 35.000000 ; chance_brake_failure

chance_brake_problem = 35.000000 ; chance_brake_problem

chance_coolant_leak = 35.000000 ; chance_coolant_leak

chance_engine_failure = 50.000000 ; chance_engine_failure

chance_engine_problem = 50.000000 ; chance_engine_problem

chance_fuel_leak = 35.000000 ; chance_fuel_leak

chance_fuel_system_failure = 35.000000 ; chance_fuel_system_failure

chance_fuel_system_problem = 35.000000 ; chance_fuel_system_problem

chance_oil_leak = 35.000000 ; chance_oil_leak

chance_suspension_failure = 50.000000 ; chance_suspension_failure

chance_suspension_problem = 50.000000 ; chance_suspension_problem

chance_tire_failure = 40.000000 ; chance_tire_failure

chance_tire_problem = 35.000000 ; chance_tire_problem

photo = clar ; photo_file

(8^{|)

holeshot
Junior Member

Career Honda motorcycle tech, state drag race championship builder, world land speed record builder.

Posts: 60

NR2003 INI FILES Aug 17, 2017 18:45:24 GMT

Quote

Post by holeshot on Aug 17, 2017 18:45:24 GMT

GPL offers the following for command line options, NR has cmd line options, too:

Advanced options: Using startup arguments can setup certain settings automatically, or start the game without using the GUI.

Format: GTP_Launcher.exe -<arg1key> -<arg2key>="<arg2value>" <any other arguments for the game itself>

with:

<arg1key>: argument which doesn't require a value (like directExec and enableTrace, see below)

<arg2key>: argument which does require a value (like eg. selectCar)

<any other arguments for the game itself>: arguments which are to be send to the game itself, its imporant to first give the arguments which are meant for the launcher, and after those any other arguments for the game

Supported arguments:

"selectCar": Description: Select one of the 4 cars

Value: [0-3]

0=Mazda 787b

1=Toyota 88cv

2=Sauber c9

3=Jaguar XJR-9

"selectSkin": Description: Select the skin for the selected car. This can be the one provided by the selectCar argument if one is given, else the last selected car will be used.

Value: Skin filename (eg. "13 BRD SAU.gtp.car")

"gtpMode": Description: Select the mode in which the game should be run.

Value: [0-3]

0=Day - Singleplayer

1=Day - Multiplayer

2=Night - Singleplayer

3=Night - Multiplayer

"selectActivePlayerDir": Description: Select the directory of the player which should be used.

Value: Directory name of the selected player (eg. "Player__The")

"directExec": Description: Skin the GUI, and execute the game directly

Value: None required

"enableTrace": Description: Enable the creation of a trace.txt file, which is only important for bugtracking.

Value: None required

"requireVersion": Description: Enables external programs to specify which minimal version of the launcher should be used.

Value: Version number (eg. "1.00")

Example: Say you want to execute the mod with the toyota, in gamemode 0 (day - singleplayer) and skipping the gui, you'd have to use the following command: GTP_Launcher -selectCar="1" -gtpMode="0" -directExec

This will launch the game without interferance of the GUI, and will use the last used skin for the selected car (last skin from the launchers point of view).

(8^{|)

Adrianokig Guest	NR2003 INI FILES Jul 23, 2020 14:47:12 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by Adrianokig on Jul 23, 2020 14:47:12 GMT Nicely put. Thanks a lot! <a href="https://paydayloansbbv.com//">payday loans online</a>

rotcletty Guest	NR2003 INI FILES Aug 4, 2020 12:55:00 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by rotcletty on Aug 4, 2020 12:55:00 GMT what does levitra pill look like Lawdrido viagra vs cialis MulseBiseMic Levitra Comprare incemnig <a href=https://ascialis.com/#>Cialis</a> Fraceanarync Levitra With Dapoxetine Reviews

HaroldStamn Guest	NR2003 INI FILES Sept 16, 2020 21:58:06 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by HaroldStamn on Sept 16, 2020 21:58:06 GMT Hi, here on the forum guys advised a cool Dating site, be sure to register - you will not REGRET it <a href=https://bit.ly/35y3a7C>https://bit.ly/35y3a7C</a>

gyproryNags Guest	NR2003 INI FILES Sept 22, 2020 23:27:11 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by gyproryNags on Sept 22, 2020 23:27:11 GMT casino slots free slots games vegas casino slots <a href="http://onlinecasinouse.com/# ">online casino bonus </a> real money casino

cialis dosage Guest	NR2003 INI FILES Nov 12, 2021 21:52:45 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by cialis dosage on Nov 12, 2021 21:52:45 GMT <a href="https://cialiswithdapoxetine.com/#">cialis 20 mg</a> cialis 20 mg

cialis dosage Guest	NR2003 INI FILES Nov 12, 2021 21:53:57 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by cialis dosage on Nov 12, 2021 21:53:57 GMT <a href="https://cialiswithdapoxetine.com/#">cialis 20 mg</a> cialis 20 mg

buy cialis online Guest	NR2003 INI FILES Nov 13, 2021 21:18:37 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by buy cialis online on Nov 13, 2021 21:18:37 GMT <a href="https://cialiswithdapoxetine.com/#">cialis without a doctor prescription</a> cheap cialis

Nrgnascar

NR2003 INI FILES

Post by Admin on Aug 16, 2017 18:19:13 GMT

Post by holeshot on Aug 17, 2017 3:36:22 GMT

Post by holeshot on Aug 17, 2017 3:40:52 GMT

Post by holeshot on Aug 17, 2017 3:44:55 GMT

Post by holeshot on Aug 17, 2017 4:20:55 GMT

Post by holeshot on Aug 17, 2017 18:32:47 GMT

Post by holeshot on Aug 17, 2017 18:34:25 GMT

Post by holeshot on Aug 17, 2017 18:45:24 GMT

Post by Adrianokig on Jul 23, 2020 14:47:12 GMT

Post by rotcletty on Aug 4, 2020 12:55:00 GMT

Post by HaroldStamn on Sept 16, 2020 21:58:06 GMT

Post by gyproryNags on Sept 22, 2020 23:27:11 GMT

Post by cialis dosage on Nov 12, 2021 21:52:45 GMT

Post by cialis dosage on Nov 12, 2021 21:53:57 GMT

Post by buy cialis online on Nov 13, 2021 21:18:37 GMT

Quick Reply