Satisfactory’s Update 1.2, released in June 2026 across PC, PlayStation 5, and Xbox Series X/S, ships two transport features that pair naturally: fluid trucks with dedicated fluid stations, and a vehicle pathing system rebuilt from the ground up to work like railways. For engineers who have wrestled with long-distance pipelines across uneven terrain, the combination is a genuine alternative worth understanding before you commit to a build.

What changed

Coffee Stain rebuilt how automated ground vehicles route across the map. The old recorded-path system — where you drove a vehicle once and the game replayed your route — is gone. In its place is a spline-based path system placed with the build gun, modeled on how railways are laid down. You plot a path in segments, complete it into a valid loop, snap truck stations to it, and assign vehicles the way you’d assign a train to a track.

Alongside the pathing rework, 1.2 introduces fluid trucks and fluid stations, a new transport pair for moving liquids. Both the truck and the station have an internal capacity of 3,200 m³, and they unlock through the Tier 5 Logistics Mk.4 milestone. Until now, moving fluids over distance meant pipelines, trains with fluid wagons, or nothing. Fluid trucks add a fourth option aimed at mid-range routes where a pipeline would be expensive or a train would be overkill.

How it works

The new vehicle path system

Paths are built from the Build Menu’s Transport section using one of five path tools, each calibrated to a vehicle’s turning ability: a Universal Path, plus dedicated paths for the Tractor, the Truck (and Fluid Truck), the Explorer, and the Factory Cart. Each path type has a different maximum turn radius — the Truck and Fluid Truck need the widest 180° turns at 18 meters, the Tractor and Explorer manage 8 meters, and the Factory Cart turns at 4 meters. The Universal Path shares the 18-meter truck spec but cannot carry Factory Carts.

A path becomes valid and complete when it forms a loop and turns blue. Intersections show as green. To make the loop usable, you must connect it to truck stations: each station snaps onto the path as a “pause” point marked by a white double vertical line, and the vehicle loads or unloads there depending on how the station is configured. You need a minimum of two stations per path — one to load, one to unload — but can add more.

Paths only place on smooth terrain or foundations. Abrupt height changes — rocks, cliffs, foundation holes — invalidate a section and turn it red, and removing a foundation under an existing path invalidates it. All paths are unidirectional, shown by animated directional arrows, so bidirectional routes aren’t possible; you use Y-split and Y-merge junctions instead, keeping traffic one-way. Path holograms use a color code: yellow for valid-but-unconnected, blue for connected, green for a crossing, red for invalid, and purple for a converted legacy path from a 1.1 save.

Converting older saves

When you load a 1.1 or earlier save, every old recorded route converts into the new path system as a purple “converted legacy path.” Coffee Stain notes that because vehicle physics changed with the engine upgrade in 1.2, converted vehicles show atypical behavior, and the converted paths are un-editable. The studio recommends manually removing them and rebuilding the route in the new system. You cannot create new legacy paths in 1.2.

Fluid trucks and fluid stations

Fluid trucks operate on the same path system as the standard Truck — they use the same 18-meter turn path type. The fluid station pairs with the truck: a station on the supply end fills the truck, a station on the demand end empties it, and the truck runs its loop on autopilot. With 3,200 m³ of capacity on both the truck and the station, a single Fluid Truck can move a meaningful buffer of liquid per trip without the continuous flow a pipeline requires.

Vehicles run pathfinding per vehicle, always seeking the shortest route to the next stop. If you add a new path section that shortens a vehicle’s route, it takes the shorter path automatically — build order doesn’t matter. Vehicles share a path safely: they slow and brake to avoid the vehicle ahead rather than colliding, and intersections use a priority system where Trucks and Fluid Trucks have the highest priority, followed by Tractors and Explorers using default wait-time logic.

How to build a fluid truck route

A practical setup follows a short, repeatable sequence.

  1. Plan the loop. Pick a supply point (your fluid source) and a demand point (where the liquid is consumed). The route needs to be a closed loop with smooth terrain or foundations the whole way.
  2. Lay the path. Use the Fluid Truck / Truck path tool to build segments from the source to the demand point and back. Watch the hologram color — complete the loop until the section turns blue. Use Default mode for gentle ground curves, or Straight mode for clean 90° corners and straight runs.
  3. Snap the stations. Place a fluid station at the source and one at the destination, snapping each to the path so its pause point sits on the loop. Name them clearly — something like “Heavy Oil (Out)” and “Plastic (In)” — since all stations default to the name “Truck Station” and are hard to tell apart on the map.
  4. Place and assign the truck. Build a Fluid Truck on the path; it snaps automatically. Open the Vehicle UI, select both stations in order, and enable Autopilot.
  5. Connect fluids. Pipe the source into the supply station and pipe the demand station into your consumers. The station buffers 3,200 m³, so it absorbs the gap between truck arrivals.

For longer or steeper routes, remember vehicles slow on inclines, declines, and curves — the steeper or sharper, the slower. Keep main straight sections level for top speed, and prefer short intersection sections so vehicles don’t stop far back from the junction.

What it means for players

Fluid trucks fill a specific gap. Pipelines are the obvious choice for short, direct runs, and trains with fluid wagons remain best for very high throughput over long distances. Fluid trucks land in the middle: routes long enough that a pipeline would burn through resources and build time on supports and pumps, but not so long that a train network is justified. They also shine on uneven terrain where laying a continuous pipeline is fiddly — a path can climb and descend foundations where a pipe needs careful gradient management.

The rebuilt path system matters beyond fluids. Existing automated trucks and tractors benefit from the same spline placement, intersection priority, and blueprints support, so any vehicle route in 1.2 is easier to plan, place, and modify than the old recorded-path approach. Paths can be embedded in blueprints (with or without foundations), and blueprints auto-connect on placement, so a standardized “fluid truck highway” can be templated and stamped across a factory.

There are real trade-offs to weigh. A fluid truck’s 3,200 m³ arrives in discrete trips, not continuously like a pipe, so your downstream consumers need a buffer or a tolerance for intermittent supply — the station’s own 3,200 m³ helps here. Unidirectional paths mean every route needs a return loop, which costs more footprint than a single pipeline. And the one-way restriction means a busy two-way corridor needs parallel paths in each direction, not a single shared road.

Platform notes

1.2 launched simultaneously on PC, PlayStation 5, and Xbox — the first major Satisfactory update to do so. Console players get improved controller support, including dynamic gamepad swap and rebindable inputs. PC players on Steam Deck should note community reports that the new weather effects can cause slowdown on the device; the weather frequency and intensity are adjustable, and the effects can be switched off entirely. The update also adds a real single-player pause menu, daisy-chain power connectors (via Caterium research), Pipeline T-Junctions, and the SPWN cubicle spawn point.