jer029

If you've added additional voices (I think I found 4 others out there for download (3 male and 1 female). If installed correctly they should indeed appear in the left pane. Perhaps you might try reinstalling them, as it appears they didn't install correctly.

I thought it worked off of the first intersection that matched your current STAR if included in your flight plan - perhaps if you included the shared intersection that matched your approach not including the old one it might bypass old intersections and pick up from there - though not sure about this. John

Not sure about MT6 as I use UT2 with VoxATC. Any 3rd-party traffic add-on would not be seen by VoxATC, however in the case of UT2 the bridge application that VOX offers allows UT2 liveries to be included in the VoxATC traffic setup. I don't think the scheduling part works with Vox but I see lots of Alaskan Air liveries around Ketchikan when I fly out of there - so I'm pleased to see the various 'real-world' airlines represented. With the bridge setup Vox does control these aircraft as well - having them hold while you land, etc.

Not sure exactly, but did you run the indexer after making any scenery or aircraft changes, and after initial install? what version of VoxATC are you running? and on what sim system? Make sure your flight plan is loaded before starting VoxATC, What flight plan? Did you try altering the flight plan? Just some thoughts on possible solutions and ways of narrowing the problem down. Lastly - try reinstalling the program. You might have to email the developer on otherwise

Just a thought here - although it applies primarily to those FSX users who at some point altered their Uiautomationcore.dll files by deleting or renaming so that they wouldn't have FSX crashes. I've found that many applications require these - including the new VoxATC setup utilities. Once Voxatc is installed correctly - the UIautomationcore.dll can again be renamed to prevent fsx crashes. The dll is only needed to run the various setup utilities, and Vox will run with FSX with these files again disabled. Just thought I'd mention it in case you used to use FSX and have those dll's disabled. If so - make sure both the system and system64 files versions of UIautomationcore.dll are restored during install of Vox (and any other programs that mysteriously have stopped working).

Also note that the panel set up doesn't always work for some addons. If, after running panel setup and indexer and the other settings as beerwolfe mentioned, you still don't see your Vox window in your instruments view under "views" at the top fsx menu, then you will have to add the vox windows manually. Best done by finding a default aircraft that the panel did install correctly to and just copying and pasting those panels to you 737ng panel.cfg file - but changing the headers and the windows to match the next available window numbers that will likely be different from the default you are copying from. I still think vox is one of the best ATC add-ons available for fsx, and flying without it takes a big chunk of realism out of it. John

Rick, What simulator are you trying to use it with? Have you been able to make any earlier versions work? "normal installs" means that you've run both the panel install and indexer right? Have you tried different aircraft with it (like some basic fsx default aircraft)? I might suggest the following: Compare a working version of the main voxatc window panel with the panel configuration file in the problem plane and look for differences that might cause the window to not stay showing (perhaps a conflict in numbering or something). Although I've not heard of this before - it seems its always either installed or not using the panel installer - or I had to manually install. John

Thanks Raz2214, that's what I tried to do, but didn't have much luck - however all I did was move the existing points around a bit. Perhaps I'll have to try redoing the whole think like you did.

Yes...It's my understanding that this might have to do with the layout of runway lines and distance to various connector points like the runway hold-short lines, although I've tried adjusting these in the airport editor and have seen no changes. I've also had planes taxi out onto the active and just sit there. I've given up on solving this - perhaps someone else has figured it out. I just taxi around the 'drunk' pilots and continue with my flight - but it does detract from the realism.

I've given up on P3D since it doesn't play well with my multi-monitor system, but I'll take a wild guess based on the error message you attached. It appears that it's not finding your FSUIPC application (or you don't have the current one installed and the one that's P3d compatible). I'd start there - making sure you have FSUIPC installed and working correctly. John

What are you running this on FSX or P3D? You only need to use UT2 bridge if you have Ultimate Traffic 2 installed. The bridge allows Vox to use all those aircraft (that's all it uses - not the program or schedules, but it's great having all those real-world liveries). You do have Ultimate Traffic 2 installed right? Otherwise I can't help on this because I'm still running V6.46 on FSX. I'm interested in the upgrade to 6.49 too, but only if I can run it with the UT2 bridge. Make sure you've updated the UT2 bridge also (older versions won't work with the newer Vox versions). John

To follow a SID/STAR you must have it saved in level-d format and the location defined in the Voxatc setup area. Then ATC will guide you on the STAR. In any event it has no knowledge of your FMC's TOD position. Additionally, you will note on page 80 of the instruction manual: No Vectors Approach If checked, no vectors will be given by ATC at your destination. This should be used when the destination airport has mountains or high terrain in the vicinity of its approaches. VoxATC is not terrain aware and may vector an aircraft into high terrain while vectoring to an approach. If I recall - the ATC will gracefully bow out with some instruction and allow you to fly your desired approach. John

Since VoxATC uses the windows voice recognition system, it's likely you will have problems with VoxATC if your windows voice recognition has problems. I do believe that you can try VoxATC for a limited time for free - so you should be able to give it a try to see if it works. Also, I think Voxatc is set up so that it will "auto-recognize" second or third attempts - so you still might be able to use it - even if it misses now and again. If I understand the workings of Vox correctly - it might be worth just giving the limited free trial run a try to see if it's worth the purchase. It installs and uninstalls easily enough. John

Manually install the two voxatc windows (if you want both the past coms and the VOXATC window). Find a plane that has the voxatc windows successfully installed and copy those two window entries into your plane's panel file. Make sure you adjust the window ID numbers to match the next consecutive number available for the plane you're installing it to - it rarely matches the one you're copying from. It's all in plain text in the Panel file of each aircraft so it shouldn't be difficult to replicate in your new plane. Just to be safe - back up the panel file before changing it. John

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