I've been trying out a few voice control packages lately (IYP, MCE and VoxATC). Each package has it's good and not-so-good sides but as I have tested them I have realized the ATC aspect is the most importan one for me so VoxATC is a "likely choice" right now. However, before I go ahead and spend my

I can't answer your Vista 64 question specifically (I use 32bit) but I was in a similar position to you and invested 70 pounds on the full VoxATC DVD (with voices and the UK enhancement).I have tried so hard to love this software! I never wanted to be a 'VoxATC basher', and I'm not, it has some great things about it but it IS generally buggy (not just the AI) situation.There are also some dubious things about the way it seems to draw memory and CPU resources too - it doesn't seem to directly pull FPS down, but lock-ups, pauses and generally unrelaible FSX performance are regularities for me using VoxATC.The AT&T voices are really, really good and LIGHTYEARS ahead of any of the MS voices. The ATC methodology is also really good - it's just the stability and reliability that the VoxATC guys have got to improve.I'd struggle to recommend it at present - considering it's relatively high price (which is driven by the license costs for the AT&T voices I believe).David.

Cepstal provides third party voices as well. Pretty good but a bit pricey (~ $20-$30 USD per voice if I remember correctly).I'm with David on a cautious recommendation. I use VOXATC and enjoy it but lets just say I am eagerly awaiting the next upgrade. Performance has not been an issue for me but rather how VOXATC handles assigning IFR approach clearances. Seems I am "fighting" with the program to get the approach I want assigned to me. I have not found the program to buggy nor has it slowed down my machine. I also like that I can start VOXATC while enroute. How I typically use VOXATC is to combine it with VATSIM. I use VATSIM for my takeoffs (and landings if a VATSIM controller is available) and I use VOXATC for the enroute portion where VATSIM seldom has coverage anyways. That way works quite nicely for me and made the whole package worthwhile for me. Perhaps with the next upgrade or two, it will handle approach assignments better.Hope this helps!

Cepstal provides third party voices as well. Pretty good but a bit pricey (~ $20-$30 USD per voice if I remember correctly).I'm with David on a cautious recommendation. I use VOXATC and enjoy it but lets just say I am eagerly awaiting the next upgrade. Performance has not been an issue for me but rather how VOXATC handles assigning IFR approach clearances. Seems I am "fighting" with the program to get the approach I want assigned to me. I have not found the program to buggy nor has it slowed down my machine. I also like that I can start VOXATC while enroute. How I typically use VOXATC is to combine it with VATSIM. I use VATSIM for my takeoffs (and landings if a VATSIM controller is available) and I use VOXATC for the enroute portion where VATSIM seldom has coverage anyways. That way works quite nicely for me and made the whole package worthwhile for me. Perhaps with the next upgrade or two, it will handle approach assignments better.Hope this helps!

I do use Vista 64 and found that the DVD voices (including UK) would not work with VoxATC. I was advised to purchase from Cepstral. It all works well now, if a little buggy, but the voices have made it a very expensive addon. I too look forward to later versions. It does add realism to an already excellent FSX.

...How I typically use VOXATC is to combine it with VATSIM. I use VATSIM for my takeoffs (and landings if a VATSIM controller is available) and I use VOXATC for the enroute portion where VATSIM seldom has coverage anyways. That way works quite nicely for me and made the whole package worthwhile for me. Perhaps with the next upgrade or two, it will handle approach assignments better.Hope this helps!

<offTopic level="I guess">Yes, VATSIM is another "natural next step" for me and my hobby so I'm glad you bring it up. I'm from Europe but I fly mostly in the US and Australia (the current "addon situation" renders these continents prettier than Europe). How would you say VATSIM works in terms of controller coverage? Will there be controllers available in the US/Australia during the hours I usually fly or would I be de-facto limited to Europe?</offTopic>Another VoxATC question: The AI sound is bordering "silly" since I started my VoxATC try-out. Is that because of VoxATC or is it just my imagination playing tricks on me? Can anything be done about it (providing VoxATC is the culprit)?Cheers/Jonas

...The AT&T voices are really, really good and LIGHTYEARS ahead of any of the MS voices. The ATC methodology is also really good - it's just the stability and reliability that the VoxATC guys have got to improve....David.

I tried out the test flight provided by VoxATC (VFR Kansas City --> Eppley) but couldn't complete it. Somewhere along the way ATC stopped issuing instructions but continued to call out another aircraft, apparently 1 mile ahead on the same course as me, 500 feet above. I could neither see that aircraft nor complete the flight as ATC had completely abandoned me. I flew past Eppley with no instructions on how to proceed. I'm not terribly good with ATC so it might be as it should (maybe I should have terminated the VFR flight myself?). Another issue along that flight was when I mistakenly tried to listen to Eppley ATIS on COM2, oblivious of the fact I had turned FSX ATC off and was therefore met with complete silence. Having done that VoxATC couldn't here me for some time. It kept calling out other aircrafts and I copied it every time but VoxATC didn't "hear" me and kept requesting I copy its call-outs. Then suddenly VoxATC called me with "Minneapolis Center" go ahead", although I had already called in with that center. I just called in again and after that VoxATC could here my calls. I then tried to leave the frequency to listen to Eppley ATIS on COM1 instead but was still met with silence although I was now within 20 miles from the airport.My general impression so far is that VoxATC is rather intolerant for mistakes.Are these issues you have experienced as well?/Jonas

Yes, I would agree that VoxATC is not the most forgiving program. Say it their way or ATC will not hear you. However, there should be blue text in the VOXATC box that gives you the exact verbage ATC is looking for with each callout. There are also to other helpful hints. I think it is the J key or the K key that you can press and get a list of options (such as request a different approach). The other key gives you a history of past callouts, I believe.I'm glad I have VOXATC but it definitely could improve some in the next revision. From reading the boards, sounds like IYP and MCE are looking actively at this space. My opinion though, at this time, is that VOXATC is the winner for voice ATC.

My try-out of VoxATC isn't going well. So far, I have yet to complete a full flight. Every flight so far has ended with VoxATC getting stuck in one state or another from which it never recovers. This happens somewhere en route and I have yet to initiate a descent and approach. I'll read some more and give it a few more chances but unless it drastically improves I'm going to have to skip this piece of software for the time being.I only wich someone text-to-speech-savvy individual would take up the challenge and crate a voice control module for Radar Contact! /Jonas

My try-out of VoxATC isn't going well. So far, I have yet to complete a full flight. Every flight so far has ended with VoxATC getting stuck in one state or another from which it never recovers. This happens somewhere en route and I have yet to initiate a descent and approach. I'll read some more and give it a few more chances but unless it drastically improves I'm going to have to skip this piece of software for the time being.I only wich someone text-to-speech-savvy individual would take up the challenge and crate a voice control module for Radar Contact! /Jonas

Same here, moggel.. I have VoxATC with the AT & T voices, Radar Contact and FDC, and I found none of them are sufficiently flexible, reliable or accurate enough to guarantee a successful flight. I use the LSH Maddog along with FS Passengers, and so a successful flight is mandatory if you don't want to mess up your FSP record. Fighting a virtual controller who ignores you or steer you the wrong way, has got to be the "Mayday, Mayday" of all problems.So they all now sit on my "E:\Stuff" drive gathering virtual dust.... :(

Same here, moggel.. I have VoxATC with the AT & T voices, Radar Contact and FDC, and I found none of them are sufficiently flexible, reliable or accurate enough to guarantee a successful flight. ...

I have used Radar Contact for a few years and I have actually never had technical problems with it. It could be more flexible of course but I have never abadoned a flight because of RC getting stuck like VoxATC does.BTW: What is "FDC"?/Jonas

Yes, I would agree that VoxATC is not the most forgiving program. Say it their way or ATC will not hear you. However, there should be blue text in the VOXATC box that gives you the exact verbage ATC is looking for with each callout. There are also to other helpful hints. I think it is the J key or the K key that you can press and get a list of options (such as request a different approach). The other key gives you a history of past callouts, I believe.

Hi,Concerning the 'arrival menu' it is written in the documentation: 'When being vectored to an approach or after being cleared for a non-vectored approach the ArrivalOptions Menu is available. From this you can select to request any of the approaches available atthe destination airport.'Does this mean that I can select an NDB approach at an airport that also has ILS approaches available? How does VOXATC know about which published procedures exist at any given airport?Thanks,Alex

Same here, moggel.. I have VoxATC with the AT & T voices, Radar Contact and FDC, and I found none of them are sufficiently flexible, reliable or accurate enough to guarantee a successful flight. I use the LSH Maddog along with FS Passengers, and so a successful flight is mandatory if you don't want to mess up your FSP record. Fighting a virtual controller who ignores you or steer you the wrong way, has got to be the "Mayday, Mayday" of all problems.So they all now sit on my "E:\Stuff" drive gathering virtual dust.... :(

This is my exact dilemma too. So what do you use then? I know about the usual reply about 'go fly online' however I truly hate the empty airports and the sporadic coverage.By FDC you might have meant PFE (same company) :Straight FaceAlex

This is my exact dilemma too. So what do you use then? I know about the usual reply about 'go fly online' however I truly hate the empty airports and the sporadic coverage....

Where do you usually fly, and at which hours of the day? I'm considering VATSIM myself but I'm reluctant ATM as most people seems to agree with what you say.Back to VoxATC...Seems the simming world is in great demans for what VoxATC attempts to deliver so it is a big shame it doesn't. I have been running Radar Contact for several years and I'm very happy with it but the lack of voice recognition is a major drawback to me. Being forced to read back would make a enormous difference. With RC you just press a key, just like with the default FSX ATC, to read back. It simulates having a co-pilot but that's not really what I'm looking for.Instead, being able to speak to the controller increases the realism tenfold. I feel the best solution would be a voice recognition interface that sits between Radar Contact and the user. Radar contact would then act as the controller, emitting data to the VC-interface and sound to the speakers. The VC-interface would then receive voice input from the user, compare it to the controller's (RC) state/expectations and decide what to do. For example, a correct read back would simply initiate the controller's "Confirm" option while an incorrect readback could either force the pilot to read back again or have the controller software to ask the pilot to read back the incorrect parts (VoxATC does that but RC have no such option).Such an interface could possibly be built to allow other software packages to act as the ATC "brain". I think there's lots of money to be made for anyone willing to accept the challenge.Go for it! :( Cheers/Jonas

Where do you usually fly, and at which hours of the day? I'm considering VATSIM myself but I'm reluctant ATM as most people seems to agree with what you say.Back to VoxATC...Seems the simming world is in great demans for what VoxATC attempts to deliver so it is a big shame it doesn't. I have been running Radar Contact for several years and I'm very happy with it but the lack of voice recognition is a major drawback to me. Being forced to read back would make a enormous difference. With RC you just press a key, just like with the default FSX ATC, to read back. It simulates having a co-pilot but that's not really what I'm looking for.Instead, being able to speak to the controller increases the realism tenfold. I feel the best solution would be a voice recognition interface that sits between Radar Contact and the user. Radar contact would then act as the controller, emitting data to the VC-interface and sound to the speakers. The VC-interface would then receive voice input from the user, compare it to the controller's (RC) state/expectations and decide what to do. For example, a correct read back would simply initiate the controller's "Confirm" option while an incorrect readback could either force the pilot to read back again or have the controller software to ask the pilot to read back the incorrect parts (VoxATC does that but RC have no such option).Such an interface could possibly be built to allow other software packages to act as the ATC "brain". I think there's lots of money to be made for anyone willing to accept the challenge.Go for it! :( Cheers/Jonas

HelloWhat you are asking for has been available for a long time, It is Called SAPI 5.1 and is free from microsoftIt may even be on your system already.I am successfully controlling Radar Contact by voice.I am using shoot v1.6.4 but there are many other alternatives, They are all using SAPI 5.1.for Payware have a look at http://www.itsyourplane.com/.It has Radar Contact commands available

HelloWhat you are asking for has been available for a long time, It is Called SAPI 5.1 and is free from microsoftIt may even be on your system already.I am successfully controlling Radar Contact by voice.I am using shoot v1.6.4 but there are many other alternatives, They are all using SAPI 5.1.for Payware have a look at http://www.itsyourplane.com/.It has Radar Contact commands available

Yes, it's certainly possible to send voice-controlled input to Radar Contact or any other program in Windows using SAPI 5.1. In fact, that's how VoxATC, IYP and MCE does it. However, what you can do is just transform a sentence into a key press. Basically, that means you can say "press 1" and the key '1' is emitted to the software. Naturally, you can program the VC software to accept something more intelligent, like "Readback clearance" and the key "7" can be emitted to Radar Contact for example. That's pretty much how IYP does it. However, this is not what I mean by a VC interface between the pilot and the ATC "controller".VoxATC attempts to provide such an interface AND the ATC controller AND an AI solution which is a bad idea IMHO. This allows the pilot to read back a clearance to VoxATC which then analyzes it and decides on an action based on what you said. If you read back the instruction correctly all is well but if you didn't it can "understand" what was incorrect and act accordingly. You won't see that in IYP or MCE. VoxATC lets you interact with the controller in two-way communication, like you would with a real controller. At least, that's what VoxATC attempts to do. Had VoxATC been a stable reliable VC platform I would have been quite happy but the whole concept is somewhat crippled by the following drawbacks:1. It is very unstable. During my try-out I wasn't able to complete a single flight2. 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.3. It injects its on AI mechanism into FSX rather than interacting with the existing solution. This means you won't see time tables honored in any 3rd party AI package you have bought (UT or MyTraffic X). There's also a few defects related to how the VoxATC-controlled AI behaves.4. It uses synthesized AI voices and only supports five different ones (your co-pilot and male/female controller and AI pilot/co-pilot). This means there's almost no diversity in voices, like with Radar Contact of PFE. Also, even to use all five voices you'd need to buy them from AT&T or Cepstral. They cost aprox. $30 each so you'd end up spending ALOT of money and still wouldn't realize you had just changed from one center to another during your flight.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. The guys and gals that builds the ATC package(s) need to know alot about the ATC business (like with Radar Contact) and will likely have their hands full just to bring us that aspect to new levels of realism. Providing a good VC interface would be too much to ask from a handful of people, like most 3rd party studios are (unless I'm misinformed, RC is pretty much developed by one person). Also, if more than one VC interface existed us armchair pilots would be able to select the one fitting our needs in terms of price and quality. Improving such an interface (greater tolerance in phrasing, better performance etc.) would be easier since the developers didn't also have to build the ATC aspect.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