Elevated Tracks, Pillars and Supports in Satisfactory

Running anything across the map means crossing ground that is never flat. The tools for this are cheap and unglamorous, and using them properly is the difference between a rail line that took an hour and one that took an afternoon.

Build on foundations, not on terrain

This is the single decision that matters. Track and belts laid directly on the ground follow every bump, which produces gradients you did not intend and, on rail, the runaway train problem on long descents.

Track laid on a foundation is level, predictable, and easy to extend. The concrete cost is real but small compared to the time spent fixing a line that follows the landscape.

The same applies to vehicle paths, where terrain-following routes are the main cause of vehicles drifting off course.

The global grid does the alignment for you

Foundations snap to a world grid shared across the entire map. Two structures built kilometres apart line up with each other without any effort on your part.

The practical consequence: if you lay your first foundation at a sensible height and orientation, everything you build later inherits that alignment. If you lay it at an arbitrary angle, you fight it forever.

Worth doing deliberately at the start of any large project rather than discovering it halfway.

The support pieces and what each is for

Pillars hold a foundation up where the ground has dropped away. They stack, and they come in variants sized to different gaps. This is the standard answer for a platform crossing a valley.

Conveyor and Pipeline Supports hold belts and pipes at a set height without needing a foundation underneath. Cheaper than foundations for a long straight run where you do not need a walkable surface.

Stackable supports extend upward in increments, which is how you get a belt line over a cliff without building a foundation tower.

Frames and Walkways give you a surface to walk on alongside a belt run. Worth adding on any line you expect to maintain, because tracing a fault along a belt you cannot walk beside is unpleasant.

The general rule: foundations where you need to stand, supports where you only need to carry something.

Crossing a valley

Three approaches, in increasing order of effort and quality:

Follow the terrain down and up. Fastest, worst outcome. Creates gradients, and on rail creates the braking problem.

Bridge it with supports. Stackable supports from the valley floor carrying a belt or pipe straight across. Cheap, effective, and fine when nothing needs to walk there.

Bridge it with foundations on pillars. Most expensive, and the only one that gives you a surface to build on, walk along, and extend later. For a main line between two factories this is usually worth it.

Clearance heights that matter

Build with these in mind and you will not have to redo things:

• A standing pioneer needs about 1.8 m. Anything lower means crouching every time.
• Vehicles need considerably more, and a vehicle path under a low bridge will simply stop working.
• Trains need clearance above the track for the locomotive and cars.

The cheap habit: when bridging over something you might later want to drive or walk under, add a foundation level of headroom beyond what looks necessary. Raising a finished bridge is far more work than building it one level higher in the first place.

Building into hillsides

Foundations clip into terrain without complaint. You can bury half a structure inside a hill and it functions normally — only the visible faces matter.

This is often better than building around an obstacle. A factory floor cut into a slope is level, stable, and looks deliberate, where a platform perched on pillars beside the same slope looks like an afterthought.

There is no terrain deformation in this game, so cutting into a hill means placing foundations that intersect it rather than excavating anything.

Blueprints for repeated segments

Once you have a bridge or elevated run you like, the Blueprint Designer lets you save the segment and stamp it repeatedly. For long runs this saves substantial time and, more importantly, keeps the geometry identical along the whole length.

Since 1.2, vehicle paths can be included in blueprints as well, so a standard road segment with its path is repeatable as one unit.

Setting a height standard early

A habit that pays off across an entire playthrough: decide on one or two standard heights and use them everywhere.

Pick a foundation height for your main factory floor, and a second, higher one for long-distance belt and rail runs. Every new structure then snaps into a system that already exists, and lines from different projects meet at the same level without adjustment.

The alternative — choosing a height per project based on whatever the terrain suggested that day — produces a factory where every junction between two areas needs a ramp or a lift to reconcile them. Those adjustments are individually trivial and collectively a large amount of wasted time.

Running power alongside

Power lines follow the same routes as your belts and track, and it is worth running them together rather than separately.

Power poles can be placed on foundations, which means an elevated line carrying a belt can carry power along the same supports. This saves poles, keeps the route tidy, and means a new outpost at the far end has power the moment the belt reaches it.

Street lights support up to two power line connections each, so on a route you will walk or drive along, lights can double as the power run itself.

Common mistakes

Laying track on raw terrain to save concrete. The gradients cost more later than the foundations would have.

Setting your first foundation at an arbitrary angle. Everything after inherits it.

Building bridges at minimum clearance. You will want to drive under it eventually.

Using foundations where supports would do. A belt run that nobody walks beside does not need a floor.

Not walking your own lines. If you cannot get alongside a belt, you cannot diagnose it.