Quote:
Originally Posted by Shipkiller
At the beginning, it is just one peddle at a time. At the apex, start to release the brake and apply throttle. Many times I have to do this to transfer weight to the rear (the front is already set) to keep the rear planted...
|
So you're doing it to smooth the transition from braking to accelerating, and make the resultant weight transfer subtle, yes?
Quote:
Originally Posted by Matt Romanowski
Reading quickly, you may be able to nest another if/then function (if RS2 allows it) or a greater than to make it choose only one input.
|
Yes, we should be able to nest a couple more if-then-elses in there, keying off both bakes and throttle being greater than 0, but the question is which input would we want to select in this situation? Throttle or brakes? I'd say use the brake data, and then create yet another math channel that's only throttle position, but with the downshift blips suppressed as per above. Then, that new trace could be overlayeded on the same graph as he combined throttle-brakes trace; most of the time, they're exactly the same line (with a little "clutter" at zero). When doing the 'Shipkiller Techniqure", however, you'd be able to see each input separately.
The only problem here is that it wouldn't work well when presenting the 'pedal inputs" in map format using Track Report view. You'd want the combined channel to have, I think, the throttle input instead of brakes there. Of course, you could make yet another combined math channel just for the Track Report view...
Any of this make any sense?