Gaea professional and unreal node problems

[TyXanders]

Mmm, you might be mixing a few terms up there, let’s see if I can untangle that.

Gaea + Unreal Node

In Gaea you need the Unreal node for height fields else you can’t export in the resolution Unreal needs ie 2017.
Otherwise it’d follow the usual power of 2 (like 2048)

It’s the node itself that auto levels as a necessity for move high bit depth data down to 16 efficiently and more robust for keeping data intact.

Gaea2Unreal plug-in Vs manual

As for Gaea2Unreal plugin, if you don’t wish to use it then you just need to do the calculations in unreal manually:

Landscape Technical Guide in Unreal Engine | Unreal Engine 5.7 Documentation...

First section - manual calculations

Unreal - Gaea Documentation

Deep dive

Manually Importing into Unreal

[!Note] This is the manual import path for Unreal (no plugins, full control). If you want the faster option, Gaea2Unreal is open source and available on GitHub.[1] Manual is still useful for debugging scale, custom pipelines, or locked-down projects. Manually Importing Gaea Heightmaps into Unreal Engine This guide covers the reliable way to bring a Gaea heightmap into Unreal Landscape with correct scale and height. Gaea works in metres. Unreal works in centimetres. The import works fine w…

In some cases can match the terrain definition so when the unreal node autolevels there is
No difference
see topic

Height Remap option with the Unreal node

Hello, I have a question about using the Height Remap option with the Unreal node. I am currently creating terrains using Unreal Engine and Gaea 2. My workflow is to create a simple terrain in Unreal, export it to Gaea for further editing, and then export it back to Unreal. However, when I connect the Unreal node at the end of my node graph, the terrain height starts to change compared to the original. In the viewport, adjusting the Height Remap values in the Unreal node seems to visually mat…

---

[!warning]
The following isn’t generally the recommended approach

You may resample from a power of two resolution like 2048 to 2017 manually if you want to but it can complicate your workflow and speed morethan the plugin or manual method above due to data retention and increasing errors chance.

In general this would only really be a use case if you have a very unique end result goal.

• Export using the normal mark for export route
• Export as PNG or .r16
• Ensure you’re working space is in 16bit, and linear (Heightfield data isn’t an image!)
• Resample the image size from example 2048 > 2017
• Use Bilinear mode

[!note]

• You will end up with a softener image
• ringing may occur from resampling
• if your Terrain only occupies a low amount of the full 32bit range you might introduce banding and stepping.
• Example
  0.48–0.56 ≈ only 8% of the 16-bit range
  Rather than 100 if it were auto leveled.