I have a simple example piece of code injecting 3 plan files via AICreateEnrouteATCAircraft using pure C++ simmconnect. The plans place aircraft at 3 points on an approach route to KLAX and are identical except for the starting point being slightly further out for each. In SU10 all 3 planes will land. On SU11 the first one will land, the 2nd one will eventually overfly the airport while still climbing past 10,000ft, the 3rd one turns and heads in the opposite direction from the airport never to return.
I'm looking for confirmation of changes that would have impacted this behaviour and indication if it will be looked as a bug.
I do note that the altitude in SU10 is inserted incorrectly but in SU11 it is more accurate (related to live traffic altitude changes perhaps). Maybe this then leads to the odd behaviour in SU11 approach. But ultimately SU11 leads to lots of aircraft overlyflying airports and circling before landing and some planes never trying to land at all - different from SU10.
This link is a video of the aircraft moition in little nav map in SU11.
This link is a video of the aircraft moition in little nav map in SU10 - exact same code and plans.
After leaving the SU11 test running for an extended time - Plane 3 finally landed after about an hour and lots of ciruits above the airport. After an hour Plane 2 is still doing circuits above the airport at 6000ft.