Issue: Throttle Stuck at 100% when using Engine Braking Maps
Affected Mod: Porsche 962C (Mak Corp Group C)
The Problem
The issue was caused by a conflict between the
EngineBrakingParams and the
Turbo physics calculation in rFactor’s engine.
The original Porsche file used:EngineBrakingParams=(3, 250)The algorithm "
3" is often used for turbocharged engines to calculate engine braking based on manifold pressure. However, in this specific mod, this calculation was broken. As soon as the user selected "Map 1" (or higher) in the garage, the physics engine would return an erroneous value, saturating the throttle input to 100% (full acceleration) even without touching the pedal.
Additionally, RevLimitLogic=1 was causing a feedback loop where the software-controlled limiter tried to fight the ghost-throttle, making the car completely uncontrollable.
The Solution
To fix the bug without affecting the Turbo boost or the car's power delivery, we had to "decouple" the engine braking logic from the broken turbo-linked algorithm.
- Switching the Algorithm: Changed EngineBrakingParams to (2, 830). This uses the logic from the Mazda 787B (a rotary/naturally aspirated car in the mod), which calculates engine braking as a linear resistance rather than a turbo-pressure-dependent value.
- Disabling Rev Limit Logic: Changed RevLimitLogic to 0. This forces the engine to use a standard hard-cut limiter, preventing the physics engine from applying "maintenance throttle" that was interfering with the braking maps.
- Adjusting Map Scaling: The original 0.250 increment was a decimal error (25% throttle per step). We corrected it to 0.015 (1.5% throttle per step), which is the standard value to prevent rear-locking during downshifts without causing unintended acceleration.
Result: The car now retains its full Turbo characteristics (1.50 bar boost, lag, and power curve remain untouched), but the throttle mapping is now stable and the Engine Braking Maps work as intended.