supercoup

I used the program, It worked rather well. The whole problem I have is that I had not known at the time of purchase but after every 6 or 7 times of offline use, you have to go online and renew the activation, which is very troublesome. Plus the fact that I use it in an actual Flight Simulator running off 4 computers and do not connect to the internet unless there is an up date to a program which is very rare. They say all you need do every time is insert the serial# and email address but that rarely works. Im just not going to use it. i fly in fsx and the default 737-800. I hear that FSUIPC may have something that would work, im gonna get into that. Frictionality is a good program but the activation system is rediculous.

Ive seen some postings here about a delayed push to talk in VoxAtc. It does happen. I fly in a regular walk in, sit down simulator that mimmicks a Boeing 737-800. This may sound a little dated but I still run FSX cause I can undock all my instruments and spread them out where I want them. Anyway, back to Voxatc. I installed Voxatc, FS2Crew and a bunch of other stuff. I have installed in the main FS computer a sound blaster Recon Tactic 3D sound card and the headset that goes with it. Its about 10 years old. I tried updating the driver for it and they just dont update the card any longer, its too old. So I used the last driver they had to offer. As soon as I installed it, some of the voices that were missing from FS2Crew suddenly appeared but so did the DELAY IN VOXATC PTT. I removed the driver and just used the window driver an Vox got back to normal but I lost a certain part of FS2Crew. SO, if your having a problem with Voxatc and "push to talk" I can assure you its either your sound card or the driver. Old drivers not made for new operating systems systems tend to corrupt the Windows registry. Luckily, I had a restore point to go back to when all was working well. Graphics drivers have been known to play funny tricks with the registry too. If your components are old, even though they say that the driver is compatable with the newer operating systems and may very well be, the components are not, especially when run on their dedicated drivers. Here's what I did. Instead of buying a new soundcard, cause I dont know if the drivers will be any better than the one I cant use, I enabled the onboard sound and Im using that for all the sounds of FSX, FS2Crew and other programs I use. I left the Sound Blaster card in the PCIe slot and use it for VOXATC, with the "windows" driver, not sound blasters. Now Vox works flawlessly. No delayed PTT, no crashes, no miss communication etc. and the onboard sound with FS2Crew? I hear things now I never heard before. Boarding sounds, flight attendants, fuelers. It opened up a whole new world. Moral of the story? Watch what drivers you install into windows. They attach themselves to the registry and sometimes corrupt it. That makes an operating system very unstable. There are many drivers that were made for windows 7 that they say are compatable with windows 10, they might work but they're not "as" compatable as they should be. Better if they were made for windows 10. Just in case somebodies still suffering with the problem, like me. Hope yo find this helpfull.

Can anyone tell me what the trigger phrase is to go from S.CREW/ENG to TAXI ? Ive tried just about everything. The only thing that works is clicking the button to change it. Aslo, I was getting the FO asking if fuel was ok and the FA telling all passengers on board but it just stopped. Any help would be apprecieated. FS2CREW DEFAULT 737 VOICE COMMANDER EDITION Thanks in advance

Hi Bryan: Im flying FSX and using FS2CREW Default 737 voice commander. I have 2 small problems. First I go through prestart checks, then before start checks just fine. When the mode changes to S.CREW/ENG, It doesnt change to "TAXI" CHECKS.I have to change it manually. After "BEFORE START CHECKLIST" I thought at first movement prior to engine start to announce "CABIN CREW ARM SLIDES" would change it from S.CREW/ENG to "Taxi" but nothing does it except manually clicking the button to change it. Got me goin crazy. Also I heard the "ASKING IF THE FUEL IS OK" one time and never again nor do I hear the FA tell the captain that all passangers are boarded. Everything else works just fine, audio is good, speech recognition is good. Im running GSX and using them for pushback so "AES" IS yes, pushback required is no as is doors and gate dep gate arr. Two very high end machines are running this walk in simulator, so I dont think the problem is there. I did hear them ask about fuel and passengers once after a reinstall, but that was it. I hope you could help Thank you

yes fsx sliders at zero. the app-data mentions incompatable program. Heres what happened. i had an old program of traffic 360. I installed it and it didnt work right. i uninstalled it and ever since then, No voxatc traffic. I think somewhere , voxatc still thinks traffic 360 is still in there. 360 must have left something somewhere after uninstall and vox is recognizing it, I liooked for it but just cant find anything. I did a restore point to before the install of 360, same difference. I believe it to be somewhere in FSX since traffic 360 resided there, but where. Vox is still picking it up as being there. ANY IDEAS??

I had a sound card problem that corrupted Voxatc so I uninstalled it and reinstalled 7.43. It works fine but I have no AI traffic. Ive adjusted all the sliders in Voxatc and in FSX. Vox initializes fine but without poppulating the AI traffic. Any help would be greatly appreciated Thanks