2. It is too rigid. You have to phrase your input word by word as VoxATC expects it or you will be ignored. This makes it hard to use and degrades the realism. In the end, you tend to just read a text provided by VoxATC.In my opinion a separate "Voice Controlled ATC Interface" (VCI) that interacted with the ATC mechanism would be the preferred architecture and would allow greater freedom for both end users and developers. This is how I'd like to see it:User -- voice --> [VC interface] <-- data --> [ATC controller *] <-- data --> [FSX, incl, AI]* Radar Contact, FSX default ATC, PFE etc./Jonas

Jonas - thanks for the well thought out response. I completely agreePoint #2 - I really enjoy VOXATC but agree that it is too rigid. This is likely why I really relegate VOXATC to enroute flying and use VATSIM for Departure and Arrival (as long as a controller is available..)"Voice Controlled ATC Interface", VCAI - Brillant! This would add alot of value to my flying. For me, this would likely be Radar Contact and this VCAI program.

...Point #2 - I really enjoy VOXATC but agree that it is too rigid. This is likely why I really relegate VOXATC to enroute flying and use VATSIM for Departure and Arrival (as long as a controller is available..)...

I have only used the VoxATC trial. Would you recommend I still get the full version or shall I expect the same lack of quality? Are you usually able to complete your flights with VoxATC as the controller (when/if you're not on VATSIM)?

...For me, this would likely be Radar Contact and this VCAI program....

Yes, had a VCAI solution existed I would also have picked Radar Contact as the controller. That would be the perfect combination of really good ATC, diversity in voices as well as a slick AI interaction.Cheers/Jonas

Jonas - thanks for the well thought out response. I completely agreeThis is likely why I really relegate VOXATC to enroute flying and use VATSIM for Departure and Arrival (as long as a controller is available..)

May I ask how you go about doing that? Do you stay connected to VATSIM while using VOXATC enroute? What about VOX's AI?Alex

Do you stay connected to VATSIM while using VOXATC enroute? What about VOX's AI?Alex

Hi Alex,Here is what I do- Start up my flight. The VoxATC window opens and I minimize it. Importantly, I do NOT click "enable"- Start SquawkBox for VATSIM- Depart airport using VATSIM- Tower hands me off to Center. Center usually keeps with me for 100-200 miles and then transfers me to Unicom with a comment to call Center close to my arrival airport- At this point, I disconnect from Vatsim (by sending a text to Center and closing SquawkBox)- I then re-open VoxATC's window- Click "Enable" in VoxATC window- VoxATC pick me up seemlessly- When VoxATC starts giving me vectors or clears me for the visual (while in IMC! -- ugh!), I shut down VoxATC and simply fly the approach the way I think I would have to in the real world.Hope this helps.Doug

Jonas, you make some interesting points and I would like to comment on them.1. VoxATC is unstable. The software environment VoxATC has to operate it is anything but consistent. No two simmers systems are going to be the same. VoxATC depends upon the OS, FSX (its components and add-ons) and Voice recognition all working well together. This may not happen

...To reiterate, the developers of VoxATC are only too happy to help out with configuration problems and teething troubles so that people have a working system they are happy with before they buy. We will even extend the trial period if needed.I urge any existing users who are having trouble to also contact support via www.voxatc.com.

Teqoid, I assume you are connected to the VoxATC development? I followed your advice and posted a request for support at www.voxatc.xom but was met with an ASP.NET standard error message (the one advicing the reader to turn on custom errors to see the actual error message and stack trace).So, I posted you a forum PM instead. It contains my email address and a request for assistance.Cheers/Jonas

Hi Moggel:Be aware that VoxATC for FS9 doen't work in Vista. It's a great programme. I've been using it for about four years now but recently decided to go back to FS9 until I upgrade my system to work comfortably in FSX. I had to uninstall my Vista 32 HDD and reninstall XP to use VoxATC.Be sure to do lots of training in "Flight Plan Trainer". The more you do the greater will be the recognition from VoxATC. Whenever I fly to a "new" destination, I use the Flight Plan Trainer for that flight.Also, IYP is a great complement to flight simming but I've had problems with it working in conjunction with VoxATC. The IYP progammer is doing a good job of trying to overcome its limitations but so far it hasn't worked well for me. The problem appears to be that Vista hears my VoxATC communications then "willy-nilly" starts to make unauthorized changes...most annoying on short final. Another issue I had with IYP and VoxATC working in unison is one or another of them would start to pout and go silent if I used the opposing progamme to much.In my case VoxATC is the most important of the two so I've dropped IYP for now.Also, if you are using add-on AI you may want to delete the MS AI. They will occasionally conflict with your approach. And, if you are using extended wake turbulence you will have unwanted turbulence from that 737 that just passed you on short final.Conclusion: go ahead and purchase VoxATC but be sure to follow the instructions in "Help" carefully. If you get into trouble, review where you went wrong and re-do the flight. It will only get better.Sox.Conclusion: go ahead and purchase VoxATC but follow the instructions carefully in Help.