Beamng.drive V0.4.2.0 [VERIFIED]

The most noticeable addition for car enthusiasts is the visual and mechanical overhaul of the Cherrier Vivace. In v0.4.2.0, the Vivace receives a complete remaster of its body panels and interior textures. But the real story is the introduction of the Cherrier FCV (Fuel Cell Vehicle).

This electric vehicle variant comes with a hydrogen fuel cell system, simulating realistic weight distribution changes as the hydrogen tanks deplete. Unlike standard BEVs (Battery Electric Vehicles), the FCV maintains consistent power output until the fuel is nearly exhausted. Driving the FCV through the automation-generated traffic in v0.4.2.0 feels distinctly futuristic, complete with a unique high-frequency motor whine that audiophiles will appreciate.

If you own BeamNG.drive on Steam:

For standalone users, log into the BeamNG member portal to download the v0.4.2.0 installer. BeamNG.drive v0.4.2.0

In v0.4.2.0, the UI was HTML/CSS based but less sophisticated than modern versions. We will create a simple overlay.

File: ui/apps/cargoDelivery/main.html

<div id="CargoApp" class="appWindow">
    <div class="title">Commercial Logistics</div>
    <div id="content">
        <div id="status">Status: Idle</div>
        <div id="jobList"></div>
    </div>
</div>
<script>
    // Hook into Lua events
    angular.module('beamngApp').controller('CargoController', function($scope) 
        $scope.jobs = [];
        $scope.status = "Looking for work...";
// Listen for data from the Lua extension
        $scope.$on('JobAccepted', function(event, data) 
            $scope.status = "Transporting " + data.type + " to " + data.endLoc;
        );
$scope.$on('JobListUpdate', function(event, data) 
            $scope.jobs = data;
        );
    );
</script>

The transition from v0.4.1.0 to v0.4.2.0 focuses on three pillars: vehicle dynamics refinement, UI modernization, and world streaming optimization. Let’s look at the headline features. The most noticeable addition for car enthusiasts is

The new Career Mode is brilliant, but it was rough around the edges. Here is what changed:

In v0.4.2.0, triggers were often defined in the mission file or created dynamically. We will define zones on the JRI map.

File: levels/jri/playmodes/trafficLogic.mission For standalone users, log into the BeamNG member

// Define the pickup zone at the Sawmill
new Trigger(SawmillPickupZone) 
    position = "512.5 1024.0 45.2"; // Example coordinates for JRI Sawmill
    scale = "10 10 5";
    polyhedron = "0.0000000 0.0000000 0.0000000 1.0000000 0.0000000 0.0000000 0.0000000 -1.0000000 0.0000000 0.0000000 0.0000000 1.0000000";
    isPolyhedral = "0";
    scriptPath = "art/scripts/cargoTrigger.cs"; // Script to handle entry
;

File: art/scripts/cargoTrigger.cs

function SawmillPickupZone::onEnter(%this, %obj)
// Check if the entering object is the player
    if (%obj.client != 0) // Simple check for player control
// Call the Lua extension
        commandToServer('CheckCargoLoad', "Sawmill");

In v0.4.2.0, the mission system was handled largely through the TorqueScript layer and Lua game logic. We will create a script extension that tracks the player's vehicle location and cargo status.

For years, the UI in BeamNG felt like a holdover from 2013. Version 0.4.2.0 introduces a drag-and-drop UI App Editor that actually works.