How to Install RCC

This document walks you through importing RCC into a Unity project, installing the dependencies, and making sure everything compiles. By the end you should have a project that runs the included demo scenes without errors.

If you've never imported a Unity Asset Store package before, this document also explains how the Asset Store flow works.

Before You Install

Pick a Unity Version

RCC supports Unity 2022.3 LTS and newer, including all 2023.x versions and Unity 6.x LTS. Older versions (2021 and earlier) are not supported because RCC depends on the modern Input System package and a few Unity APIs introduced in 2022.

If you don't have Unity installed, install the latest Unity LTS release from the Unity Hub. LTS releases are the most stable — they receive bug fixes and security patches for two years.

New Project or Existing Project?

You can import RCC into a brand-new project or into an existing project. Both work fine. If you're new to RCC, we recommend creating a fresh project first so you can drive the demo scenes without anything else in the way.

To create a new project: open Unity Hub → New Project → 3D (Built-in Render Pipeline) template → name it something like RCC_Test → Create.

You can also start with the URP or HDRP templates if you know you'll be using those — RCC supports all three pipelines. See 22 — URP & HDRP Conversion for pipeline-specific notes.

Dependency Packages

Before importing RCC, install one dependency through the Unity Package Manager. RCC uses Unity's official Input System package — the old Input.GetAxis() style input is not supported.

Installing the Input System

1. In Unity, open the menu Window → Package Manager.
2. In the top-left of the Package Manager window, change the dropdown from "In Project" to "Unity Registry".
3. In the search box, type Input System.
4. Click the package called Input System (its identifier is com.unity.inputsystem).
5. Click the Install button on the right side. Wait for the install to finish.

Unity will display a dialog asking:

"This Project is using the new Input System package but the native platform backends for the new Input System are not enabled in the Player Settings."

Click Yes to enable the new backends. Unity will restart the editor. This is required — RCC does not work with the legacy Input Manager.

After the restart, you can verify the Input System is active by opening Edit → Project Settings → Player → Other Settings and confirming that Active Input Handling is set to either Input System Package (New) or Both.

Why Both Input Handling?

Some Unity built-in scripts (like the EventSystem in UI Canvases) still expect the old input manager. Setting Active Input Handling to Both lets the old API silently coexist with RCC's new-input-system code, which avoids confusing errors in third-party assets that haven't migrated yet. If you don't have any such third-party code, "Input System Package (New)" alone is fine.

Importing the RCC Package

From the Asset Store

1. Buy or "Open in Unity" RCC from the Unity Asset Store in your browser.
2. In Unity, open the menu Window → Package Manager.
3. In the top-left of the Package Manager window, change the dropdown to "My Assets".
4. Find Realistic Car Controller in the list. Click it.
5. Click Download (if you haven't yet), then Import.
6. The Import Unity Package dialog appears showing every file in RCC, all checked.
7. Click Import at the bottom-right. Wait for the import to complete — typically 30–60 seconds depending on your machine.

From a Local .unitypackage File

If you received RCC as a .unitypackage file directly (for example, from a backup):

1. In Unity, open the menu Assets → Import Package → Custom Package…
2. Navigate to the .unitypackage file and select it.
3. The Import Unity Package dialog appears. Click Import.

What Gets Imported

After import, the following appears in your project:

• Assets/RealisticCarControllerV4/ — all RCC scripts, prefabs, scenes, textures, materials, audio, and documentation.
• Optionally Assets/TextMesh Pro/ if the dashboard requires it and you don't already have TMP installed.

RCC does not add anything outside the RealisticCarControllerV4 folder, so it's easy to remove the package later by deleting that one folder if you ever need to.

First-Time Setup

After import, RCC runs an automatic setup pass that does the following:

1. Welcome window — opens automatically on first import. It shows the version number and quick links to the documentation, demo scenes, and the welcome scene.
2. Layer setup — RCC adds three custom physics layers to your project: RCC_Vehicle, RCC_WheelCollider, RCC_DetachablePart. These are used to make sure wheel colliders don't collide with the vehicle body and that detachable parts behave correctly. The layers are added with LayerMask-safe slots so they don't overwrite any existing layers in your project.
3. Scripting symbols — RCC adds BCG_URP or BCG_HDRP to your Scripting Define Symbols if you're using URP or HDRP. This happens automatically when you run the Render Pipeline Converter (see 22 — URP & HDRP Conversion) — not on initial import.

If the Welcome window doesn't appear automatically, you can open it manually at any time: Tools → BoneCracker Games → Realistic Car Controller → Welcome Window.

Verifying the Installation

The fastest way to confirm RCC works is to open a demo scene.

1. In the Unity Project window, navigate to Assets/RealisticCarControllerV4/Demo Scenes/.
2. Double-click RCC_City.unity to open it.
3. If Unity asks you to save your current scene first, save it.
4. Press the Play button at the top of the editor.

You should see a vehicle in a small city environment with a working camera, working speedometer in the corner, and the engine running. Use WASD or the arrow keys to drive. Press C to cycle through camera modes.

If this works, you're done. Skip to 03 — First Look to learn what each folder contains, or jump to 05 — Quick Start to start building your own scene.

Common Installation Problems

"Assets/RealisticCarControllerV4/Scripts/...cs(line): error CS0246: The type or namespace name 'InputAction' could not be found"

You skipped the Input System install step. Open the Package Manager and install the Input System package. After installing, Unity will ask to restart — click Yes.

"All compiler errors have to be fixed before you can enter playmode!"

There are still compile errors. Open the Console window (Window → General → Console). Look at the first error in the list. If it mentions InputAction, InputActionAsset, or anything starting with UnityEngine.InputSystem, it's the Input System issue described above.

If the errors reference scripts you don't recognize (something like RCC_PhotonNetwork.cs or RCC_EnterExitVehicle.cs), you may have an older version of RCC with the removed addon scripts still present. Delete the folders Assets/RealisticCarControllerV4/Scripts/Photon PUN 2/, Assets/RealisticCarControllerV4/Scripts/EnterExit/, and Assets/BCG Shared Assets/ if they exist.

"RCC_Settings.asset is missing"

This usually means the import didn't finish. Close Unity, delete the Library/ folder in your project root, and reopen the project. Unity will rebuild its cache and the asset should appear in Assets/RealisticCarControllerV4/Resources/RCC Assets/RCC_Settings.asset.

Vehicle in the Demo Scene Doesn't Move

Open Edit → Project Settings → Player → Other Settings and check Active Input Handling. If it's set to Input Manager (Old), change it to Input System Package (New) or Both, and restart the editor. The Input System dialog described earlier may have been dismissed without enabling the backends.

Pink Materials / Missing Textures

This is a URP or HDRP issue. RCC ships with Built-in Render Pipeline materials by default. If you imported it into a URP or HDRP project, the materials will appear pink because their shaders don't exist in the new pipeline. The fix is to run the Render Pipeline Converter:

1. Switch your project to URP or HDRP first via Package Manager.
2. Then run Tools → BoneCracker Games → Realistic Car Controller → Render Pipeline Converter.
3. Click Convert to URP or Convert to HDRP depending on your project.

See 22 — URP & HDRP Conversion for the full procedure.

What Doesn't Need to Be Installed

The following are not required:

• NGUI — was supported historically but is optional. Set RCC_Settings.uiType to UI (the default) for the standard Unity UI dashboard.
• Photon PUN 2 — was supported via a separate Photon Integration Addon but removed in V5. RCC no longer ships any Photon code.
• BCG Shared Assets / Enter-Exit — was supported via a separate addon but removed in V5. RCC no longer ships any character or enter/exit code.
• DOTween, Cinemachine, Post Processing — RCC does not depend on these. You're free to add them yourself if your game uses them, but RCC will work without any of them.

Updating from an Older RCC Version

If you're upgrading from RCC V4.x to V5.2.0, back up your project first (Git commit, or copy the whole project folder).

1. In the Project window, right-click Assets/RealisticCarControllerV4/ and delete it.
2. If you also have Assets/BCG Shared Assets/, Assets/Photon/, or any folder added by the old addon packages, delete those too.
3. Import the new V5 .unitypackage cleanly.
4. Open the Console and resolve any remaining compile errors (typically references to removed addon scripts in your own game code).

You do not need to reconfigure layers — RCC's layer setup runs again on import and adds the layers if they're missing.

Next Steps

After a successful install, go to 03 — First Look to learn what each folder contains, or skip directly to 05 — Quick Start to put a vehicle into your own scene.