If you want a "consultant" on Orbiter base making, I'm more than willing to help. You can contact me at [email protected] (FYI, I'm the developer of OBM)
First tip: read the PDF files that come with Orbiter that describe how to make bases and customize universes, if you haven't already.
Second tip: use a data type for different units/frames of reference. I.e. have a "Meters" class (that is actually a double) for "meter" units. Expand on that and have a "MeterPoint" class that has x,y,z variables that are Meters; for coordinators. Now have a "MousePoint" class that also has x, y, z, and a function that converts MousePoint to MeterPoint. Have "LonLatPoint" class (longitude, latitude if that wasn't obvious), and more functions for convertion. The screen will use MousePoints, and the base objects will use MeterPoints from a reference LonLatPoint (the base position).
Trust me, if you do that, and find out how many errors it prevents, you will data type EVERYTHING.
First tip: read the PDF files that come with Orbiter that describe how to make bases and customize universes, if you haven't already.
Second tip: use a data type for different units/frames of reference. I.e. have a "Meters" class (that is actually a double) for "meter" units. Expand on that and have a "MeterPoint" class that has x,y,z variables that are Meters; for coordinators. Now have a "MousePoint" class that also has x, y, z, and a function that converts MousePoint to MeterPoint. Have "LonLatPoint" class (longitude, latitude if that wasn't obvious), and more functions for convertion. The screen will use MousePoints, and the base objects will use MeterPoints from a reference LonLatPoint (the base position).
Trust me, if you do that, and find out how many errors it prevents, you will data type EVERYTHING.