Version: 2.2.9.0
I an experiencing an intermittent bug with the Height Remap Modifier (not tried the node).
I have a very simple setup using the same imported 8-bit heightmap and no extra processing. I add a Height Remap modifier to the file and then enter a value in metres (in my case, 255m). If I change the Terrain Definition size but keep the exact same aspect ratio, the file’s heightmap terrain should remain consistent as far as I understand.
Most of the time, that is what happens.
However, sometimes after changing Terrain Definition size (same aspect ratio, though), entering the same metre value in the Height Remap modifier gives a clearly different result than before, even though the setup is otherwise identical. In other words, the same input in m can sometimes produce the expected terrain, and other times produce terrain that is obviously far too tall.
What makes this feel like a bad internal state rather than expected behaviour is:
-
restarting Gaea often fixes it
-
deleting and re-adding the Height Remap Modifier often fixes it
-
once it is in the “good” state again, the same metre input behaves as expected across different terrain definition sizes but with matching aspect ratios
One extra detail: after entering a metre value such as 255m, the modifier then displays a converted internal number such as 0.125. The problem is not that conversion by itself, the problem is that sometimes the same metre input seems to be interpreted differently after Terrain Definition changes.
I cannot reproduce it 100% reliably yet, so this is a heads-up rather than a formal repro, but it has caused a lot of confusion and wasted time so perhaps it’s worthy of further investigation. It’s about as simple a node set-up as you can get (file, with a height remap modifier and 8-bit input texture). I’ll continue trying to find a perfect repo, thanks!