Unreal at the Centre: Exporters Out, NVIDIA Alongside

What we are committing to

Earlier this week we proved a real-world terrain pipeline into Unreal: elevation, roads, water and rule-placed trees on a test tile, with Madison data prepared for the first full build. That work only matters if the product story matches it.

Farm Forge authors worlds in Unreal Engine. That is the centre of the platform going forward. Exporters carry routes, terrain and scene data into other programmes when a project needs them — including Farming Simulator pipelines — so work is not trapped in one editor. Beside that sits the company’s NVIDIA Inception commitment: OpenUSD scene exchange, Omniverse / Kit material, and the longer RTX-aware path.

What this is not

This is not a claim that every exporter ships today, or that every Omniverse viewport path is finished. It is a direction lock. The routing alpha, project files and early USD stage remain demonstrated foundations. Broader environment modules and full exporter coverage still have to earn their place on Madison.

Personal map-making tools for existing games stay separate from the Farm Forge product core. Game-specific work travels through exporters and adapters, not by turning Farm Forge into another editor clone.

Public page, same rules

The Farm Forge Technologies page now says the same thing in plain language: Unreal at the centre, exporters outbound, NVIDIA alongside, Madison as the proving ground. No public release date. No overclaim on unfinished modules.

What comes next

Consolidate the Unreal-centred project into one canonical build path. Strengthen the routing and terrain loop. Harden OpenUSD export on the NVIDIA path. Grow exporter coverage only where Madison proves the result is worth keeping.