N3 - How do you make fuel/tires usage relative?

Hey, Just got N3 and was wondering if there was any way to make the usage of fuel and wearing tires relative to the length of the race. I just don't have the time or patience to race long enough where pitting comes into play - and no pitting takes all the strategy out of the sim. Any way to alter this in the core file? Thanks in Advance Jcharm

Get Nascar Legends. Those older cars ate up tires and fuel 5 times faster then the modern cars. Pitting becomes part of every race even the short ones -- Kevin Anderson --------------------------------------------------- DK-Racing #15 K_Anderson ------------------------------------------------- http://www.awtech.net/ http://www.nascar-3.com/

> Just got N3 and was wondering if there was any way to make the usage of fuel > and wearing tires relative to the length of the race. I just don't have the I floated this idea 3 or 4 years ago. No one was into it. Seems like a natural feature to include. -- Pat Dotson IMPACT Motorsports http://www.impactmotorsports.com/pd.html

it is included in SCGT, but as for N3 you can "force" the early pitstop to a point, if you get the track.txt and change the pit window...not easy, not elegant, and not always do-able in really short races, but it has been done in the TPTCC. Races average about 45 minutes to an hour with one mandatory pitstop. If this is too long then you may be out of luck. dave henrie

Quoted text (10 lines)

> > Just got N3 and was wondering if there was any way to make the usage of fuel > > and wearing tires relative to the length of the race. I just don't have the > I floated this idea 3 or 4 years ago. No one was > into it. Seems like a natural feature to include. > -- > Pat Dotson > IMPACT Motorsports > http://www.impactmotorsports.com/pd.html

You can play with the tracks .txt file and get close to what you want, however, as mentioned in the previous reply, it's a considerable undertaking and the results will vary.... You can cause the AI cars to pit sooner by changing the SPDWY line: the two numbers after either a 0 or 1 is the pit window for the computer controlled cars under green flag conditions.... if the line is SPDWY 0 100 110 then somewhere between 100 to 110 laps is where they will pit... change it to whatever, but a real small window may not work too well. As far as your own fuel milage, you'll just have to decide how many laps you "run out" at as there is no way that I know of to adjust it. You can play with the tire wear by editing the TIRES line: if you have a line that reads TIRES 67344 5100 99000000 67344 4000 99000000 0, the 5100 I believe is the left side wear and the 4000 is right side.... lower numbers=shorter tire life. you'll just have to experiment and see how well it works.... ~Good Luck

You mean it is hardcoded that a right tyre will wear more than a left tyre? What sort of physicsmodell hardcodes that?! It should at least be _somewhat_ related to usage, temps etc.

The right tyre is 'coded' to wear more than the left because you are generally speaking going around a circuit anti clockwise, which puts more stress on the right tyre. In another discussion group I had it explained what the numbers do. The 5100 is left side, 4000 right side, and lower numbers are LOWER TEMP. Fore and aft is taken care of in the car setup. The 67344 in first and fourth places in the string are the grip, left and right, lower number means lower grip. In NL especially these can be edited to good effect and make the cars handle in a more entertaining way, not to mention make the tyre wear more acceptable. Steve

Quoted text (10 lines)

>You mean it is hardcoded that a right tyre will wear more than a left tyre? >What sort of physicsmodell hardcodes that?! >It should at least be _somewhat_ related to usage, temps etc. >> You can play with the tire wear by editing the TIRES line: if you have a >> line that reads TIRES 67344 5100 99000000 67344 4000 99000000 0, the 5100 >I >> believe is the left side wear and the 4000 is right side.... lower >> numbers=shorter tire life.

I think the point that martin was trying to make was that, for sake of emphasis here, if I decide for some absurd reason to drive a track clockwise am I still going to see my right front wearing quicker than the left front. If this is the case then N3 would appear to lack decent physics feedback that has any relation to how I am driving when related to tyre wear and, without a decent physics feedback how am I supposed to be able to set the car up to run at its optimum? With the example above I would still be trying to work my ass off trying to stop the right front from wearing out when in reality there is nothing that I can do about it (save tinkering with file settings which I shouldn't have to touch) because it is hard coded.

Quoted text (10 lines)

>>You mean it is hardcoded that a right tyre will wear more than a left tyre? >>What sort of physicsmodell hardcodes that?! >>It should at least be _somewhat_ related to usage, temps etc. >>> You can play with the tire wear by editing the TIRES line: if you have a >>> line that reads TIRES 67344 5100 99000000 67344 4000 99000000 0, the 5100 >>I >>> believe is the left side wear and the 4000 is right side.... lower >>> numbers=shorter tire life.

-- Peter Ives - (AKA Ivington) No person's opinions can be said to be more correct than another's, because each is the sole judge of his or her own experience.

I can't really see what you mean by 'hard coded'. If you don't like the default tyre temp values, change them. In this way it should be possible to drive backwards around any track. Steve

Quoted text (16 lines)

>I think the point that martin was trying to make was that, for sake of >emphasis here, if I decide for some absurd reason to drive a track >clockwise am I still going to see my right front wearing quicker than >the left front. If this is the case then N3 would appear to lack decent >physics feedback that has any relation to how I am driving when related >to tyre wear and, without a decent physics feedback how am I supposed to >be able to set the car up to run at its optimum? >With the example above I would still be trying to work my ass off trying >to stop the right front from wearing out when in reality there is >nothing that I can do about it (save tinkering with file settings which >I shouldn't have to touch) because it is hard coded. >>>You mean it is hardcoded that a right tyre will wear more than a left

tyre? >>>What sort of physicsmodell hardcodes that?! >>>It should at least be _somewhat_ related to usage, temps etc. >>>> You can play with the tire wear by editing the TIRES line: if you have a >>>> line that reads TIRES 67344 5100 99000000 67344 4000 99000000 0, the 5100

Quoted text (10 lines)

>>>I >>>> believe is the left side wear and the 4000 is right side.... lower >>>> numbers=shorter tire life. >-- >Peter Ives - (AKA Ivington) >No person's opinions can be said to be >more correct than another's, because each is >the sole judge of his or her own experience.

But my point was, why should I have to tell the software how to think. Surely a physics model should work 'as is' no matter what I am doing on the track. I shouldn't have to tell it what is supposed to happen in any particular situation, a good physics model will be able to cope no matter what. That's what I call 'hard coded'. A physics model that can deal realistically with whatever I am doing on the track without me having to give it some help.

Quoted text (28 lines)

>>I think the point that martin was trying to make was that, for sake of >>emphasis here, if I decide for some absurd reason to drive a track >>clockwise am I still going to see my right front wearing quicker than >>the left front. If this is the case then N3 would appear to lack decent >>physics feedback that has any relation to how I am driving when related >>to tyre wear and, without a decent physics feedback how am I supposed to >>be able to set the car up to run at its optimum? >>With the example above I would still be trying to work my ass off trying >>to stop the right front from wearing out when in reality there is >>nothing that I can do about it (save tinkering with file settings which >>I shouldn't have to touch) because it is hard coded. >>>>You mean it is hardcoded that a right tyre will wear more than a left >tyre? >>>>What sort of physicsmodell hardcodes that?! >>>>It should at least be _somewhat_ related to usage, temps etc. >>>>> You can play with the tire wear by editing the TIRES line: if you have >a >>>>> line that reads TIRES 67344 5100 99000000 67344 4000 99000000 0, the >5100 >>>>I >>>>> believe is the left side wear and the 4000 is right side.... lower >>>>> numbers=shorter tire life.

-- Peter Ives - (AKA Ivington) No person's opinions can be said to be more correct than another's, because each is the sole judge of his or her own experience.

I would have thought that making your own car 'setup' was telling the software 'how to think'. I am sure that if you drive backwards around an oval the outside tyres will still heat up more than the inside in the 'default' settings. You 'customize' the sim in the first place by selecting resolution, opponent strength, graphic options etc. Adding patches does the same. The N3 'physics' is not as great as GPL, but its not as bad as you want to make it seem. There may be flaws, but thats why people in this newsgroup try to offer solutions if you have a problem. Don't believe that the game developers/designers are the last word, tweak it! Steve >>I can't really see what you mean by 'hard coded'. If you don't like the >>default tyre temp values, change them. In this way it should be possible to

Quoted text (35 lines)

>>drive backwards around any track. >But my point was, why should I have to tell the software how to think. >Surely a physics model should work 'as is' no matter what I am doing on >the track. I shouldn't have to tell it what is supposed to happen in >any particular situation, a good physics model will be able to cope no >matter what. That's what I call 'hard coded'. A physics model that can >deal realistically with whatever I am doing on the track without me >having to give it some help. >>>I think the point that martin was trying to make was that, for sake of >>>emphasis here, if I decide for some absurd reason to drive a track >>>clockwise am I still going to see my right front wearing quicker than >>>the left front. If this is the case then N3 would appear to lack decent >>>physics feedback that has any relation to how I am driving when related >>>to tyre wear and, without a decent physics feedback how am I supposed to >>>be able to set the car up to run at its optimum? >>>With the example above I would still be trying to work my ass off trying >>>to stop the right front from wearing out when in reality there is >>>nothing that I can do about it (save tinkering with file settings which >>>I shouldn't have to touch) because it is hard coded. >>>>>You mean it is hardcoded that a right tyre will wear more than a left >>tyre? >>>>>What sort of physicsmodell hardcodes that?! >>>>>It should at least be _somewhat_ related to usage, temps etc. >>>>>> You can play with the tire wear by editing the TIRES line: if you

have

Quoted text (12 lines)

>>a >>>>>> line that reads TIRES 67344 5100 99000000 67344 4000 99000000 0, the >>5100 >>>>>I >>>>>> believe is the left side wear and the 4000 is right side.... lower >>>>>> numbers=shorter tire life. >-- >Peter Ives - (AKA Ivington) >No person's opinions can be said to be >more correct than another's, because each is >the sole judge of his or her own experience.