GoalieMedic

Okay, so looking at the output_log file, you are correct in that it is failing on ASH, AWI, RPA, SKW, and some UAL flights stating "No Free Terminal". For KIAD, I have all of the above (except UAL) assigned to terminal A2. Terminal A1 is reserved at IAD for UCA. UAL is also assigned to terminal C and terminal D (midfield terminals C and D at IAD are exclusive for UAL). I've attached the output_log and the terminal file if you want to see if there's something else going on. output_log.txt kiad_terminal.txt

Cross posting this here since I think for devs are here than on the FB ATC group. I have the long-anticipated KIAD pre-CoVID schedule completed (or so I thought) & was about ready to announce its availability for download. I compiled the whole schedule, aircraft, etc. in the custom schedule creator and loaded it in. All seems well except I'm finding that it's ignoring about 2/3 of the schedule. For example, the 07:00 hour at IAD is very busy with a lot of regional jet arrivals (35 in total on the schedule). The only flights that show, however, are United Express CommutAir (IATA C5). It's completely ignoring UA, SkyWest (OO), Mesa (YV), etc. Departures seem fine (there are only 6 in that hour, and they all appeared & were successfully sent on their ways). Also noticing on the strip that all of the flights are being given the same squawk code (3313), which means nothing since we don't do anything with those codes, but shows there's some sort of an issue where it's not giving each flight a unique code. So looking for some ideas on what may be going on from anyone who may have built their own schedule or may have had similar issues with missing aircraft from the schedule. When complete, the file will have 345 arrivals and 393 departures for the day I built. The full 7-day schedule will follow once we work out the bugs with the original file. -Jonathan

Anyone working on a pre-COVID KIAD schedule, or at least have access to the pre-COVID traffic data that they're willing to share? Happy to work on a sked if someone has the data.

Yes, it does. That's the odd thing. And I'm using an extremely high-end mic. Even just saying the word "Hold" brings up "Change". I rarely ever use the command "Change" to move someone to another runway. I'll vector them back around if I don't like what approach they're on. To that end, is there a way to completely disable "Change" from being recognized? I see the config file with the commands in it, but seems like a lot in there I'm not willing to blindly start changing or deleting.

So a new development recently and it's driving me absolutely mad. More often than not when I issue the command, "Hold short..." it recognizes "Change to", so a "Hold short of Runway 22R" for a taxing craft comes up as "Change to Runway 22R", which the pilot chokes on & comes back with "Say Again". I'm a very clear speaker (hell, I spent 5 years working in radio, so it's not like I'm slurring, mumbling, or anything). So there's no reason that 2 commands that don't even sound close to each other are coming up. Any ideas, y'all?

So far a couple of issues so far with LEBL: 1. Any departing aircraft at Terminal 1 that are issued a pushback command for runway 2 lock up. They will not pushback, the strips show a runway 2 assignment but never list "pushback" on the strip. You cannot then issue them any other runway command, so they just stay parked & never push back. Only resolution is to delete them. Does not seem to be an issue coming from south side of Terminal 1 or from anywhere at Terminal 2. See circled area in the diagram to see the aircraft that are stuck. (DLH1129 was issued from Q4 to RW2 and moved successfully / RYR7545 on north side of airport was issued to RW2 and also moved successfully / VLG8322, VLG8654, and BEL3704 were all issued to RW2 and refused to pushback). 2. Aircraft taxing northbound on taxiway N or M (example, N2 > N > T > Z8 > Runway 7L) hold short of the approach end of 7L as if they are holding to cross over an active runway (runway 7L is active). However, runway doesn't extend onto N or M, so they should just automatically continue taxing without having to issue a "CONTINUE TAXI" command. Currently, they have to be told to continue.

One bug so far. Start time of 16:00 (not a power hour start file), VLG8322 (1st aircraft) will not push back. Can issue pushback commands, which they acknowledge, but never actually push back. Other miscellaneous... Still having issues program-wide with the voice recognition picking up on any Avianca jet. End up having to manually clear them with the buttons at the top. Also, probably also not this file but program issue, no one will taxi past approach end of 7L on taxiway N (coming up from say N2 > N taxing to T > Z8 > 7L). Aircraft hold as if they're trying to cross an active runway. Have to issue them a TAXI CONTINUE command to keep them moving. Also, if you're trying to have someone depart runway 2, if you say, "Pushback Approved, expect runway 2", the system will type out "...runway two", which will error ("Negative" response from aircraft). You have to hold the transmit button an extra 1-2 seconds before the program changes "runway two" to "runway 2" (number) at which time it will acknowledge the command and taxi accordingly.

Disregard. Apparently had to reinstall v11 of Real Traffic then copied the LEBL files over and it's working.

I've copied the the files into the LEBL directory, but it won't load past 63%. Any ideas?

Is there any way to save a game in-progress & come back to it later? Can't leave it running and don't want to keep having to start all over with 1 aircraft on the screen.