Import Guide

Requirements

  • Unity 6000.0.80f1 or newer
  • Universal Render Pipeline (URP)

Installation

Install via Unity Package Manager:

  1. Open Window => Package Manager
  2. Import the package (method depends on distribution - Asset Store, scoped registry, or local)
  3. Dependencies are installed automatically: com.nwh.common, com.nwh.wheelcontroller, InputSystem, URP

Setup

Build Profile

Choose the intended platform through File > Build Profiles. The package's declared Input System dependency does not impose a package-wide 64-bit requirement.

Assembly Definitions

The package assemblies are auto-referenced. Scripts that compile into Unity's predefined assemblies (for example, Assembly-CSharp) need no manual assembly references.

If your scripts are in a custom assembly definition and use Vehicle Physics, Wheel Controller, or Common types, add the corresponding assembly references to that .asmdef:

"references": [
    "NWH.VehiclePhysics2",
    "NWH.WheelController",
    "NWH.Common"
]

Do not delete package assembly definitions. NWH.WheelController3D is a C# namespace, not the Wheel Controller assembly name.

The setup wizard is in its own auto-referenced assembly. A custom assembly that calls VehicleSetupWizard must also reference NWH.VehiclePhysics2.SetupWizard.

Importing Samples

Important

Import NWH Common Package > Common Base Sample first for the Base, Mobile, and Multiplayer samples. The Direct Input FFB Sample includes its own demo assets and needs only the Unity-DirectInput dependency.

Import Order

  1. Package Manager => NWH Common Package => Samples => Common Base Sample (import first)
  2. Package Manager => NWH Vehicle Physics 2 => Samples => Base Sample (import second)
  3. Import additional samples as needed (Mobile, Multiplayer, etc.)
Note

Samples are in Package Manager under the "In Project" tab, not "My Assets".