92
« Last post by forum_admin on July 19, 2022, 11:12:19 PM »
Bridge Command uses metres internally, and assumes that binary heightmaps are defined in metres, so as long as the original data is in metres, they should be correct. Please double check the source, but let me know if it still doesn't look right.
For information, from the latest release (5.7.12), there are a few improvements to terrain loading, including directly supporting 3dem 16 bit integer and 32 bit floating point terrain matrix (the 3dem format uses a separate binary map and ascii header file). Additionally, if the heightmap isn't (2^n + 1) square, instead of resizing it, Bridge Command now uses the data directly (it still internally using a 2^n+1 square worldmap, but just picking the next size up, and only using the amount required.)