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