Gaea vs SimpleXTerrain

Gaea is a Windows terrain design application for VFX, games, and virtual production. It builds terrain from procedural forms, imported data, or hand-drawn elements, then applies simulations for erosion, debris, glaciers, rivers, snow, and vegetation. It can produce terrain-aware color, textures, masks, material zones, vegetation data, and flow maps. Exports include heightfields, meshes, point clouds, textures, masks, and other terrain data. Bridges connect Gaea with Unreal Engine and Houdini; the Gaea2Houdini plugin requires a Professional or Enterprise license. Gaea also offers node-based compositing and a hybrid render engine.

The Community Edition is free for non-commercial use. The listed perpetual-license prices are $99 a month for Indie, $199 a month for Professional, and $299 a month for Enterprise; each is described as a one-time price. Gaea requires Windows, an AVX2-capable CPU, and at least 16 GB of RAM. CPU-only operation is supported; GPU compute needs CUDA 12.5 or higher or HIP 6.0 or higher.

SimpleXTerrain is a free, MIT-licensed addon for procedural terrain generation in Godot 4 .NET using C#. Its node graph editor defines heightmaps, biomes, splatmaps, and scattered instances. Heightmap sources include Perlin, fractal, and Voronoi noise, radial shapes, splines, and images. Modifiers include levels, curves, slope masks, hydraulic and thermal erosion, terraces, beaches, ledges, and blur.

At runtime, the addon evaluates terrain chunks asynchronously on .NET background tasks around a moving camera, then streams heightmaps and control maps into Terrain3D regions. The documented workflow uses a Terrain3D node with a camera or character attached to a terrain streamer to build Godot scenes. Requirements are Godot Engine 4.6 or later in its .NET or Mono edition, .NET SDK 8.0 or later, and the Terrain3D plugin. Setup involves copying the addon into the project’s addons directory, rebuilding the C# solution, and enabling the plugin in Project Settings. Foliage and object scattering can generate placement data, but the feature is experimental. Some GPU-capable work has RenderingDevice compute helpers; the documentation identifies CPU evaluation as the reliable path.