Real Car Driver — Custom Physics
Real Car Driver — Custom Physics 4.4.0 Documentation
Start here: your first drive
Using your own four-wheel car? In Collection Mode, assign the body, front-left wheel, front-right wheel and both rear wheels together. Assign your road collection separately, then click Prepare Custom Physics. Suspension meshes and lights are optional. See the part assignments ↓
Trying the demo first? Choose Collection Mode and click Create Custom-Physics Demo Car in a new file. Follow the demo setup ↓
Already recorded? Watch how to edit your recorded path, or jump to recording and export ↓.
Compatibility
- Minimum Blender version: 4.0.0
- Targeted compatibility tests: Blender 4.0, 4.1, 4.2, 4.3, 4.4, 4.5 LTS, 5.0, 5.1 and 5.2 LTS on Windows
- Product version: 4.4.0
Other operating systems have not been separately verified. Compatibility checks are targeted regression tests, not certification of every possible scene.
What the Add-on Does
Real Car Driver provides an independent fixed-step road-vehicle solver for a conventional four-wheel vehicle. Driving Mode operates directly in the 3D Viewport without requiring a Blender rigid-body world or timeline playback. The recording workflow exports an editable drive path in Collection Mode, with native Blender Actions preserving vehicle mechanics. Direct Animation export is also available and is used in Mesh Mode.
The add-on supports:
- Mesh Mode for direct body and wheel mesh assignments
- Collection Mode for vehicles whose visible parts remain separate
- A mesh road or ground in Mesh Mode, or an environment collection in Collection Mode
- Vehicle and simulation-quality presets
- Keyboard or optional analog mouse steering
- Optional automatic transmission and live P-R-N-D controls
- Drive recording, preview, disk save/load, Editable Path export and Direct Animation export
- Optional visual caliper, LED, hazard, brake, reverse, and headlight behavior
- An optional supplied test-road builder
Installation
- Finish any render or Driving Mode session. Use Save Recording for any take you need, and save your Blender file.
- Use a fresh Blender session for the update. Disable the previous Real Car Driver version if installed.
- In Blender 4.2 and newer, open Edit → Preferences → Get Extensions, open the menu and choose Install from Disk. In Blender 4.0–4.1, use Preferences → Add-ons → Install.
- Select real_car_driver_custom_physics_4.4.0.zip without extracting it, then install and enable Real Car Driver — Custom Physics.
- Open 3D Viewport → Sidebar → Car Drive.
Quick Start with the Included Demo
- Open 3D Viewport → Sidebar → Car Drive.
- Press Create Custom-Physics Demo Car.
- Review the assigned car parts and Road / Ground.
- Press Prepare Custom Physics.
- Use Record Driving Mode if the drive should be kept, or Driving Mode for driving without recording.
- Drive with the default controls.
- Press Esc to finish.
- Preview the take if it was recorded.
- Use Save Recording. Choose Export As: Editable Path in Collection Mode, or Direct Animation in Mesh Mode, set the start frame, then press Export Drive.
Preparing Your Own Vehicle
The supported vehicle layout is:
- One body role
- One front-left wheel role
- One front-right wheel role
- One combined rear-wheel role
- One driving surface: a mesh in Mesh Mode or a collection in Collection Mode
The rear-wheel role contains both rear wheels in Mesh Mode. The two rear contact positions are solved independently, while the combined rear-wheel mesh uses one averaged visual spin angle.
Mesh Mode
Use Mesh Mode when the visible setup can be assigned through four direct vehicle mesh roles:
- Assign the visible body mesh.
- Assign the front-left wheel mesh.
- Assign the front-right wheel mesh.
- Assign the combined rear-wheel mesh.
- Assign the mesh road or ground.
- Use Auto Setup or verify the detected vehicle axes.
- Apply a quality and vehicle preset if desired.
- Press Prepare Custom Physics.
Wheel origins may remain offset. The solver derives wheel centers, radii, widths, pivots, suspension mounts, and rear contact positions from evaluated geometry.
Collection Mode
Use Collection Mode when the vehicle must remain made from separate visible objects.
Assign these core role collections:
- Body collection
- Front-left wheel collection
- Front-right wheel collection
- Rear-wheels collection
The rear-wheels collection may contain the two rear assemblies as separate objects. Nested collections and existing internal parent-child hierarchies are supported. Each source object must belong to only one assigned role collection.
Collection Mode creates non-rendering controller geometry for the solver. It does not join or replace the visible source meshes.
Automatic Name Detection
Core collection names recognized by automatic collection detection are:
- car_body
- front_left_wheel
- front_right_wheel
- rear_wheels
In Mesh Mode, Auto Add Car Parts can detect:
- front_left_wheel
- front_right_wheel
- rear_wheels
- ground
A body named car_body is detected when available. Name matching is case-insensitive and accepts spaces or hyphens in place of underscores. Every supported role can also be assigned manually.
Road and Ground
In Mesh Mode, assign a mesh object as Road / Ground. In Collection Mode, assign the environment collection; its nested mesh surfaces provide collision without adding vehicle-style controllers to the environment. A custom road may keep its own topology, materials, UVs, and modifiers. The add-on uses the evaluated mesh for collision and does not rebuild, reshape, or topology-check a custom surface.
The road collision data is prepared before Driving Mode and remains fixed during that session.
After changing the physical road surface:
- Exit Driving Mode.
- Complete the road edit.
- If using the optional test-road builder, allow its live update to finish.
- Press Prepare Custom Physics again.
- Start Driving Mode.
For very large environments, keep distant scenery separate from the driveable collision surface so the road collision mesh remains practical.
Per-Material Surface Response
Road materials can adjust tire behavior with Blender custom properties:
- rcd_surface_grip — grip multiplier, commonly around 0.2 to 1.5
- rcd_surface_rolling — rolling-resistance multiplier, commonly around 0.5 to 4.0
These are optional material properties. If they are absent, the normal road response is used.
Optional Test-Road Builder
Press Create Optional Test Road to append the included author-supplied segmented asphalt test asset with its UV layout, procedural material, and shader groups.
For a road that remains recognized as the generated test road, the panel provides live controls for:
- Length
- Width
- Collision thickness
- Placement
- Smooth left or right turns at measured positions
- Smooth hills or dips at measured positions
Six starting layouts are supplied:
- Straight Test Road
- Circle Circuit
- Oval Loop
- Rounded Circuit
- Technical Loop
- Rolling Hills Loop
The supplied lane paint is visual only. Shader micro-detail does not create physical displacement.
The builder applies only to a road still recognized as the optional generated test road. A user-assigned road, reassigned object, or edited custom surface is treated as custom and is not rebuilt by these controls.
The optional road is a testing aid. It is not required and is not a general production-road generator.
Optional Collection Mode Features
Suspension Mesh Parts: enable the section only when you want visible suspension animation. Assign front-left, front-right and combined rear suspension collections, choose a setup preset matching the modeled mechanism, and use the part pickers to assign each available spring, damper, arm and other supported role. Manual role assignment avoids relying on names alone. Prepared RIDGE Rig is for the supplied RIDGE setup, not a universal preset for other cars. Verify the part assignments and mechanical bump/droop limits, then prepare physics again.
Grass Interaction: assign a grass collection and choose the appropriate normal-mesh or Geometry Nodes workflow. Enable and configure bending for the grass instead of treating it as a solid driving obstacle.
Small Rock Interaction: this optional collection-based feature is disabled by default. Assign the small-rock collection and enable it when rounded tire contact and suspension response over those rocks are wanted. It does not make large obstacles freely passable.
The demo cars and optional canyon environment are testing aids. You can use your own vehicles and environments; neither bundled asset is required. Trailer dust, cinematic cameras and motion-graphic titles are presentation work, not an automatic dust-generation feature of the add-on.
Presets
Vehicle Presets
- Road Car
- Sports Car
- Off-Road
- Drift
Vehicle presets are editable starting points rather than locked modes.
Quality Presets
- Performance — 90 Hz with reduced body-contact workload
- Balanced — 120 Hz and the recommended default starting point
- Maximum Realism — 180 Hz with denser contacts and more collision iterations
Higher settings increase the simulation workload. Actual viewport performance depends on scene complexity and computer hardware.
Portable Profiles
Vehicle tuning can be exported to and imported from JSON. Profiles store scalar physics and presentation settings. They intentionally omit Blender object references and runtime state so they can be reused between files.
Default Driving Controls
Use P-R-N-D Selector is off by default.
- W — forward request
- S — reverse request
- Space — brake
- A / D — steer left or right
- 1–9 — select accelerator power level
- Shift — boost
- B — toggle Brake Hold
- C — set Cruise Control to the current forward speed; press again to cancel
- Shift+C — resume Cruise Control at the stored target
- = / Numpad + — increase the cruise target
- - / Numpad - — decrease the cruise target
- M — toggle optional analog mouse steering
- H — toggle rear hazard-light flashing when the optional rear LEDs are configured
- O / Pause — pause or resume the independent solver
- R — reset to the Driving Mode entry pose
- Esc — exit Driving Mode
Manual braking, Brake Hold, Park, Neutral, Reverse, or an explicit cancellation safely disables Cruise Control.
Optional P-R-N-D Selector
Enable Use P-R-N-D Selector when separate transmission states are wanted:
- P — Park; engine torque is disconnected and brake hold is applied
- N — Neutral; the engine returns to idle without engine torque at the wheels
- Ctrl+D — Drive; W accelerates forward and S or Space brakes
- Ctrl+R — Reverse; W accelerates backward and S or Space brakes
Park applies its firm wheel lock only below the configured Park Lock Speed.
Analog Mouse Steering
Enable Steering → Mouse Steering, then press M during Driving Mode. The pointer is captured inside the 3D Viewport and relative left-right movement becomes a continuous steering target. A/D remains available as a temporary keyboard override.
Mouse-steering response follows the configured full-lock width, center deadzone, response curve, steering speed, and high-speed steering reduction.
Drive Recording and Editable Path Export
Recording keeps the fixed solver sampling cadence. Version 4.4.0 reduces repeated Blender-side work and uses bulk native animation export; performance still depends on the scene and hardware.
- Prepare the car and surface, then start Record Driving Mode.
- Drive and press Esc to finish. Use Preview Recording to check the take.
- Use Save Recording to save a compressed .rcdrec file before closing Blender. Load Recording restores saved takes, including supported older recordings.
- In Collection Mode choose Export As: Editable Path. Choose a timeline start frame and press Export Drive.
- Use Select Drive Path, then Tab for Curve Edit Mode. Save the Blender file after exporting or editing.
Editable Path keeps all captured samples and transfers global translation to a native curve. Recorded body orientation, wheel spin, steering, suspension, calipers and supported lights/material changes remain native Blender Actions. Exported animation does not need a custom playback handler.
This is not a zero-keyframe system. Mechanical animation still needs native animation channels to preserve the recorded performance. Editing the route does not re-simulate tire contact, steering, suspension or collisions; record a new drive when physically correct interaction with changed terrain is needed. Retiming path progress alone does not retime the mechanical Actions—retime the entire take together.
Direct Animation remains available in Collection Mode and is used in Mesh Mode. Its Exact, Balanced and Light options control export reduction. Editable Path uses the captured samples rather than approximate path simplification.
Safety Disk Cache (Extra I/O) is optional and off by default for new setups. Existing saved settings are respected. The active take is held in memory; save it explicitly rather than relying on temporary cache for recovery. The Driving Mode chase camera is not included in exported animation.
Save a copy before editing an exported route: re-exporting for that car rebuilds its route. Existing complex parenting, constraints, drivers or NLA may require Direct Animation. Unsafe path conversion is rejected rather than silently deleting user setup. Use Replace Existing Animation only when replacement is intended.
Optional Calipers and Lights
Calipers
Four optional caliper roles can follow their matching wheel positions:
- Front left
- Front right
- Rear left
- Rear right
Calipers do not receive tire spin and do not affect physics.
LED and Headlight Roles
Optional visual roles include:
- Front-left LED
- Front-right LED
- Front-left headlight placement mesh
- Front-right headlight placement mesh
- Rear-left LED
- Rear-right LED
Front and rear LED emission can be enabled, disabled, colored, and applied to compatible emission materials. Rear LEDs can brighten for braking or reversing and can pulse as hazard lights.
Managed night beams use the dedicated front light meshes for placement and provide color, power, distance, angle, drop, and softness controls. Turning on the night beams does not automatically turn on decorative front LEDs.
These roles are optional and do not change vehicle physics.
Resetting the Setup
Each panel-section Reset restores the settings and object slots owned by that section. Reset Whole Add-on restores all sections and clears car, road, brake, and light assignments.
Exit Driving Mode before resetting or changing physical setup objects.
Known Limits
- One Driving Mode session is active at a time.
- The supported setup is a conventional four-wheel vehicle.
- All-wheel drive and arbitrary wheel counts are not provided.
- Vehicle-to-vehicle rigid-body simulation is not provided.
- This is not a general-purpose Blender rigid-body replacement.
- A custom road is not rebuilt by the add-on.
- Road collision data remains fixed during Driving Mode.
- The optional road builder is a testing tool, not a final production-road generator.
- Scene performance depends on vehicle complexity, road complexity, quality settings, and hardware.
Troubleshooting
Driving Mode does not start
Confirm that the body, front wheels, combined rear-wheel role, and Road / Ground are assigned. Run Auto Setup or check the vehicle axes, then press Prepare Custom Physics before starting Driving Mode.
The car no longer follows an edited road
Exit Driving Mode and press Prepare Custom Physics again. Collision data from the previous physical road shape remains in use until preparation is refreshed.
Test-road controls no longer affect a road
The controls apply only to an object still recognized as the optional generated test road. A reassigned or edited custom surface is intentionally protected from rebuilding.
Automatic assignment misses an object
Use the documented role names or assign the role manually. Confirm that each Collection Mode source object belongs to only one assigned role collection.
A recorded take is missing
Drive Recording must be enabled before or during Driving Mode. Finish the drive with Esc, then use the recording controls to preview, save, or export it.
Viewport performance is low
Start with the Performance or Balanced quality preset. Keep distant scenery separate from a very large collision surface and reduce unnecessary scene complexity.
Product Support
Use the support or message button on the Superhive product page so the request reaches the creator through the Superhive Inbox.
For a reproducible problem, include:
- Proof of purchase
- Blender version
- Operating system
- Vehicle assignment mode
- Vehicle role setup
- Road or ground details
- Exact reproduction steps
- Screenshots
- Visible error text
Support covers installation, add-on activation, vehicle setup, and reproducible add-on errors on supported Blender versions. General Blender training, custom vehicle modeling, and bespoke vehicle tuning are outside the included product-support scope.
Licensing and Included Assets
The readable Python add-on source is distributed under GPL-3.0-or-later. The archive includes the complete GPL text and per-file notices.
The supplied demonstration scene, road asset, documentation, branding, and other non-code material are governed by the separate notices and commercial terms included in the product archive unless a file states another license. Those assets may not be redistributed as standalone products.
Discover more products like this
vehicle physics viewport driving mouse steering driving car-animation Keyframe animation recording car rig suspension vehicle simulator