Yeah no, I tested it pushing the aircraft out like 1.5km away from its waypoint and it still just hovers in space with STATE_SIMPLE_FLIGHT but Pilot: Zombie.
If the initposition is on the ground, it’ll take off and fly waypoints, if it’s not, zombie mode…
So you got a double issue, unless I’m missing something here, @FlyingRaccoon
It won’t taxi if the next waypoint is on_ground and it won’t fly if it starts in the air. It sets the right flight states but the pilot remains zombie …
Sorry to be a pain in your derriere here, but I got another issue/bug with these NonATCAircraft…
If the aircraft is started on the ground (initpos onGround) and fed waypoints, it will fly them… if the final waypoints are also flagged as on ground, it will land… if you flag the final waypoint as wrap_to_first (i.e. to create a looping pattern)… the simulator will outright crash. I’m assuming that the Aircraft/AI state has to have switched to STATE_SIMPLE_LANDING and Landing respectively.
I appreciate time constraints and demands with the upcoming 2024 release but there is clearly a cart full of issues related to NonATCAircraft and waypoint behaviours Any chance you can add the extra two issues (if not already known) and mention it again internally? It’d be much appreciated as this is really hampering a lot of cool stuff we would like to be able to do.
quick summary:
Aircraft spawned using AICreateNonATCAircraft()
If Aircraft is onGround in the init position and the first waypoint is also flagged as onGround, it enters STATE_SIMPLE_TAXI but pilot remains Zombie and nothing happens
If the Aircraft is NOT onGround in the init position and the first waypoint is also not flagged as on ground, it enters STATE_SIMPLE_FLIGHT but pilot remains zombie and it will hover infinitely at its init position
If the aircraft is onGround in the init position and the first waypoint is NOT flagged as on ground, it will enter STATE_SIMPLE_TAKEOFF, charge straight forward till it lifts off and then switch to STATE_SIMPLE_FLIGHT with a pilot of Waypoint. This then behaves pretty well following its waypoints…
If the above is done and the final waypoint is also flagged as on ground and altitude 0, it will enter the right states and pilot to land… however if that final waypoint is also flagged as WRAP_TO_FIRST, then MSFS 2020 will outright crash.
Let me know if I can get you additional debug information/crash logs/whatever to help with this.
Tech Alpha: No, it wasn’t fixed in that build
Dev Alpha: No access to test it, Marketplace sellers only and we cannot publish in the marketplace (Both OnAir and SayIntentions are external applications and thus cannot be in the marketplace).
Well, all will be revealed in a few weeks, and if such a simple thing is not fixed in 2024, then the request will probably start flooding in .
.
(better than flooding simconnect !! )
At least the BUG is marked as LOGGED… that’s a good 1st step in getting a solution from Asobo.
…
I can probably take a look after the mid-December patch is done, although I have to admit I am not that familiar with this part of the sim. Would you have a simple C++ SimConnect test app that I could use to reproduce the erratic behaviors that you have been describing here?