% My understanding is that the Papyrus sims do not model the gas and brake
% separately. When you step on the brake, it overrides the gas pedal, even if
% they are on separate axes.
(Note: for news servers that don't honor supersedes or cancels this is
an enhanced post).
While Papyrus sims does not "accurately" model separate axis for brake
and throttle, there is a marked difference in how the program reacts
between combined and separate axis. There is an advantage to having the
inputs on separate axis, however, it is not exactly the same as in real
life.
Here is Jim Sokoloff's explanation from the an older r.a.s. post:
ubject: Re: How do pedals / wheels work?
Date: 1997/04/26
Newsgroups: rec.autos.simulators
>> If the pedals are both wired to the same axis (the usual case), then
>> applying the brake is (electrically) the same as letting off the
>> throttle. If the brake and throttle are on separate axes, then it is
>> up to the game software what happens.
>> In Papyrus sims released to date, applying the brakes at all
overrides
>> the throttle input, causing something which is not what you describe
>> you want...
>> ---Jim
>So let me get this stright. If I'm running at Pocono and I have the
>Throttle all the way down heading into turn 1 I don't have to lift the
>foot off? I can just press on the brake and it overrides the throttle?
>So in a race, I can leave my foot on the throttle the whole time?
No. I wasn't clear.
In pedal sets with gas and brake wired together, the computer can only
read one value. (Think of it as Value = Throttle - Brakes.) If you
keep your foot on the throttle, and press the brakes 10%, the computer
will read (in percentages for simplicity:)
Value = 100% - 10% (+ 90% or 90% throttle, 0% brakes)
If you get off the throttle and 50% on the brakes, you'll get:
Value = 0% - 50% (-50% or 0% throttle, 50% brakes)
If you have 30% throttle and 50% brakes, the computer sees -20%, which
is 0% throttle, 20% brakes.
In the case of split axes (gas and brake not electrically connected),
the game reads the true value for brakes and throttle, and uses logic
similar to:
/* Account for noise in brake value reading */
If (brakes > 5%) {
throttle = 0%
Maybe that's clearer. Sorry for the earlier confusion.
---Jim
--
**************************** Michael E. Carver *************************
Upside out, or inside down...False alarm the only game in town.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=<[ /./. [- < ]>=-=-=-=-=-=-=-=-=-=-=-=-=-=