jer029

nam1394, That's very interesting. I look forward to your additional test results. I'm confusing your issue regarding my elaboration on the AI stalling on the runway, but regarding your initial post on the fatal error before takeoff - that can be caused by an AI hitting a problem spot, as I've encountered it. I too have had issues with the clearance fatals - fortunately the later versions of Vox seem to restart and continue on without dying completely like older versions. I do believe this to be a navigational issue where certain waypoints in navigraph of your plane's fmc don't match up with the airports version of the approach. For instance - at PAJN I can get Vox to land me using the localizer approach to Rwy 8, but if I tell it I want to fly the RNAV-V RWY8 approach it throws a fatal error, then continues on asking me to report the various intersections. Unfortunately I've lately been then stuck at the last intersection "menae" and it refuses to recognize when I radio that I've reached that. I've also tried the "anyplace" substitute that is supposed to get past name recognition issues - and it doesn't even recognize that! John

UT2 with the Voxatc AI Bridge. Like I said, I got it working, but don't remember what I did in that case. I'm just suggesting that this might be a more likely cause of the fatal error than the type=special setting. I'd be surprised if that is an issue (but I've been surprised before).

That's what "special" does - keeps the window visible during view changes (very handy - I also use and love ezdok). As such, I doubt it is the problem for pre-takeoff fatal errors. More likely I've traced some of these random fatals to airport layouts that don't configure correctly to the Voxatc expectations (often orbx stuff). I've also found that it's often the AI at these airports that are setting off the fatals. When Voxatc tries to move your plane or an AI to a misconfigured area - the fatal occurs. Forcing different approaches, taxiways etc. will narrow down which is the problem. I noted at PAKT at one point I had a fatal error that kept occurring. I found that it happened while I was sitting at the gate preparing my plane for takeoff. The trigger was the AI that became active and immediately began taxiing to the problem spot. Finding out the exact problem and fixing it is another story though. Tegwyn believed that some of this might have been misaligned or disconnected taxi connections to parking areas, hold short line distances from runwyas, etc. I don't remember what I did to fix PAKT. I tried to find out why my AI at KHIB or KINL (don't remember which of the two), kept parking on the runway rather than taking off, and never could figure it out. I finally just started taxiing around it.

Manually install it (necessary for some payware addon aircraft). Go into your FSX folder->simobjects->aircraft Find the folder for that aircraft, find the subfolder called "panel" find the "panel.cfg" file. This is the file you want to change - but make a backup of it in case this doesn't work right or you want to reset it. Also - open a similar file in an aircraft with that Voxatc successfully installed. You can almost copy and paste those two entry group of lines ( one group of lines for the atc window and the other for the past com messages). You will likely have to change the numbering to match the next consecutive available window number based on the ones listed in the file you are adding these lines to. Finally - if you want it to remain on screen through view changes in the VC, add the line "type=special" without the quotes of course. This will keep the window active until you manually close it. John

You might try uninstalling and reinstalling the voice packs. I've been using them for some time and, other than the several minute voice initialization when first turning on computer or a reboot, secondary initialize of voices on re-enable of Voxatc are quick (and I hear 'test'). I thought I heard a reinstall can help sometimes with these voice issues. Oh...and I do get the occasional fatal errors too. I don't think these are necessarily 'false' errors, but that the latest Voxatc can recover from some of the errors - often related to nav data not matching airport data I think. I'm thinking the developer had Vox continue without the pilot losing the entire flight communication in mid-flight, but didn't change the initial 'fatal' error message. Yes...a more graceful error handling protocol would be nice.

Alan, I don't think it's a voice recognition issue but something specific to that airport scenery or runway. Try using the menu '0' - see if you can select a different runway - also test another airport to test further. "Seamlessly working" ? Hmmm....I'm not sure I've ever had my FSX system working seamlessly - but I've come close. With all these many addons having to play nice with each other it's a wonder it works at all My VoxATC setup was perhaps the best ATC I've used when integrated with the UT2 bridge for additional air traffic. The only problem in recognition would be a continual repeat of hold at runway instruction - but would only have to repeat it once each time. I've had similar issues you describe - and it's usually related to some addon that Vox doesn't like - something about runway hold-short lines not positioned just right or something. I've tried comparing airports and runways that work and don't, but could never figure out what the issue was on those few ones that cause problems. John

Yes...I also have this issue - annoying but I just keep jumping channels as requested. Might give radios to the FO until it gets it out of its system during those times. It seems to be specific to certain areas or airports - I'm not sure I experience it every flight.

Would not Radar Contact work better for you if you didn't want to use the Voice feature?

I use Vox with UT2 planes and find that I do get a performance hit with the AI traffic - even choosing other core options. They don't follow any SIDs or STARS as far as I can tell. I wanted to see how they made the offset approach at PAJN - they didn't - just flew right through the elevated terrain located near the end of the runway.

As long as I'm here - anyone have the issue with ATC repeating the 'hold at runway' segment of the taxi instructions when a runway crossing is required? I have this thing humming along great - hardly misses a word that I say ever! However - it seems to not recognize the first repeat of my taxi instructions back to the controller - and it's only the hold portion. The second time it always goes through. This has been an issue with past versions too. My first thought is a bug in the displayed text and what it is expecting to hear from me - so when I read the displayed text - it automatically fails on the last part where the match fails. I'm also guessing that it automatically takes the repeat as a default so as to keep the simulation moving smoothly. If I get ambitious I might check the error log to see if I can see if I can identify a mismatch or error related to this. It's annoying but not crippling. John

I might suggest that that's probably the problem aircraft then. I would suggest looking at the panel that its using and compare to another functioning aircraft panel with voxatc in stalled. Remove any voxatc additions currently in the flawed panel setting for that aircraft and manually install it as I previously described (unless you can figure out by looking at it why the voxatc default panel - if any there - isn't working correctly. Manually installing or editing panels allows other configuration like 'type=special' which keeps a window from disappearing when you switch views. That's handy with vox - that you want to be there on all views unless you specifically close the vox window. Hint: There should only be two voxatc panel windows added to the panel.cfg - which I think is in the aircraft model folder (one for the actual interaction, and the other that shows the history of vox transmissions). Just make sure that your new panel entries are numbered consecutively starting at the next available number after the last number for the panel windows already defined in your particular model that you're editing. LIke I said - it will likely be different than the one you use as a sample. Some of those complex addon aircraft confuse voxatc panel config utility, then I just install manually - but I don't remember them crashing the whole config utility though - just not installing anything if I remember on past versions. I suspect it's a limitation of voxt - not a deficient install (if other aircraft installed panel correctly). Reinstalling vox won't fix it. Try manual examination and correction of the panel.cfg file. Oh...and as always with such things - back up your panel.cfg before messing with it. John

Never had this so - Just a guess on this from the error and what you said. If it worked and then stopped (and it appears related to panels), did you make any changes to aircraft or settings or reinstall something between the time it worked and stopped? Does it crash when you first choose the panel option or after you select aircraft to update panel and click to have it added? That would likely be the source of the error (though not narrowing down the cause). I believe I had some payware addons that used to not install the panel - so I had to install them manually on those aircraft. This can be done easily enough be duplicating an existing panel working with Vox - just make sure to adjust the new panel number to match the next open one in your new aircraft which will likely be different than the one you're using as example. Make sure you're base file settings for Vox are still set correctly - I forget now - but if there's a setting for your Base FSX folder - make sure it's set correctly.

Yes...Vox will land you at a runway it determines to be the correct runway (not always the best dwn-wind runway). I've only experienced a few times when it sent me on unusual turns before landing me. In the earlier bugged version of the new release I had it vector me away (down wind) then stop working - causing me to continue away from the airport until I figured out Vox had froze up. The "0" option allows you to change runways and approaches other than the default that Vox had planned. Since the latest release I have not had this problem - but only did limited testing on it so far. Make sure you have the current release, run the runway indexer after any scenery changes, and also that you've linked to your Level-D Naviagraph if you're using updated Navigraph data for your airports.

This is an interesting topic and I've been only somewhat successful in correcting problems in this area. First - the files you show there seem to be all outside of FSX file structure. I'm not familiar with Aerosoft scenery - but even Orbx puts the actual files into various scenery files into the actual FSX structure in the scenery folders. I would do a search of the fsx scenery folders for the 4-letter airport code of the airport you're working on - that should show the main airport file. Also - ADE won't open the bgl if it doesn't contain the airport - if will give an error message saying 'no airport in this bgl'. As for the actual fix - this is where it can be hard to fix. My problem has been ai getting stuck on runways and taxi ways - even though the taxi pathways and hold-shorts all appear connected properly in ADE and the ADE tool indicates no runway faults identified. John I also sometimes try to compare properly functioning airports to the problem airport by looking at each file in the ADE to see if I can find the problem. I would say that the one good thing on this latest version is that the 'press 0 if impatient' seems to work better - as it cleared the stuck airplane and then gave me take-off clearance. The problem plane just disappeared - so not realistic, but at least I didn't have to drive through or around it - also not realistic. John

Thanks A3, I think they are important for improved recognition, but interesting thing - I obviously failed to train after this latest release. I also deleted the entire voxatc install folder under program files for the old version before installing the new version. I had no "say again" Issues on this new test flight. It might be saving the voice files elsewhere though - as it did remember my free voice addon assignments. I did find other things with voice settings to improve things though on earlier versions. First I used the sound recorder utility in windows accessories to record from my mic to ensure it played back ok, adjusting volume controls until it sounded good. I found that too low was bad and too high volume caused distortion and was also bad. I also learned from flying on line with friends that my mic level dropped to low level on longer transmission. Checking the forums I found that turning off special sound features in mic recorder properties setting stopped that from happening. Otherwise the only solution I can think of till they fix trainer on this release would be to train on earlier version (see links to the 6.2 version download under ...6.34 has major issues post). Then use 6.2 - which is pretty good - or update to this newest one after training. The trainer did work for me on that version :)

Yikes...didn't mean for you to download a virus! I actually didn't run that again as it appeared all my voice settings remained in place from the old version and it worked well. I just fired up the system and gave it a try -- NOPE - Same Error on My Computer. Sorry A3 610, I should have tested it on my own computer before I opened my big mouth. John

Based on the error message received it looks like something wrong with your voice recognition stuff. I might suggest that you start first by making sure that the voice recognition works in Windows before you try to run voxatc. Also make sure you have not loaded extra voice files yet - as they can cause errors too. Get the base package working on your system and then add voices. This looks like a windows error problem to me. Once you fix windows error problem vox should work. John

Not sure what you're trying to say Vonmar. There were only two problems I specifically mentioned regarding Voxatc current version: 1. Vox repeatedly asking if I copied last message after giving me "taxi to runway" message. For this I think is a minor bug in current version. 2. Install problem (failed after "select simulator", and wouldn't run runway indexer). This I assumed was due to my disabling the file UIAutomationCore.dll. My assumption was apparently correct because the install was successful after enabling those files on my system. I post these for two reasons - The first is (with my problem number 1) that I think is a minor bug that might need tweaking by the vendor. The second (with problem number 2) to alert others who may have the FSX tweak of disabling that dll file, that they can properly install Voxatc by restoring that file. This is not a problem with the software for the vendor to deal with, but a 'heads-up' to other users who may have not identified the problem (same with the Plan-G app) that they need to restore their dll file to work these programs. Overall my first test flight went very well with the minor exception of that noted - a great improvement over version 6.34. John

One flight from PAKT PAJN this morning in Majestic Dash-8 Q400. Very pleased with results. No Fatal errors, although I followed the ATC (dodging mountains as best I could) rather than selecting RNAV approach like I would normally do. So...I'll see how it does on future flights - but so far I'm very pleased (no pause problem and no loss of connection in the middle of flight). The only issue I had was on taxi for takeoff - vox window told me to taxi to the runway while the controller continued to ask me if I copied his last request. I tried again - but it had already recognized that I was cleared to taxi per the message on the screen. He continued to ask me if I copied until I was taking the runway - at which point I was given the message to state I was taking the runway - as one would expect to see. So...in spite of this glitch - it recovered nicely and the flight went on without problem. I found that it didn't want to install when I had disabled my UIAutomationCore.dll files (fix for fsx freeze on some systems). The installer worked after I re-enabled those files. I think I can disable them later if I get freezes during flight. I've had freezes with Majestic (even with the new UIAutomationCore file), so have those disabled normally unless if have issues with other programs (like the newest version of Plan-G). I would also suggest repeating the update process after install (rwy number update, indexer, and UT2 bridge if installed). This might clear up some issues. While I see that the indexer ran automatically on install, I don't think the rwy number updater did. That's why I would redo this entire process. John

Great to hear crashmax! Following install instructions on the download page - yes uninstall current version before install. I didn't see the voxpop voice support issue, so would expect them to work also - after reinstalling them in new system perhaps? I will install tonight or tomorrow and give it a spin. John

Great news!

I'll have to try the smaller airports again with Voxatc. I forget the responses. From the user manual it looks like much of that only works for VFR flying in Vox. But my plans are usually IFR so I will have to experiment with some of my old flight plans.

Yes...and with latest patches it even works with FSPassengers. I use them both with the Q-400. You might have to manually add the Vox windows to the panel, but I forget. It's easy though.

Yes...I get that message when my flight plan isn't loaded properly - but I use version 6.2 because 6.34 currently has too many bugs for me. You must load your flight plan as previously described to get ATC service.

The process is automated once you've loaded your plan into FSX (note that in 6.34 this can be done without restarting a new flight, but older versions must use 'end flight' and "load flight plan" options in FSX before starting Voxatc to get Voxatc to recognize the flight plan - otherwise it will say something about local flying and you won't get to fly IFR airport to airport. Loaded correctly Voxatc should automatically direct to you a different radio frequency for opening and closing flight plans at smaller airports. John