I do not plan to work in this direction, because, frankly, I do not see great prospects in this direction.
I don't think using Mesh to Terrain is the right way to go in this case.
]]>Hello.
Why this happens and how heightmap works:
Heightmap is just a char array (values 0-65k).
There is a total height of the area, on the basis of which the height multiplier is calculated.
As you know the real world has a different range of heights.
It may seem that 65k values are enough for the real world, but this is not so, and if you say that 1 meter = 1 heightmap step, then you will see a ladder on the terrain.
To work around this problem, terrain generators (including RWT) distribute the range of values of the desired area over the range of heightmap values.
This gives high precision and smoothness to the terrain.
But at the same time, this creates the problem of transferring heightmaps between terrains.
This will only work if the terrains have the same position and size.
In addition, this will create a problem for the RWT API, because it stores the minimum and maximum altitude, and may not work correctly with a different heightmap.To sum it up: when transferring a heightmap, you need to make sure that both tools work the same way, and that the terrains have the same settings. Otherwise it won't work.
Hello, thank you for enlightening me !
The more I understand how maps do work, the more it seems complicated to me :-)
My answer will be short : is there a workaround that would allow me to import 5m resolution heightmaps from RGEAlti in RWT ? When you import heightmaps from a provider, like MapBox or BingMaps, the elevation values are extracted from a raster, to I would need a "converter" if I want to get values from RGEAlti ?
Best regards
Philippe
Why this happens and how heightmap works:
Heightmap is just a char array (values 0-65k).
There is a total height of the area, on the basis of which the height multiplier is calculated.
As you know the real world has a different range of heights.
It may seem that 65k values are enough for the real world, but this is not so, and if you say that 1 meter = 1 heightmap step, then you will see a ladder on the terrain.
To work around this problem, terrain generators (including RWT) distribute the range of values of the desired area over the range of heightmap values.
This gives high precision and smoothness to the terrain.
But at the same time, this creates the problem of transferring heightmaps between terrains.
This will only work if the terrains have the same position and size.
In addition, this will create a problem for the RWT API, because it stores the minimum and maximum altitude, and may not work correctly with a different heightmap.
To sum it up: when transferring a heightmap, you need to make sure that both tools work the same way, and that the terrains have the same settings. Otherwise it won't work.
]]>