msparks43/xplane-11-autoatc-plugin

C/C++ Source code for Xplane AutoATC plugin

xplane-11-autoatc-plugin's Issues

AI Planes broken flight paths

AI aircraft occasionally get lost at some airports, and fly impossible flight paths - priority bug to fix before beta release

Document basic app features

About time the application was better documented, especially "sounds like" rational, settings and ground school.
Settings also need a menu item just before beginning a flight

Android App Landscape layout issue

The android app in landscape mode has following issue:
If you click the the "command" button the layout switches from landscape to portrait and back to landscape without triggering recording.

AirportOps:ATC controller doesn't consume arrival time estimate

This is a long standing bug that results in the breach of separation first seen here:
https://www.youtube.com/watch?v=1RJ_NX2R-7w

In Jan 2018!!
Basically ATC currently assumes an aircraft is "at" the position it is estimating, rather than be there at the time given.
Needs to handle given time errors to fix this, but likely won't be until the Airport Traffic Management updates:
https://forums.x-plane.org/index.php?/forums/topic/170459-airport-traffic-management/

start to go in after this month before I can fix it.

EHAM: Planes not landing

Amsterdam Airport Schiphol IATA: AMS, ICAO: EHAM AI Planes seem unable to land and circle above the airport until they run out of fuel.

Can't connect to Zibo 737-800

possibly a java conflict, needs more testing with the 737 Zibo mod.

android network switching prevents radio restart/connection

If the android device switches wifi networks while connected to the simulator, or is on the wrong wifi network when first started, this can block simulator radio restart forcing a hard restart, or prevent the android device from connecting.

Fix/work around: Ensure android device only connects to the correct wifi network and disable autoswitching for nearby networks.

AirportOps:Take off & arrival proceedure

line up clearance being issued to soon.
join clearance taking to long (with conflicts)

Cannot complete ground school

Training the voice recognition works but exercise answers are not recognized.
Phonetics training can be executed but progress is only displayed after restarting the app.
While training the status is always Trained [0/39] even after getting some matches. After restart the app status gets refreshed, Trained [39/39].
Phonetics exercise cannot be completed. UI shows Completed [ 0/25]
After giving right answer nothing happens, answer is not recognized.
Example:

Whats the phonetic word for the letter "J" ?

answer: juliett

But then nothing happens and answer is not recognized as correct. Status is Completed[0/25] even after restarting the app.

correct pronunciation of "decimal"

default TTS should pronounce numbers as:
https://www.youtube.com/watch?v=NufAKh0ux8E

->conflicting pronunciations?

AutoATC Pad display

Cleanup and "beautification" of the info display in X-Plane.
Different font colors for ATC and user commands,
more spaces and tabs between pieces of info,
maybe a "normalization" of spoken and received commands (display "N135SP" instead of "november wun tree fife sierra papa"),
maybe a clickable button to trigger speech recognition so you don't have to use your controller or the mobile device when testing stuff

Incompatible plugins

Xplane plugins that try to load the JVM after AutoATC will cause XP to crash.

There are two possible solutions to this, first is for the other plugin developer to adopt the
api.XPJVMAPI

described on
https://forums.x-plane.org/index.php?/forums/topic/175706-sharing-the-jvm/

Alternatively, but much less desirable it should be possible for the user to patch the offending plugin with the API and force AutoATC to load after them by changing the name of the folder.

This issue is for tracking such plugins and providing solutions

Restart Radio has no effect

Expected:
Selecting restart radio from xplane plugin menu should disconnect and reconnect to device.

Actual:
No effect

Ambiguous Identifiers

It seems as though when dealing with locale names, only the first word of the name is being used-- likely intentionally and likely for the sake of brevity. ie: "San Francisco International Ground" becomes "San Ground." Problems arise when you have multiple similarly named entities in the same area.

The best example of this I've found so far, is the SF Bay Area [KSFO/KSJC/KOAK] in which numerous airports in the area start with "San." However, everybody on the radio says "San ground", "San radar" etc. and it is very unclear who is taking to who about where.

I can see why this would be a problem as there probably isn't a very good algorithmic way of determining how many words are used as an identifier. Some of the time it isn't so bad, as you are on SF Ground or SF Tower and it can be assumed-- but if things proceed in a realistic manner and you are handed off to NORCAL and then Oakland Center... it would get fuzzy very quickly as the Center frequencies continue to refer to everything a "San x".

missing nearby aircraft

looks like maybe the "first" 30 aircraft rather than "closest" 30 aircraft are being rendered in sim.

Good place to test is around the KJFK KEWR KLGA grouping which will always have more than 30 aircraft in the surrounding 120nm.

AI flights dropping out under heavy load

This looks like returning data is taking to long: move find flights to flight maintenance window to improve responsiveness.

android battery drain

A couple of times now i have noticed the app drawing an excessive amount of battery after it is dropped into the background.

For now the workaround is just to close it when done.
I suspect when it goes into the background something is causing one of the maintenance loops to except before it pauses. I did recently fix a load of crash issues related to the app resuming from deep sleep.

Will investigate.

Taxi Errors

KSFO Taxi to 28L via Z U C causes aircraft to turn on 1R/19L instead of crossing 1L/1R on C toward the end of 28L. This puts them in the mother of all bad places, pretty much where 28L/R, and 1L/R all converge with their wonderful # sign configuration. It considers this place to be the hold short of 28L, and then when instructed to take the runway, they taxi down 28L and turn around at the end.

Some aircraft are also confused as to the frequency they are on. One of them contacted the tower for taxi clearance [on the gnd frequency], and ground gave it instead of saying... wrong frequency or "this is ground."

Tower voice should be regional

rather than one predefined voice for the atc controller, there should be multiple options for each region (AUS,UK,US, india etc) with sensible defaults

"request vectors to" not finding beacons

from LYNI
"request vectors to victor alpha lima" works
"request vectors to echo kilo" returns "no vectoring available at this time".

AI Server Status

AI server status tracker for restarts (resets the world) and update transitions (flight plans filed before not be available during)

[Crash] Airport Change

Description:
Changing your airport from the settings menu on a fresh booting of the app before selecting anything else causes app to crash.

Repeatable:
Yes

Steps to Reproduce:
1: Fresh boot app, make sure it's not resuming anything.
2: Go to settings
3: Change your airport

Expected behavior:
Airport change. Interestingly enough, it does change the airport, it just crashes in doing so. Next time it comes up, the airport change is reflected.

[Suggest] Map Snapping

There are times, especially during observation of traffic that one might wish to pan the world map in one direction or the other, but whenever you do this it snaps back into place around the user's aircraft. I would suggest that the default behavior be to leave the map at the user specified position and zoom level with perhaps a little button along the bottom or side to center on user position.

The map screen is also a little bit swipe left/right happy. You have to pan the map up or down before moving it left or right or it assumes you're attempting to... change.. panels or whatever you call them.

Deleting Flight Plan App. Crash

This is regarding AutoATC Radio Beta [0.8.6.9].

Description:
Swiping right on "Create a new flight plan" causes app to crash.

Repeatable:
Yes.

Steps To Repeat:
1: Delete any existing flight plans that might exist, so the only entry is for creating a new plan.
2: Swipe it right, as if to delete it.

Expected Behavior:
Either it won't allow you to attempt the deletion, ie: swipe does nothing with empty flight plan set or catches the exception and handles it. Either or.

Actual Behavior:
Kaboom.

Xplane crash on exit

In some circumstances, AutoATC Xplane plugin will cause a crash when exiting the sim

Multiple active runways: queuing

Seen in the wild.
Airports with runways that cross each other (for example EGCB) do not yet have shared queues for multiple active runways.
There is therefore a chance of aircraft being given permission to land/takeoff in unsafe circumstances.

Pilots are therefore advised to be extra vigilant to radio traffic when operating from such airports until traffic advisories and combined clearance queues are implemented and rolled out.

Missing airframe definitions

Remaining air frame definitions are due for write up within the next few days

Stutters when transmitting and changing frequency

This is fixed and will be available at the next plugin update (or build from source here)

voice distortion not optional

radio distortion should be default clear and applying distortion optional.

multiple reports of related issues.

Applies to both phone and plugin - issue to be fixed before 0.8.7 comes out of beta.

Shared cockpit setup

For multi PC/shared cockpits - added "Extended Cockpit" option to the plugin settings.
As many PCs as needed (I guess within reason) can be added to a single android app to show AI planes from a single android device.

Working in beta, this issue for tracking any problems with it.

EIFR:En-Route frequencies

Currently frequency changes while enroute must be made manually, and many if not all centre frequencies are inactive.

Current workaround is just to tune to any in range radar frequency.

Automated handover is a work in progress. As is an implementation of:
https://www.cfinotebook.net/notebook/flight-hazards-and-safety/lost-communication

adding an airframe clears new flight plan data

When filling in a flight plan adding an airframe last clears already entered data. (android app)

Stand-Alone Positioning Conflict

As per testing suggestions, I started up AutoATC without any X-Plane interaction and put myself at Covington [KCVG]. Radio traffic was really good, lots of planes started communicating and moving but...

Description:
The personal airport selection resulted in the placement of my "aircraft location" in the middle of the airport, which was incidentally right along the taxiway the planes were wanting to use for runway 18. They all taxied just short of my indicated position [on the map] and formed a long line completely choking ground flow at KCVG.

Repeatability:
Untested, yet somehow presumed. When moved to the municipal field nearby, the traffic continued as normally-- but since it is presumably simulated on a server somewhere, traffic didn't actually reset with a program restart.

Steps to Produce:
1: Open AutoATC on Andoid and start flight
2: Set your airport to KCVG [should put you pretty much dead in the middle]
3: Observe traffic pile up behind you

Expected Behavior:
Should either ignore your position if not actually connected with a simulator, or be extra cautious to place you in a parking or otherwise non-essential traffic area.

Actual Behavior:
Rather amusing tangle of aircraft on the tarmac.

Conjoined twins

look like the aircraft feed is conjoining aircraft (I should have recorded a video as another one of those "bugs that make you laugh" but I was to confused trying to understand how it was happening to pause out and capture it). Possibly callsign key related. Needs fixing asap.

EIFR:Flight plan starting

Experimental IFR flight plans as @ AI server version 0.8.8.26 can't be started or joined other than from the source airport and before the startup time, meaning they do not survive an AI server or client side restart.

EIFR:Vectors to final

Experimental IFR as @ AI server version 0.8.8.26 does not give approach vectors to final

AI server not checking if gate is occupied

AI Server needs to check if a gate is otherwise occupied before assigning it.

Untowered airport support

Some kind of "no ATC controller" support is required on the AI server for small airports for A/A communications with no controller.

AI server not using correct flight model for airframe

TODO (for 0.8.7 release):
Apply flight model data based on airframe to AI aircraft.
Most notable with slow take off speed

Missing ai aircraft

the latest server only creates default ai aircraft that visit an airport whose map has named taxiways.

this has resulted in a number of even large airports that do not automatically spawn ai aircraft (since neither they nor any destinations the ai aircraft would visit have named taxiways defined)

most notable in and around Germany which has hardly any active ai aircraft at the moment.

This doesnt affect ai aircraft spawned via a filed flight plan and will be resolved as soon as possible.

Can't cancel flight plans

Deleting an open non AI, non active flight plan should cancel it
requires android and AI server update

AI planes breaching separation rules on joining

Long standing bug first documented Jan 2018:
https://youtu.be/1RJ_NX2R-7w
(approval separation not resulting in flight separation)
Marked for fix.

Plugin frequencies can't tune

Looks like the plugin standby frequency selector doesn't work if no AI aircraft are in the vicinity.

atc not replying

johnbc on main install comments:

Installed AutoATC as directed. The android tablet is connected and I'm able to speak my commands successfully. However I receive no ATC reply. I would welcome any help.

Customizable timeout after speech recognition

add recognition timer variable to settings page.

Autistic AI

Thought this was fixed last update, seems not.
After a period of time the process by which the AI "forgets" words it has heard triggers, this is because there are far too many words for it to remember all in one go.

The process doesn't seem to be working correctly, preventing the ATC/AI aircraft from communicating.

Only current fix is a "reset the world" event, will monitor and unit test.

Airport hotspots

Just seen the first "head on conflict" with airport traffic in taxi.
I had suspected this is something that can occur (although there is already some mitigation), but this is the first time I've actually seen it happen.

Fits in with the discussion around airport traffic management:
https://forums.x-plane.org/index.php?/forums/topic/170459-airport-traffic-management/

Which has seen some good progress.

Since it also occurred on an airport hotspot in the AIP, this will likely need more AI around identifying and handling airport hotspots.

scheduled for no sooner than 0.8.8, for now if you see this, just go around them or fly somewhere else, eventually the cause of the conflict will time out and airport operations will continue as normal.

Missing waypoints

Add waypoints, map visualisation for them and allow vfr waypoints on vfr plans

ground school requirements - phonetics

I think its going to be best to force completing "at least" the ground school phonetics training.

Not doing so is resulting in lines like:
User:taxi approved by kilo proper hold at juliet one runway 0 8 right
ATC:delta 1 2 5 0 i say again , taxi via kilo papa , hold at juliett wun

in the AI server processing logs.
The issue here of course is that
proper should be papa
one should be wun
and
juliet should be juliett

The training in the phonetics works around this (so papa sounding like proper converts proper to papa before sending to the AI Server)

Work around for now is to complete the ground school phonetics training even though not forced to do so.

Callsign shortening

Shouldn't shorten callsigns if doing so creates duplicates (as per icao guidance), its a real thing, probability of it happening is actually surprising high.