At first time it worked sometimes, but not now. I get CTD alltimes with message in a small window "Error in Transopmesh". In the OGLA.log the same error message many times.
Could you post the ogla.log and your system specs?
Does it fail in any specific scenario?
Does it fail with all non-essential graphic options off (
http://orbides.1gb.ru/orbf/ogla_failsafe.png )?
Does it fail on clean Orbiter install?
Mapped shadows are the main framerate killer, with this option I'm around 25-30 FPS, also terrain generation is much slower.
Mapped shadows haven't been updated or improved for a while. Never the less, they are supposed to be the fastest of available options.
The terrain is considered an obsolete feature and is unmaintained for the moment. It badly needs redesigning, no idea when i get to it.
I still don't get how to use height maps though... I've noticed where you have to enter their path in the Config\Terrain folder, but I've no idea of which format to use or where to get those files.
That's a problem. The system was designed to be used with an external editor, know as World Studio. However that editor, dating back to Orulex, was never done to a point where you can arbitrarily edit the planet surface, and only worked as data downloader and converter for NASA servers data.
But even this got scrambled over the years, and i'll have to rewrite it completely now.
Let's see the code of the heightmap, which can be a grayscale bitmap or a signed word array with dword coordinates at start:
Code:
//O-operator, 0=add, 1=multiply, 2=replace, 3=add&truncate ocean; F-flag, 1=truncate <0; U=use flag, 1=use
//heightmap =--------------file name-----------------|lower lat|upper lat|west lon|east lon| scale |O|F|U
heightmaphei=moon-lv12-1038-301-3-3 |-000000005|-0004.0625|+0324.3750|+0325.3125|00032768|2|0|1
heightmaphei=moon-lv12-1038-301-3-3 |-000000005|-0004.0625|+0324.3750|+0325.3125|00032768|2|0|1
heightmaphei=moon-lv12-1038-301-3-3 |-000000005|-0004.0625|+0324.3750|+0325.3125|00032768|2|0|1
All fields are
fixed length
moon-lv12-1038-301-3-3 - the file
Then, latitudes of lower and higher lines of the map, west and east longitudes of the left and right sides, vertical scale (maximum of bitmap assumed to be one, and multiplied by that), and some flags:
O-operator, 0=add to existing definitions or global map, 1=multiply '--', 2=replace existing definitions, 3=add like in 0 and truncate ocean(<0 parts)
F-flag, 1=truncate under the Orbiter sphere part of the map
U=use flag, 1=use, 0 - unused.
If i'm not mistaken, it's all documented as comments in the discussed cfg files.
hei files are a simple thing - 4 bytes X resolution, 4 bytes Y resolution, signed 2 bytes altitude, in latitude lines east to west, lines going north to south (standard raster).
Only existing way to make them from non-NASA data is to do it yourself, i'm afraid.
