I just replied in the Yahoo list, but I try not to do a simple copy / paste.
In my opinion World Machine now does the terrain output correctly, no bug, no issue. Just in another way how we experienced it before in older WM versions. Following the terrain specification, it now does use the full 16 bit. So, I am in doubt if an optional checkbox is a good idea. It would mean a loss of accuracy.
So, letās have a look how the height values are calculated. First important value is Base Height. Second is Height Scale. Following a row of many 16 bit values. Example:
Base Height = 100 (terrain units, not meters)
Height Scale = 30
āManyā 16 bit integers: Range from -32768 ā¦ 32767
For those who are interested to analyze terrain file information, I recommend to download TerrainScout. No, this is not hidden advertisement.
When you open that terrain in Terragen, there will be shown a height range of 70 ā¦ 130 ( = 100 - 30 ā¦ 100 + 30). Terragen always finds a combination of Base Height and Height Scale, whereas World Machine always uses Base Height = 0. Thatās the reason for the discussion here.
Btw, Terragen itself also uses negative values (try generate + canyonize), there is no rule that āforbidsā that.
Apologies to Stephen, it was not my intention to cause such trouble.
- Karsten