Two-Step and Launch Control

Two-Step gives an installed vehicle a configurable RPM launch window, synchronized exhaust bursts, and optional launch assistance. Launch Control can hold the vehicle, limit torque while it is staged, and blend the configured torque back in when the brake is released.

Enable and install the feature

Two-Step has a global feature switch, a deployment-wide runtime switch, and a saved state for each vehicle. All three layers must allow the feature:

1. Open /jobconfig, select Mechanic Jobs, open Features, and enable Two-Step.
2. Keep Config.TwoStep.enabled = true in sky_mechanicjob/config/adv_config.lua.
3. Open a tuning session for the vehicle and select ECU & Vehicle Electronics → 2-Step → Enabled.
4. Complete the tuning order and install its required part.

The default tuning profile prices twostep_enabled through the normal tuning-price configuration and requires one ecu_tuning_kit. Change its price, availability, or required items under Tuning Prices in /jobconfig just like any other tuning option.

The installation and enabled state are persisted with the vehicle. Disabling the global feature hides the tuning option and stops its runtime without deleting saved vehicle data.

Use Two-Step

With the shipped keyboard controls, the driver stages the vehicle by holding:

• W + S when useFootBrake = true
• W + Space when useHandbrake = true

When both brake inputs are enabled, either combination can arm Two-Step. The equivalent configured vehicle controls can also be used on a controller.

The feature activates only when every condition below is met:

Gear 0 is intentionally included because some vehicles report neutral while stationary. Holding the input combination starts the responsive frame loop immediately, but exhaust bursts and Launch Control are applied only after the speed, gear, and RPM conditions also pass.

To launch, keep the throttle held and release the selected brake input. When Launch Control is enabled, the forced handbrake is released and the launch torque blends back to the vehicle's normal configured torque over releaseRampMs. Releasing the throttle as well cancels the ramp and clears the temporary launch modifier.

Open configuration

The complete deployment-wide configuration is stored in sky_mechanicjob/config/adv_config.lua:

Config.TwoStep = {
    enabled = true,
    defaultEnabled = false,
    useFootBrake = true,
    useHandbrake = false,
    inactiveCheckIntervalMs = 125,

    maxSpeedKmh = 25.0,
    minGear = 0,
    maxGear = 2,
    rpmWindowMin = 0.08,
    rpmWindowMax = 0.95,

    burstIntervalMinMs = 55,
    burstIntervalMaxMs = 115,
    flameDurationMs = 130,
    flameScaleMin = 0.7,
    flameScaleMax = 1.8,
    defaultFlameScaleLevel = 10,
    defaultVolumeLevel = 8,

    turboPressureSpikeEnabled = true,
    turboPressureSpike = 28.0,

    launchControl = {
        enabled = true,
        holdHandbrake = true,
        rpmTarget = 0.72,
        holdTorqueMultiplier = 0.12,
        releaseRampMs = 90,
        releaseTorqueStartMultiplier = 0.9
    }
}

Changes made to the Two-Step feature switch in /jobconfig are sent to connected clients immediately. Restart sky_mechanicjob after editing the static values in adv_config.lua.

Availability, input, and activation

At least one of useFootBrake and useHandbrake must be true. If both are false, no input can arm the feature.

Use 100–150 ms as a practical starting range for inactiveCheckIntervalMs. The shipped 125 ms value keeps idle work low while remaining responsive. A value of 50 ms gives faster initial recognition; values closer to 250 ms trade noticeable input delay for fewer idle checks.

Bursts, flames, and turbo pressure

Nearby players receive synchronized backfire bursts. Custom vehicles still need suitable exhaust bones for flames to appear in the expected location.

Launch Control

Launch Control and installed ECU engine tuning share the same torque coordinator. Their multipliers are combined, so staging and release do not erase the vehicle's ECU tune.

Tuning guidance

Change one group of values at a time and test it on stock vehicles and every custom handling class used by the server:

1. Set the speed, gear, and RPM activation window first.
2. Choose an rpmTarget inside that window.
3. Adjust holdTorqueMultiplier until the vehicle stays controllable while staged.
4. Tune releaseTorqueStartMultiplier and releaseRampMs together for the desired launch response.
5. Balance burst cadence, flame size, volume, and turbo pressure last.

For a tighter standing launch, reduce maxSpeedKmh, keep minGear = 0, use a low maxGear, and narrow the RPM window around the desired target. For broader compatibility with custom transmissions, keep the shipped gear range and first confirm which gear each vehicle reports while stationary.

Aggressive pressure, torque, or release values can react differently with custom handling files. Another resource that writes vehicle torque, RPM, or handbrake state every frame can also override Launch Control and should be tested or integrated explicitly.

Troubleshooting

Testing checklist

1. Install and enable 2-Step through a complete tuning order.
2. Confirm throttle by itself and brake by itself do not start the responsive frame loop or effects.
3. Hold the configured combination and verify activation only inside the speed, gear, and RPM window.
4. Release the brake while keeping throttle held and verify the configured torque ramp.
5. Release both controls and confirm the launch modifier clears immediately.
6. Repeat with Launch Control disabled and confirm bursts remain but vehicle hold and torque control stop.
7. Store and retrieve the vehicle and confirm its installed and enabled state persists.
8. Observe the test from a second nearby client and verify synchronized sound and flames.
9. Test stock, custom-handling, manual-transmission, and controller-driven vehicles used by the server.
10. Temporarily disable Two-Step in /jobconfig and confirm the running client stops the feature without a resource restart.

Related pages

• Performance Systems
• Tuning and Orders
• Configuration
• Inventory Items
• Troubleshooting