@IPACS,
Thanks much for the SDK release. I've tried everything and thanks for the new airport, new aircraft with great visibility, and the sample data read/write application which compiles and executes with VisStudio2015 just fine.
I wanted to add a very simple airport near my home in San Diego (Oceanside Municipal) but I really don't get the web-mercator coordinates. I have used websites and actual C++ code to be able to go from Lat,Lon to web-mercator (and back again) but I can't match the numbers that you used for Kingman objects - Example:
<[tmsimulator_scenery_object][element][0]
<[string8][type][ground]>
<[string8][geometry][kigm_kingman_rwy]>
<[vector3_float64][position][24043.51308231 51802.69537268 0]> <<<<=======
From editing those web-mercator numbers (by 0.1), and then seeing the scenery shift, I see that the units are 100 meters (I think), but when I enter those coords ( 24043.51308231 51802.69537268) * 100.0 into my converters, I get lat,lons which don't make sense to me (shouldn't they be like the lat,lon for Kingman airport (-113, 35)? Also, what is your longitudinal reference point ? Could you please explain these? There must be some scale factors I don't know about.
I am using simple equations like the following that I found - they agree with some online converters:
East = (180.0 + lon) * 20037508.34 / 180.;
North = log(tan((90.0 + lat) * PI / 360.)) / (PI / 180.);
North = North * 20037508.34 / 180.;