Quite nice. Do you keep a terrain type function? Or, is there an easier way to figure out what terrain there is in color function?
No, the crater world plugin keeps maps of color and altitude (like other plugins), and additionally a hidden map that contains the age of the terrain. It also keeps a list of craters, which is basically vector data, while the maps are bitmap data. The craters are drawn onto the color, altitude and age maps each time a new level of detail is generated.
(Yes, sources found, no, not easy to read).
I have the same problem
, which means that something will need to be rewritten in the future, to clean things up. For the crater world code, you can limit yourself to the plugins/ccrater* files, and interpret them with help of the libProcTer API documentation.
Why oapiCameraGlobalPos doesn't work?
I guess it does. Thanks for giving me the name of the function, so that next time I look for it I know I can find it in this thread. OTOH, I can imagine some issues with the accuracy of a global position w.r.t. the surface of e.g. a moon of Neptune. And maybe vessel-relative is better after all.
D3D7 or OGLA graphic clients have the code.
I don't have a D3D SDK (do I need it?). I think I'll first look into the OGLA code, and hope it is compatible with my 'GPL+exception' license.
Why Mercator? It have singularities.
I already explained before, and I know it's a bit controversial choice. Basically:
- It only has two singularities
- which can be made arbitrarily small
- All tiles at the most detailed level are square
- It's easy to make good storage/resolution trade-offs for tile data on disk
- Besides the poles, there are no extra boundary cases to account for, such as edges and corners in a cubic projection The parent/neighbor relations are extremely regular.