dbrucem

I finally got around to adding this aircraft to my stable last night. To enable VoxATC for any new aircraft you must first run the VoxATC indexer. After that is completed run the Vox panel setup utility. You should now see your new aircraft listed. If you do not see the aircraft listed here the only recourse would be to manually edit the aircraft panel config file.

Ken, to me the major improvement is the tighter vectoring on ILS approaches. Unfortunately terrain avoidance is still an issue. The tighter approach vectoring along with custom STAR's seems to allow me to work around this issue in most cases. Also, you can ignore the vectors until you can safely comply but repeatedly having to acknowledge gets annoying. If it is not feasible for terrain awareness to be incorperated into VoxATC it would be helpful if the developer would add a way for the pilot to respond "unable at this time". This would be in line with real world flying as the pilot is expected to refuse unsafe ATC commands and not blindly fly into the mountain. I agree that this program enhances the Sim experience and for me FS would not be the same without it. Happy flying.

The Sennheiser PC 165 headset is an excellent headset with a good noise cancelling mic. It can be plugged into your soundcard or into an USB port with the enclosed adapter. The headset is light and very comfortable. I use it with FSX and VoxATC with very good results.

Version 5.55 of VoxATC X is now available. This update includes:Greater numbers of parked aircraft at airports.Airliners allocated gates appropriate for their airline.Tighter approach vectoring.European ATIS format changes.Various phraseology updates.

There are a number of options out there. Search for SAPI5 compliant voices. As mentioned here nextup.com is a goodplace to start. Typically you purchase the enhanced TTS, text to speech, engine which generally includes both a female and male voice. This package is typically priced from $35 USD and up. Additional voices are typically around $30 USD each. Unfortuately these inhanced voices don't come cheap. Good luck.

The default location for VoxATC should be C:Program FilesInternal WorkingsVoxATC. It doesn't appear under modules in FS. During installation VoxATC will install VAgauge.gau in your FS gauge folder. Each aircraft that you will use VoxATC with will require it's panel config file to be modified. This is normally done during the original install but can be done later by running the panel setup utility which is listed in ProgramsVoxATC. The only visible aspect of VoxATC in FS is in the Instrument Panel listing under Views. If VoxATC is not present there you must run the VoxATC panel utility. Hope this helps.

"to infinity and beyond." Fusionman put on an awesome show. The National Geographic channel aired an hour long program detailing the flight and the life of this adventurer. Talk about having the real stuff. Wonder if anyone will model his jet wing for FS?

Go back to your Windows Control panel and click on the Speech Applet icon. Make sure your headset is selected under the text to speech / audio output drop down. Selecting your headset in the control panel sound and audio devices /voice doesn't carry over to the speech function. You can test both your mic and headphones in the speech applet. Hope this helps. The settings in FSX will not affect VoxATC as it is a voice recognition / text to speech application.

Sorry if I wasn't clear. I am using VoxATC ver 5.46 which is the newest version which works with FSX only. The point I was making was that based on comments made by ZEFR and other beta testers it appears that the developer is concentrating on the FSX version and it doesn't appear likely there will be updates to the FS9 version. I have used VoxATC since it was first released and even though it doesn't work perfectly I wouldn't fly without it. I currently use FSX primarily so I can use VoxATC-X as I prefer this version for its improved AI traffic and it's expanded voice capability, two controller and two pilot voices. Whichever version you use it is a vast improvement to the simulation environment.

Based on recent comments made on this forum I get the impression that the FS9 version is a finished product. The FSX version was recently updated and the developer is apparently planning further improvements especially in the control of AI aircraft. I no longer use the FS9 version and have had very good results with the FSX version. One area I would like to see improved is terrain awareness as it is very annoying to get vectored into a mountain.

With WindowsXP you need only to open the Sounds and Audio Device applet in the XP control panel. Open the Voice device and select your "headphone device". The Audio device should have your speaker sound card selected. This will work for either version of VoxATC as it is a speech or voice program and is independent of either FS9 or FSX sound configuration settings. In my case I use an USB headset instead of an additional soundcard. If the engine sounds on the speakers is bugging my wife I assign both audio and speech to my headset. Good luck.

Read the post just below, "My problems with VOXATC". Zane explains the current limitations of the VoxATC traffic module. Hopefully an upcoming version will improve the situation.

KenThanks for your kind words, I personally always try to provide feedback to anyone who takes the time to give assistance and I appreciate you doing so. Just to let you know this is an unofficial support forum so most replies here, like mine, will be from devotees of this wonderful FS addon with no official connection to VoxATC. I agree that the support from VoxATC is excellent. You can contact them directly on the contact page at voxatc.com. Even allowing for the six hour time difference they almost always respond within 24 hours or so. I have been amazed how they help especially with issues involving interaction with other software such as Vancouver Plus scenery and My Traffic-X for example. If you have any issues installing the AT&T Natural Voices try searching this forum as there have been a number of posts on this subject.

You can download the latest version for FSX on the VoxATC website. After reinstalling it you can activate it with your code from your original VoxATC-X registration. Use the FS2004 CD to install the ATT Natural voices only. Hope this helps.

Glad to hear you got the new version installed. As far as "KinGair", If you have installed the AT&T Natural Voice speech engine it includes a dictionary where you can add words and correct improper pronunciation. Locate the AT&T folder which by default will be C:Program FilesATTNaturalVoices. Open TTS1.4DesktopDATA. Dbl click . I also create a desktop shortcut to en_us. Once you have opened en_us click on edit, new word. Type in the new word, for example NATL which is pronounced letter by letter. To correct this type "national" in the box. Click the adjacent lips icon to hear the pronunciation. If you are happy click the button to generate the phoneme for this word. You can modify the phoeneme if desired. Cut and paste the phoeneme into the phoneme box below your new word. Save and exit the dictionary. You should now hear NATL pronounced properly. You can use this same method to correct King Air, US Air,etc. Good luck.

Just happened to visit the voxatc site and discovered an updated version has been released with the usual lack of fanfare. Version 5.46adds Vista 64 support, Visible taxi routes, Improved AI handling at airports, the MyTrafficX ver 5.1b fix and other features. Glad to find a distraction from the cat fights going on at the FSX forum. My thanks to the developers for their continuing efforts to improve and expand this ATC simulation.

As far as being overwhelmed by arriving aircraft, I had that happen at KSEA when using VoxATC and My TrafficX. I tried a number of things to fix this issue but reindexing a couple times seemed to be the cure. I have an older AthlonXP based PC and so generally keep my traffic level below 50%. Before loading my desired flight I always load my default flight with the stock C172, cold and dark, clear weather, a mid sized stock airport and then load the desired saved flight with flight plan over my default flight. Once the flight loads I select the desired aircraft. After the aircraft is loaded I start VoxATC. Because VoxATC is using a big hunk of my midstream PC, I click on FSX settings, general settings and listen for the initialization, including the initial AI aircraft, to complete. At this point I return to the cockpit and proceed with my departure. I am not using acceleration but do have both SP1 and 2 installed. Generally, I have had very good results with both IFR and VRF with VoxATC-X. Good luck.

FIXED! VoxATC support comes thru again. If you have MyTrafficX ver 51b installed and start having issues with the prompter hanging up on ATIS and Clearance Delivery email VoxATC and request the MTX fix. Tegwyn and I discussed my issues and he updated to ver 51b and came up with a fix in just a couple days. Thanks again for the responses posted here. Now, back to flying.

Zane, Since you recommend using scanAFD to check for duplicate AFCADs have you found a way to point it to FSX. When I run a scan it is only checking my FS9 files. I ran a search on this issue but it appears that scanAFD will not work with FSX. Thanks again for your assistance.

In my case there appears to be a number of conflicts between VOXATC and a number of files in my scenery library. I deselected all non default scenery entries and reindexed VOXATC which then worked properly. I then started adding back scenery and reindexing until the problem reocurred. I found there were issues with a freeware file, KSEA_asbuilt.bgl, Vancouver Plus_1 scenery and My TrafficX. Earlier in this post, Zane suggested checking for multiple AFCADs which might cause issues with VOXATC. This problem ocurred months after I installed the files and scenery which is perplexing. For now I have decided to do without these scenery files until I can check further and determine the specific files causing my issues. Good luck.

FIXED! The problem was caused by a BGL file in my addon scenery folder. How a scenery bgl file for KSEA could hose all airports is beyond me. Zane,thanks again for your assistance.

The aircraft's heading indicator is a gyroscopic instrument that drifts off course over time. In the real world you align the heading indicator to match your compass on the ground before departing. During flight it is necessary to periodically realign the heading indicator (also known as a Directional Gyro) which is accomplished only during level flight to insure an accurate compass indication. Unless you enjoy total realism, turning off the drift feature as suggested will work just fine.

I am having this issue all over not just in the PNW. I haven't installed any other software recently as I try to keep my sim PC as pristine as possible. This issue just seemed to come out of the blue. To be honest I have been neglecting FSX lately as I have been involved with a new mistress, Space Shuttle Mission 2007. Talk about an awesome piece of work. Going EVA is incredible especially if you have the 3H2GO and Track IR. I have also been spending more time with FS9 as I have a large collection of small airports for WA state that won't work in FSX such as Emma Field. Back to the problem at hand, Tegwyn sent me a utility to generate a log file which might shed some light on my issue. I hope to install it and get the log file over to him shortly. Thanks again for your help.

Zane, thanks for your response. The problem seems to be occuring system wide. I have been flying from KSEA to KPDX, my favorite flight, without any issues until recently. I have checked for duplicate AFCAD's especially in my AI addon program, My TrafficX which has caused issues in the past. I will be emailing a log file to VOXATC support and see if they can figure out what's going on. This program really adds alot to the flight sim experience so hopefully these issues will be resolved.

I have been using the current version of VOXATC for FSX for quite a while now and suddenly I cannot get past ATIS. When VOXATC enables I switch to the ATIS frequency as prompted. After listening to ATIS the promper displays "tune to XYZ clearance XXX.XX", which I do. The proper frequency is displayed on the aircraft radio display. The ATIS transmission continues and the prompter window doesn't update. I have reindexed several times and deinstalled VOXATC and reinstalled with the same results. I have made no major changes to either FSX or my computer. Any suggestions will be appreciated.