- May 31, 2020
- Reaction score
I guess it is a factor of two, and the cause is that I used 0.5 m vertical resolution for the elevation. The non standard scales are handled correctly only by Orbiter2016 Beta. Currently it is only a recommendation in the documentation, so I think I should modify it to clarify that this setup is practically a requirement for the proper usage of the elevation maps. If you read back some earlier posts here, you'll see that it is a recurrent problem, however the only help I'd able to provide is to degrade the vertical resolution of the elevation maps. But I'm reluctant to do so, because 1. it looks uglier (especially with the lack of terrain smoothing in the standard Orbiter), 2. it would meant the task for me to manage one additional package for each landing site, just to be compatible with some more or less obsolete Orbiter versions. Using the cutting edge setup of Orbiter beta (and the strongly recommended D3D9Client) comes with no cost, so why not to do that?I just tried it and for some reason, my terrain seems to be enlarged on the z-axis (vertically) by a factor of maybe two or three? Not sure what I did wrong, just installed the files as mentioned in the doc.
Here's some screenshots, the elevation of the surrounding look exaggerated.. hmm..
Also, please don't forget to set "ElevationResolution = 0.5" and "MaxPatchResolution = 18" in the Moon.cfg file(s), but forgetting to do so will result in only a lower quality display, not this exaggerated elevation problem.