Search the Community

Hey guys, I've been using VOXATC for a while now and have had a pretty finnicky time with it. I often get fatal errors, traffic behaving weird, etc. But this all goes away after enabling/disabling a few times. One problem that has not gone away is my inability to make requests to the ATC. The program seems to understand me fine if I follow the prompts on screen; readbacks, initial contact, etc. are all working without problem. However, if I stray from the script, both in expert mode and regular, I keep getting the dreaded "last aircraft say again." I am a native American-English speaker with no heavy dialect and have run through the speech training countless times. I have a nice logitech USB headset as well. The manual says that at anytime during flight, I should be able to declare an emergency or make a request, but even if I follow the format in the manual word for word I get the same "say again" response. Has anyone else experienced this problem/worked out a fix? Best, Anish

I installed the demo to boeing 737 800 (default) but whenever I open Voxatc it closes and the recent comms just becomes white. Please help!

MT6 has rendered VOX totally unusable. See my comments in the "Anyone tried My Traffic 6" thread.

Has there ever been any word on plans to include oceanic procedures? Right now, this is the main thing missing that's making my mouse hesitate on the "Buy" button....

I was wondering, as I can't seem to find in the manual, or even an answer in the search forums, but is there a way to add the "Heavy" suffix to your Airline Callsign? as when i'm trying to add it in the setup, I get the error "only letters then numbers allowed" or something similar. Or is this just a feature not implemented (which would be a significant disappointment). I'm using v6.34

People may find that VOXATC does not like this otherwise superb scenery, and gives a 'Fatal Error' for any flight starting at KMCO. There is a problem with the AFCAD as supplied, which does not join up the taxiways crossing the bridges over the road - this seems to confuse VOXATC and it gives up the ghost. The solution is simple - using a program such as AFX, join up the taxiways so that they cross over the road, and all will be well. I'll let Tegwyn know this solution, because other airports elsewhere may cause the same symptoms. Incidentally, I would highly recommend this excellent scenery.

Hello to all I'b been doing some flight since I brought ASNext and I kept having these problem. I had it before ASNext and i'm having it now. The thing is sometimes VOXATC assigns me that STAR for the wrong runway even if the AI is taking off and landing from the correct one. Anyone experience this? Thanks

Hi there, Was just wondering if someone could please help with this following problem: So i have set up Vox Atc to use the level-d navdata and this is working well because in the procedure pronunciation editor the sids and stars are displayed for the airport that I'm trying to fly from. I have made sure that the corresponding waypoints for the sid and star are in my flight plan but when I load up my flight and enable Vox Atc the departure clearance only includes the flight level I have to fly to and the squawk code. When I taxi out to the runway the controller just clears me to fly direct to my first waypoint. This is very annoying as I fly for a virtual airline and want to everything as realistically as possible and to do this I will need sids and stars in my flight plan. I have tried everything and also have contacted Vox Atc support but have gotten no response. I hope to hear from anyone who could offer some help. Many thanks in advance, Robbie.

So I have noticed a little quirk with VoxATC that is a bit annoying. Sometimes it is spot on and sometimes it is so off the mark that it has almost killed my virtual plane. One thing it seems to get consistently wrong is the altimeter settings while on the ground. You tune into the ATIS and the green ticker starts scrolling across the top and the ticker will say Altimeter 30.08 but VoxATC will say "Altimeter 29.96" (or any number of numbers that don't match the ATIS green strip). If you have FSX ATC turned on and listen to their ATIS read back at the same time as VoxATC, FSX ALWAYS gets the Altimeter right on the strip but VoxATC is hit and miss. As the METAR data is all coming in from the exact same place, why does VoxATC have problems getting this right? VoxATC is also bad at wind directions. Twice now, while my Avilasoft EFB has said "Winds favor a 22" departure" and I create my flight plan to depart on Runway 22 (El Paso International in this example), I've pushed back from the gate and asked for taxi to the active and VoxATC is like, "Taxi to runway 4 via blahblahblah" I am like @_@ But.. but... ALL the airport traffic is taxing to runway 22... why do you want me to taxi to the exact opposite end of the runway you daffy *(%&@*%& controller!? Are you trying to kill me!? It has done this at several other airports. I file a flight plan with departures based on the wind direction being fed in by NOAA data and it gives me the wrong damn runway. Don't get me started on a STAR approach in which it wants to take me 50 miles out of the pattern to sequence me. The last several airport approaches I've had to disable VoxATC on the approach because the controller is giving me crazy instructions that I refuse to follow and the AI controller won't shutup. I love VoxATC but the wrong altimeter and wrong runways are annoying. Anyone found a work around this or know why it is doing this in the first place? I use FS Passengers X with all procedures turned on and this incorrect Altimeter settings cost me points on my final score 50% of the time.

I have a problem getting VoxATC to use SIDs and STARs. I am using VoxATC v6.05 with FSX in a Windows 7 64bit environment, with 8GB ram. Only add-ons are VoxATC, FSUPIC, Reality XP’s GNS530W, and RealAir’sLancair Legacy (my IFR platform). Here’s what I have done so far, based on reading the manual and Forum postings. 1 Downloaded the latest NaviGraph navdata FMS file for Level-D 767 format, installed into the FSX directory (Flight Simulator X/Level-D Simulations/navdata), and pointed VoxATC to that subdirectory in Advanced Settings; run the Indexer; and checked that SIDs and STARs are now available to VoxATC by loading VoxATC’s procedure pronunciation editor and checking for the presence of SIDs and STARs. All looks good. 2 Created a flight plan in FSX’s flight planner, and edited to ensure that the first waypoint after departure airport is a valid SID waypoint for the possible runways in use, and likewise ensuring that the last waypoint before the destination airport is a valid STAR entry point for all likely runways (using RouteFinder to identify the appropriate SID exit and STAR entry waypoints for the route). In my example the route is LFSB HOC LSZH. (By “ensuring a valid waypoint” I mean ensuring that waypoint name in the FSX flight plan is the same as on the SID or STAR. I note this because the specific longs/lats differ between the current navdata file and the old FSX data, but I presume that only the name is relevant.) I set the IFR cruising altitude to be at least that stated on the relevant STAR as required or likely for possible transitions, although I don’t know if this is relevant. 3 With the flight plan saved, I save the flight with the aircraft parked at a suitable gate at the destination airport (either allowing FSX to move the aircraft there when closing the flight planner, or having parked there before creating and saving the flight plan and choosing not the have the aircraft moved; I have tried both ways). 4 I then open another saved flight, check that it is fully opened by clicking various switches on the panel and ensuring they move, then close that flight. I then reopen the saved IFR flight. I understand that this is necessary to have FSX connect the saved IFR flight with the new flight plan created for that saved flight. 5. I check that the flight plan is registered for the flight by looking at the NavLog in the Knneboard, then open VoxATC, contact clearance, and request clearance for my IFR flight. I receive “Cleared to [destination airport], cleared as filed, climb and maintain flight level 60 …” No mention of the SID. 6. I have retried with different departure and arrival airports, different SID exit and STAR entry waypoints, but the result remains the same Does anyone have any suggestions? David

Greetings, Has anyone been able to remap 0-9 on a USB numeric keypad to the keyboard 0-9 for use with VoxATC under Windows 7 and FSX? I attempted to remap using registry remapping and verified that the remapping was successful in Windows 7 using AutoHotKey. However, VoxATC still recognizes the USB numeric keypad as "Num 0" instead of the keyboard "0". Thanks in advance for your suggestions. I am trying to replace the keyboard from my setup with the smaller USB numeric keypad. Cheers, Ron

Hi I have a problem when trying to install VOXAtc 6.20 for Prepar3d v2 (Addons Rex and FTX). When running the setup.exe and the indexing part comes up, suddenly it just stops. I can see from the directory that VOXAtc is looking at a non existing path (See attached image). I've tried to abort it and running the indexer afterwards, uninstalling and re-installing. Nothing works. Anyone know of this problem or a workaround? (Btw, for now its just the demo install. Need to make sure it works before buying obviously ) Any help would be greatly appreciated!

Hi all, Has anyone got VoxATC working in V4? I downloaded the demo last night and it seems to work in all default aircraft but my A2A aircraft weren't detected, and they don't have that panel in the menu. I then manually copied the panel entries into the panel.cfg file but it still didn't show up. I was wondering if it has anything to do with the fact that the A2A planes are in the Addons folder and not in the SimObjects folder. Any suggestions on how to fix this? Cheers!

Has anyone managed to get Voxatc to recognise Amazon polly voices? Pilot2atc manages to see them but with Voxatc they are not an option in the voice configurator.

Hello all-I use VOXATC and a buttkicker in P3dv2.3. I'm having difficulty with the interaction of VOX and the buttkicker. When I use the lower pitched male voices they set the buttkicker off. I then lower the frequency cut off in the buttkicker but the male voices still set it off. I have the onboard Realtek sound. Other than having all VOX female controllers and pilots (which is OK by me), does anyone know of a way to separate the lower pitched voices from the aircraft sounds? I've heard that OPUS has an interface for it, but I really don't need all of OPUS' other features.

Hi guys i have strange problem with VoxATC, I downloaded the free (7day trial) VoxATC + i added VoxPOP and downloaded and installed the Voices from VoxATC webside. The problem is that i can't hear them i tried the voice configuration and inside FSX, weird part is that when i click "Speak" button in any of VoxATC program is starting VoxPOP server and everything but there's no voice. to be specific the button stays gray for like 1-2 sec and that it. I tried checking error log but it's blank. There's noting corresponding to any SAPI voice issue. I have installed some other voices from realspeak and their working just fine (in VoxATC program and in game). Tried reinstating everything i didn't work as well. Maybe I'm blind but i didn't find any answer of the Forums... Any help would be very appreciated. Dace P.S. English is not my first language so sorry for any mistakes.

I have recently installed VOXATC 7.2 Beta on my system. When loading a flightplan, in my sim, the system displays wrong ai traffic. Example: When departing from EHAM for a flight to EDDH, 90% of all my ai aircraft at EHAM, consist of AN-74-100's of Cavok Airlines (Ukraine). Have uninstalled and reinstalled VOX, but unfortunately, no remidy. Have restarted the system and was able to replicate the problem. My system: Prepar3D Prosim737 AS16 (via client) Rex soft clouds REX Worldwide airports ###ai ORBX Global, Vector, Europe, U.S. I have dissabled ai traffic in Prepar3d as suggested in the manual and have VOXATC ai traffic at 40%. Anyaone has a clue as to where to look for a solution?

Hello, All captain sirs I have serious problem when I tried to install the VOXATC on my p3d v2.4 system. I can’t proceed VOXATC due to Net framework trouble (Just in time, refer to image link while installing. Please help me…. Thank you sir [My summarized system] 1. OS : Windows 7 64bit (SP1) Korean version Added English language pack Changed system locale form Korean to English (US) 2. Flight Sim : Prepar3D 2.4 3. Add on : PMDG 777 / FS2crew / REX OD / Ezdok Ps ) I had tried to change the Net Framework from 4.5 (Korean) to 4.5 (English) & 4.0 (English). But result is same. Sorry, I hard to upload the image to use Avsim website editor. (I'd know why the image did't see image even though I tired to insert URL image.) So, I'd like to link the address of failure image directly like below. please click it. https://docs.google.com/file/d/0B_BCJU2Wk8SONG5DdnR0dUhOd3c/edit?usp=docslist_api on the detail is See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.TypeInitializationException: The type initializer for 'com.intworkings.voxatc.FSUIPCInt' threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object. at com.intworkings.voxatc.FSUIPCInt.SetSimulatorToUse() at com.intworkings.voxatc.FSUIPCInt..cctor() --- End of inner exception stack trace --- at com.intworkings.voxatc.FSUIPCInt.GetFSFolderName() at VoxATCIndexer.VoxATCIndexer.VoxATCIndexer_Activated(Object sender, EventArgs e) at System.Windows.Forms.Form.OnActivated(EventArgs e) at System.Windows.Forms.Form.set_Active(Boolean value) at System.Windows.Forms.Form.WmActivate(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL ---------------------------------------- VoxATCIndexer Assembly Version: 1.0.5536.29229 Win32 Version: 1.0.5536.29229 ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL ---------------------------------------- BGLAFD3 Assembly Version: 1.0.5536.29222 Win32 Version: 1.0.5536.29222 ---------------------------------------- VoxATC Assembly Version: 1.0.5536.29226 Win32 Version: 1.0.5536.29226 ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

There are many options in VoxATC to fiddle with and it is very wise to spend time training with the program. I did about six flights where I loaded up the flight plans in the flight plan trainer and went through all the lines. I don't have to do that anymore. It pretty much knows what I am saying now and I can even change the tone of my voice and sound more natural when talking to it and it will take my commands. My problem that I have and I wonder if there is a way to fix this, is to make VoxATC pronounce locations correctly. Example; I take off from Dallas Love Field a lot and one of the centers I pass through is Fort Worth Center. It is abbreviated FT Worth. VoxATC likes to say "F T Center" rather than "Fort Worth Center". Is there a way to train VoxATC how to pronounce things like this correctly? It's REALLY bad about pronouncing VOR stations.

I upgraded to 6.49 last night for Prepar3D. I uninstalled the previous version as instructed and installed the new one. Install went 99% fine. I noticed the uninstaller did not remove previous VoxATC entries from the panel.cfg files of my aircraft and just installed new ones. I fixed that as it was interfering with my ability to push buttons in the virtual cockpit. Everything looks fine except for one horrific thing that the previous version did not do. The simulation will now pause for a second every few minutes. All sound cuts out, all the lights in the virtual cockpit I am in will fade like there is a power problem, the VoxATC window will clear whatever text is in there and say 'Sim Paused' And then everything will unpause and go back to normal. It does this far to often. It shouldn't be doing it at all. I went into Advanced Settings and made VoxATC a High priority and even gave it 3 of my 6 cores to play with, keeping it off of the 3 cores that Prepar3D is using to avoid any simulation slow downs. Obviously, that has failed. Anyone else experience this kind of problem before? Is there a fix? Also, my test flight with this new VoxATC was KMDW to KIAD. VoxATC did great apart from pausing the sim two dozen times in the hour long flight UNTIL I got to approach control. I switched to approach, the controller gave me my vector and altitude she wanted me at and that was the last I ever heard of her. The VoxATC window had 'Fly the I L S 1C approach'. The path she put me on made me cross right across the approach path at an angle and I just kept going for about 12 NM in the direction until finally I took matter into my own hands. I brought it around, got into the final approach pattern, locked on the ils and started my glide scope in. Still nothing. I got no final approach call outs, no change to the tower frequency, no cleared to land. ??? I never had VoxATC do that to me ever. Yeah, it would give me wrong runways to land on and the ARTCCs still love handing me off like a ping pong ball (even in this new version the do it like crazy) but VoxATC has never just gone silent, at least not without a FatalError in the VoxATC window but that didn't happen. Did the approach controller just die of a heart attack at their station and that's why I heard no more vectors to final? That's some hardcore simulation there! I kid! I kid! Anyway... I don't kid about anything else I said. Did VoxATC 6.49 not install properly? What settings did it set to suddenly take all the power out of Prepar3D and make it PAUSE? If there is no answer to this I will revert back to 6.46 and live with wrong runways being assigned on final. I CANNOT live with the sim pausing all the time. This is how we end up in a padded cell. Thanks everyone for your suggestions, insights, insults. I will contact the vendor as well about this.

Hi everyone, I got voxatc about few weeks, but I frequently got " fatal error" during the beginning of the flight (haven't taken-off"). I want to add more voices so I installed some voice. I didn't get this error before installing any new voice (ie only the default voice Anna...). First I install the voices from Neospeech. Then I started to get this error message. After that somehow I knew that Neospeech may lead to error with voxatc in fsx so I uninstall it. Then I found that voxatc have voice packs (voxpop) to download so I downloaded and installed it. However, "fatal error" still happens on every flight. Then I uninstalled it. I then tried AT&T VOICES, also cannot get rid of this error. I have already run the indexer many times, but the problem is still there. I almost get this error on EVERY FLIGHT!! It is so annoying to me and I get very frustrated about it.... Is it normal????? I dun think it is...... anyone help plz?? I will also use FDC cockpit, FS Global Real Weather, FS captain, pmsound, fspassenger during the flight I know that voxatc will control AI traffic, I also installed Mytraffic 2010, is it lead to the error???? Please help me... I like voxatc very much, and the interaction, but just the dame fatal error!!!!........thanks! My voxatc version is 6.20

Hi all, this is my first post and i know this question has been asked around alot but there has been no definate ansews for my needs. First of all I use ultimate traffic 2 and world of ai and i was wondering if they could both be used in VOXATC 6 UK. I know ut2 can be transfered with the special 'bridge' but what about woai? Secondly are the skies still quite empty doing this because almost every comment about voxatc say the airports are ok however the skies are practically dead!! Is the traffic realistic i know they follow sids and stars but i mean you dont suddenly get 20 planes at once trying to peform a (perfect ?) landing everytime? Do planes hold at different holding points for an example do a380s go futher up to the last holding point compared to little ga planes? Or do they all go to the same holding point like default fsx ai? Sorry as i know they is ALOT of quesions but there is so much i want to know cause I really want to purchase this product :) Thanks!

Hello! I just did a trial flight with the demo version. I flew with a c208 from Zurich to Innsbruck. I've been using LOWI as a base in AirHauler and wanted to see how VoxATC handles the challenging approach in to LOWI. Here's the route I filed (@FL190): LSZH DEGES Z2 OSDOV M738 MADEB N606 ELMEM LOWI Things got a terrifying twist when I was vectored of ELEM1A arrival. "Turn left heading 055, descend to 3500". After the turn, I was nose to nose with a 13000ft mountain and descending! After that, I had to fly the approach visually, while VoxATC was repeating the heading and altitude that would smash me straight into a mountain. So before I break out my credit card, what can I do to make VoxATC aware of the surrounding terrain? I looked at the Level-D (cycle 1210) navdata that I requested VoxATC to use. There were no altitude restrictions for the STARs to LOWI. Only the localizer approach for runway 26 had correct altitude constrains. What is the correct way of teaching VoxATC the altitudes that are found in these plates: STAR http://charts.vacc-a...AR_07082012.pdf and approach http://charts.vacc-a...st_07082012.pdf? Thanks for the help! EDIT: Found more suitable charts. Original was: http://data.x-plane.com/Docs/LOWI.pdf

Ok so I've been running Flight Simulator X (FSX) for a while now but after loading up Prepar3d (P3D) I decided I liked the changes and decided to take the plunge. <Content removed by Administrator SpiritFlyer as it breaches the AVSIM ToS>

I have been trying to use VoxATC with P3D. It does run and is functional but whenever I run the Indexer it picks up the FSX directory rather than P3D and I cannot find a way to change it. As a result, where I have addon scenery I seem to get planes parked half in buildings etc. I use FSXtoP3D to install into P3D and everything else works fine. Any thoughts appreciated. Cheers