Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
Russel,
Nice progress! I still find it unbelievable that this is a Java application.
Is it already possible to move the Airport Reference Point? If so, how do I do it?
Cheers,
Martin

Thanks! Why the surprise at it being a Java app? (just curious)
Regarding the ARP - I like to see if overlays are working the same way as before. What I meant with my question was if there is any way to drag the visual ARP marker to another point; comparable to how you could do that in AFCAD. [ I bet you and Jon probably hate this "like in AFCAD...]
Cheers,
Martin

When you drag the reference point, would that move the entire airport?


One thing that can make working with overlay airports tricky has to do with a quirk of the Flight Simulator ATC. If you program the AI to use separate overlays, they will land on the appropriate runway for the overlay they are assigned to, but once on the ground the AI will contact the ATC ground control at the closest airport for taxiing and parking instructions. At a normal airport there would only be one ATC ground control, and the closest airport would obviously be the one the AI just landed at, but in an overlaid airport there would be two ground controls at the exact same location, so the AI would contact just one of those ground controls. Unfortunately that may not be the ATC in the overlay the AI was programmed to land at, and they would end up going to a parking spot in the 'other' overlay. But worse still, this usually results in all the AI ending up in the same overlay and fighting for all the parking spots in that overlay, which would only be half the parking at that airport.
There is a way to get around this, and that is to move the Airport Reference Point (the pink spiky dot) in the overlay and/or base airport. The AI contact the closest ground control based on the distance to the Airport Reference Point, so if you make sure that the reference point for each overlay is closest to the active runway for that overlay, then the AI will contact the 'right' ground control upon landing, and will remain in the overlay that it was programmed to land in. This works well for airports with parallel runways like KLAX or KATL, where you can easily move the reference point closer to the appropriate active runway, but that may not be easy to achieve at airports with crossing active runways.
Moving the reference point by either dragging it or by entering new coordinates would have the effect of repositioning where FSX thinks the airport actually is, even if everything in the airport stayed in its original location. I haven't tested this but would think that is what would happen.