Mobile Setup

01Quick Start

1. Switch the build platform to Android or iOS. RCC turns Mobile Controller Enabled on for you (see Platform Switching & Warnings).
2. Add the canvas: Tools → BoneCracker Games → Realistic Car Controller → Create → UI → Add RCC Canvas To Scene.
3. Open Tools → BoneCracker Games → Realistic Car Controller → Edit RCC Settings, expand Controller Settings, and pick a Mobile Controller Type.
4. Press Play. The touch controls work with the mouse in the Editor.
5. Build.

While Mobile Controller Enabled is on, RCC takes throttle, brake, steering, handbrake and NOS from the touch controls only. Keyboard and gamepad input for these is ignored on every platform, including the Editor. Button actions such as lights, gear shifting and camera change still respond to keyboard and gamepad.

Figure 01Open full size ↗

The mobile controls are in Prefabs/UI/RCC_Canvas.prefab. RCC_Canvas (AIO).prefab is the demo launcher menu. It has no touch controls.

02Controller Types

The NOS button appears only when the player vehicle has Use NOS enabled.

Figure 02Open full size ↗

Figure 03Open full size ↗

Figure 04Open full size ↗

Figure 05Open full size ↗

To change the type or turn mobile controls on or off at runtime (for example, from an options menu):

using UnityEngine;

public class MobileOptions : MonoBehaviour {

    public void UseJoystick() {

        RCC.SetMobileController(RCC_Settings.MobileController.Joystick);

    }

    public void SetTouchControls(bool enabled) {

        RCC_Settings.Instance.mobileControllerEnabled = enabled;

    }

}

In Play mode, RCC_Settings.Instance is a copy of the settings asset, so these changes last only for the current session. The asset on disk is not changed.

Changed in V6: turning mobileControllerEnabled on or off at runtime now shows or hides the touch UI immediately.

03Settings

Edit RCC Settings → Controller Settings → Mobile Controller Settings. Fields below the first one are visible only while Mobile Controller Enabled is on.

Figure 06Open full size ↗

The gradual throttle slider does not use Sensitivity / Gravity. Its input is the slider value while touched and 0 when released.

Figure 07Open full size ↗

04Platform Switching & Warnings

New in V6: RCC keeps Mobile Controller Enabled in sync with the build platform.

Figure 08Open full size ↗

• Switching the build platform to Android or iOS turns it on. Switching to Windows, macOS or Linux turns it off. Other platforms (WebGL, consoles) keep your setting. The Console logs each change.
• Building logs a Console warning if the setting doesn't match the platform (a mobile build with it off, or a desktop build with it on). The build never changes the setting.
• Entering Play mode shows a dialog if the setting doesn't match the active build target. The choices are Enable it / Disable it, Ignore for now, and Ignore and don't warn me again. Any build target other than Android or iOS counts as not mobile, WebGL included.
• Ignore and don't warn me again is saved per project. It also stops the automatic sync on platform switch. If you made this choice in RCC 5.x, it is kept. To turn warnings and sync back on, use Tools → BoneCracker Games → Realistic Car Controller → Other → Reset Mobile Controller Warnings.
• If Mobile Controller Enabled is on and the scene has no mobile buttons, the vehicle inspector shows a warning and an Add RCC Canvas button.

On-foot controls in the Enter-Exit addon follow this setting. See Addon Packages.

05Customizing the Canvas

Add RCC Canvas To Scene adds Prefabs/UI/RCC_Canvas.prefab. If the scene already has an RCC Canvas, the command selects it instead. If the scene already has an EventSystem, the canvas's own EventSystem is removed.

The touch widgets are under the canvas's Controller Buttons child:

Figure 09Open full size ↗

The full-screen Drag (Orbit) panel orbits the camera when the player drags on empty screen space.

RCC_MobileButtons on the canvas root shows and hides the widgets every frame to match the controller type. You can move, resize and restyle them freely. Do not activate or deactivate them by hand. To remove a widget, clear its field on RCC_MobileButtons, then delete or deactivate the GameObject.

RCC_MobileButtons

RCC_UI_SteeringWheelController

RCC_UI_Joystick: Background Sprite sets the movement area, and Handle Sprite is the part that moves. Full steering is reached at the edge of the background.

Changed in V6: a quick tap on the steering wheel no longer leaves it turned. The joystick range no longer depends on screen resolution.

The canvas uses a Canvas Scaler in Scale With Screen Size mode, with a reference resolution of 1920 × 1080 and the Expand screen match mode. Change these to fit your target devices.

06Custom Touch UI From Code

To drive RCC from your own touch UI:

1. Keep Mobile Controller Enabled on.
2. Disable the RCC_MobileButtons component on the RCC Canvas, or leave the RCC Canvas out of the scene. RCC_MobileButtons rewrites the inputs every frame and would overwrite yours.
3. Write to RCC_MobileButtons.mobileInputs every frame, before RCC_InputManager (execution order −50) reads it.

using UnityEngine;

// -60 = the order RCC_MobileButtons uses, so RCC_InputManager (-50) reads the values in the same frame.
[DefaultExecutionOrder(-60)]
public class MyTouchInput : MonoBehaviour {

    // Set these from your own UI widgets.
    [Range(0f, 1f)] public float throttle;
    [Range(0f, 1f)] public float brake;
    [Range(-1f, 1f)] public float steer;
    [Range(0f, 1f)] public float handbrake;
    [Range(0f, 1f)] public float nos;

    private void Update() {

        RCC_Inputs inputs = RCC_MobileButtons.mobileInputs;

        inputs.throttleInput = throttle;
        inputs.brakeInput = brake;
        inputs.steerInput = steer;
        inputs.handbrakeInput = handbrake;
        inputs.boostInput = nos;

    }

}

To control one vehicle directly without the mobile pipeline, see How To Override Inputs.

07Performance Tips

In Edit RCC Settings:

Collision sparks are set per vehicle with Use Collision Particles on the vehicle inspector.

To optimize distant vehicles, add RCC_LOD to them. When a vehicle is farther than 50 × Lod Bias meters from the RCC camera, RCC_LOD deactivates its audio sources, particle systems and hood / wheel cameras, and reactivates them when it comes closer. Lod Bias defaults to 2, so that distance is 100 m. Lights and wheels are not affected.

08See Also

• Input System
• How To Override Inputs
• RCC Settings
• Addon Packages
• Troubleshooting