GoalieMedic

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.