Hey, I have created an airplane via AICreateNonATCAircraft at my Airport. When
now sending waypoints for taxi instructions to it, it will remain at the
position with the State “STATE_SIMPLE_TAXI”. Flag is set to ON_GROUND. When
removing the flag the Aircraft will jump directly to “STATE_SIMPLE_TAKEOFF”
and start stright forward. I have checked the SDK sample but was unable to
find one for an NonATCAircraft with taxi instructions to test it as well.
Update: Creating the airplane with AICreateSimulatedObject → Same issue
Creating a ground vehicle with AICreateSimulatedObject using the same code to
send waypoints → working as it should. ==> Seems to be related to
Category=“Airplane”
Update (used the sample AIObjectsAndWaypoints): Replace the firetruck with the
“DA62 Asobo” → it will takeoff like the 1st DA62 Asobo. Add the Ground FLAG
to the waypoints → it will remain in position
Sample is uplaoded here:
https://1drv.ms/u/s!AqjmyvgAhMkBn6M4R-kwWspYSlUNmw?e=Xpk4ZE
We programming the “Enhanced Live Traffic” Mod and had the same problem. No
taxi of aircrafts if you set the “onground” flag. The planes stuck at the
position and starts to turn around the own axe. So we could only use the
positioning. This bug is really annoying… The problem is also that there
are no variable for Heading for the waypoint function. I think that taxiing
without heading will be a problem with this function.
I have an idea. Maybe you have to release the brakes. I would try, but
honestly I don’t know how to code that! I don’t know how you will set
variables to the AI objects!
@FlyingRaccoon any chance to had a look at the sample?
Yes, this has been reviewed and added to our backlog.
The same problem occurs when placing objects with a mission script. You can
kinda work around it by giving the waypoint a speed. I think you can do it
with ktsSpeed in simconnect:
https://docs.flightsimulator.com/html/Programming_Tools/SimConnect/API_Reference/Structures_And_Enumerations/SIMCONNECT_DATA_WAYPOINT.htm#members
sadly even with Speed it does not work in SimConnect
Sorry to bring up old topic but I’m assuming this never actually got fixed and is being mostly deprioritized because everyone dedicated enough ended up working around it and manually updating aircraft positions? I don’t want to have to do that but I’m getting the strong impression from research here that it’s the only way to make an aircraft move on the ground?
1 Like
Yes, this has been reviewed and added to our backlog.
Its been 2 years now, and increasing more Devs are wanting this Ground Control feature to work, and having to do very inefficient & resource hungry work arounds,
As it is working in the air, but not on the Ground, maybe it;'s just a simple bug that could be fixed quite quickly & easily, and would work as intended, as well as saving Devs the time & resource expense, to implement an unsatisfactory work around.
As you indicated that ASOBO had “looked at it”, are you able to tell us if the issue is working correctly ON the Ground in MSFS 2024, which is only a few months away, with an answer making it a lot easier for devs to plan going forward , the best way to inject traffic into the sim, both in the air, and also in the same way, correctly on the ground.
Thanks …
To add a smidgeon more detail to the issue/clarify the earlier points made what happens is thus:
If you AICreateNonATCAircraft() and pass it waypoints that have the ON_GROUND flag set, it will enter AI state SIMPLE_TAXI but the “Pilot” will remain as “Zombie”, therefore it never tries to simulate any actions required to meet the waypoints. I don’t know if this is because it simply doesn’t have an appropriate “Pilot” for this implemented or indeed it could be a very trivial bug where it just needs to assign the correct “Pilot”.
If the waypoints do not have the ON_GROUND flag, it will simply charge recklessly forward from wherever it is and take off, it makes zero attempts to manoeuvre on the ground, it won’t care what speed/throttle value is set and will instead do whatever it needs to do to take-off, but it will function quite reliably in the air as far as I can tell. I believe having ON_GROUND flags do help it to land though!
If it’s an ATC aircraft instead and given a flight plan, it will enter a state like “TAXI_TO_RUNWAY” with a “Pilot” of “TAXI” which appears to do what it’s supposed to do but from what I’m gathering there’s no way to influence what paths this will take and it’s managed internally by the simulator and the airport taxi way data. I believe this is probably what some traffic injectors are doing?
1 Like
In your review, was it noted that this works 100% correctly in both FSX and all tested versions of P3D, including current version. ?
Could you maybe give any update on this? I appreciate you’re currently likely quite busy but I’ve been waiting a couple weeks now for this to be looked at.
Hello
This issue was not prioritized so far on MSFS 2020 and it is unlikely to change.
I will keep bumping the subject internally so that it is looked at when we have more bandwidth.
I am not allowed to communicate on MSFS 2024 but we will discuss this in due time.
Regards,
Sylvain
1 Like
Appreciate the response Sylvain! If it helps I am here representing two 3rd party products that have a use of this functionality and based on previous posters several other noteworthy products had a use for it too… If it requires significant dev time that is understandable but indirectly this could be an issue affecting 10 of thousands of users and adding significant (read: potentially months) of additional dev time to produce a reasonable work around. I observed some products having solutions that involved making in the region of 100 calls to simconnect to set data per frame, which struck me as a less than ideal solution.
1 Like
Problem is, there is no “reasonable work around”, apart from Asobo fixing the code, that works in both FSX & P3D.
Its NOT a new feature request, but rather a request to fix a bug that is causing many Developers to not be able to finish their products.
From a SDK perspective, there is nothing in the SDK that states this feature should not be working correctly.
1 Like
I must admit, I’m facing a lot of issues fighting with simconnect on this. There’s a lot of strange behaviour that is almost impossible to get meaningful debug data on and entirely unexplained in the SDK docs… but when I said “reasonable” workaround I actually meant “something that appears to work for the end user”. It’s a very unreasonable workaround to micromanage the position of every single aircraft on a per frame basis in my opinion, unless it’s edge-casing. The very fact that the ability to create a “Non ATC” aircraft and give it waypoints exists is meant to remove the need to micromanage what the aircraft does.
Should be noted, I’ve also discovered that injecting an aircraft in the air and passing it a waypoint often leads to STATE_SIMPLE_FLIGHT but pilot Zombie: and the aircraft simply hovers fixed in the air too… I’m still looking into this but I have a sneaky feeling it’s something like if the waypoint is “too close” to the initial position, it just doesn’t do anything but equally doesn’t appear to have a way of meaningfully telling you this. I’ll try giving it further ranged waypoints later and see if it suddenly decides it wants to fly.