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
--
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
--
Pat Dotson
IMPACT Motorsports
http://www.impactmotorsports.com/pd.html
> > 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 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
What sort of physicsmodell hardcodes that?!
It should at least be _somewhat_ related to usage, temps etc.
>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.
>>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.
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 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.
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
>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.
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.
>>>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.
