john1383

It's not satisfactory is it? Although I have vox working OK in P3d v35, I am not happy with it being a bit of a bodge to get it to work, and the mig tool is not ideal by any means. At the moment I am using one of the other "voice" atc offerings which is being developed currently, and will continue to use it until "7" comes out and if it does I will reassess the situation. i'm getting a bit old for waiting around with no communication other than rumours. "Moving on" might be a good idea in the meantime.

They can pause for a long time sometimes! But if it does not continue at a bgl file you could move the file somewhere else and see if the indexer progresses any further without that file stopping it. Make sure you give it plenty of time to work though.

yup

I can't help exactly as I use the "copilot" function which tunes the radios and saves having to use the speech recognition feature and I have never had any trouble with Vox using it that way, although I do intend to try to use voice commands at some point in the future. Anyway. all I can think of is for you to do a reinstall of Vox atc and make sure the indexer completes completely, and then go to the start menu and configure the various option menus that are available such as voice setup, and settings. Remember too that the traffic should be set to zero in FSX as Vox generates its own traffic. When I used FSX, long ago, Vox always worked fine.

Bob, it looks like you have buy one of the Ivona "partner" applications which then allow you to install the voices in Windows. Once installed Vox seems to know they are there and they appear in the voice configuration thingy for you to choose if you want. These partner things are not cheap from what I can see, but you can try the voices before buying which helps. I am actually 69, so I am hanging on by a thread! John

Glad you fixed it! Like Mike I use Ivona voices with Vox, and the MCE (Multicrew Experience) application. When I bought them some years ago there was an offer of three voices at a reduced price, which is what I went for. Their installation into windows is straightforward, once you have bought them(!), then you can choose which to use in the Vox voice configuration option. Once installed you can use Ivona voices with any application that allows voices to be imported. Update to the Ivona thing: I had a look on the Ivona website and I came away totally confused, and I have no idea how an individual user can now buy some voices to use in Vox. It must be possible but I must be getting old because I couldn't see how to buy anything!

If the Vox atc box, with the enable/disable option, doesn't appear when an aircraft is loaded in P3d, the first thing I would do is press "alt" if the P3d menu bar is not showing, then open the "vehicle" drop down menu, go down to the "instrument panel" option, open it and see if there are two Voxatc entries in it. If so, click on the voxatc option and the box you need should appear on screen. For some reason I have to do this with some aircraft in P3dv3. This is assuming the voxatc lines have been added to the panel.cfg for the aircraft when vox was installed, or later by running the "voxatc panel setup", from the voxatc start menu. You can check if the lines have been added to the panel.cfg file for each aircraft by going to sim objects/aircraft choose your aircraft, open the "panel" folder the open panel.cfg and you should see two new "voxatc" windows added to the windows list. If the new vox entries are not there then vox installer has not modified the panel.cfg file. I have nothing networked in my setup , I suppose that could cause differences in your and my success in running vox in P3d, but it shouldn't! If the box does appear then don't forget to load a flight plan and be at that flight plans start airport before you click on "enable" or you may get an error message. Good luck, hope that helps! By the way I have never had to copy "gauges" anywhere or move "simobjects" (misc?) either. I don't know why that is needed. I just run the voxatc 6.52 installer after enabling the migration tool, and it does everything.

Yes, the last time I installed it the indexer took a while but did finish ultimately. I have tried to install it previously in other P3d versions and it has stopped at the indexer stage but I don't know why. If it stops at the airbus 321 and you don't intend to use that aircraft, you could move it out of the P3d/simobjects folder so the indexer doesn't try to scan it, and see if it goes further. Or, when asked which sim you are using, say P3d and not FSX, and see what happens. My Voxatc is within the P3dv3 folder, if that makes any difference, and I run it as an administrator. Or wait for version 7! I promise mine does work, but not everyone who has tried it has been successful, probably due to minor differences in computer setups etc.

Sorry, I am not Samster, but I read your post and have a few minutes spare...! We are hoping for version 7 in the near future which will install into pd3 v3 without needing the migration tool. In the meantime you should download Vox atc version 6.52 from its website unless that is the version on your CD. You must also have the latest version of the Migration tool. Once you have it and have bought a registration key for it, run it's installer and follow the onscreen instructions, putting in the registration key when requested. Once it is installed, enable it, by clicking the appropriate onscreen box. Then run the Voxatc installer voxATCinstall.exe , version 6.52 At a point in the process you will be asked which simulator you are using, Although I am using P3D someone else said click the FSX box at this point, which I did, and it has worked OK since. Give the installer plenty of time to run through the indexing stage, it may seem to hang but it probably will eventually finish OK unless something else is not quite right. Then you have to configure the Vox options and apply the registration code which I presume is on the CD. I keep the migration tool active but I will remove it completely if version 7 does what it is supposed to. Once version 7 is out most of that will be unnecessary I hope! Hope that helps, but I may have missed something, or made a mistake in which case I am open to correction by anyone, if required.

I'm glad it worked, but what we need now is a proper Vox installer for P3d v3. Hoping for good news in the near future! Fingers crossed.

Have you tried installing Vox using the latest Flightsim Estonia Migration Tool? It seems to make Vox work in P3d for those who have tried it. It is not a free utility, unfortunately.

Probably a daft suggestion, but have you loaded a flightplan and is the aircraft positioned at the departure airport of the flight plan, before you click on enable?

I have experimented with the other atc offerings, and reinstalled Vox into P3dv3 using the migration tool, and it is the easiest and so far the "best" one for me. I think I will stick with it for now. It seems to work fine in P3d.

Will do, thanks Dave. John

Thanks, Dave, 20010 stopped that error. Another thing, which doesn't seem to affect anything else, is that after I have been given clearance to takeoff, the yellow text appears with the ~ in front of it, and I press the sayit button as normal to acknowledge the instruction..but this time the green text does not appear after the instruction has been repeated. The green text always appears in every other case when an instruction is repeated. I am not sure whether to keep "saying it" hoping the green text will pop-up or just assume all is ok! John

I would just like to report a similar problem when flying from EGNT to EGPH (UK) when told to contact center, I dial in the frequency, chose the sayit phrase to report current altitude and an unhandled exception occurs when pressing the sayit button. This has happened both times I have tried this flight since updating to 2009. I have no other log info on this I am afraid, nor the frequencies used.

Now I am getting the hang of PF3 I must say it is doing what I need it to do, and rather well, so far. I use two monitors though which allows me to have some of the helpful extras like the keypress display index and the taxi monitor gauge not interfering with the monitor upon which the "flying" takes place. I will certainly use it until any new Vox comes out, then I will see which suits best.

I am not sure how Vox or My Traffic interact, but I installed My Traffic in a folder called "my traffic professional" in my P3d...I use P3d... directory, in my case D:\P3dv3\my traffic professional. When I ran the Vox indexer I noticed it ran through the contents of the "my traffic professional folder". And when I run P3d , load a flight plan, and go to the relevant airport, start Voxatc there is plenty of traffic! You could try uninstalling My Traffic and reinstall it in your FSX directory and see if it helps. Make sure My Traffic is installed properly apart from that, in P3d it is a bit unnecessarily complicated... perhaps not so in FSX.

Gary, the SDK files are installed from either the FSX Acceleration DVD if you have it, or disc2 of the original FSX discs, if I remember correctly, but as you suggest that may not be your problem. The SDKs are installed in the C:\ drive and once you find them, there should be files called simconnect.msi in there, that have to be used to install the simconnect files into the sim and Windows. I never had any trouble with the NGX and Voxatc in FSX using Windows 7 but I can't speak for XP. The problem with click spots etc in P3D is due to not starting with the NGX,or 777, or missing simconnect files.

If you have trouble with missing clickable buttons etc with PMDG aircraft, they suggest you check all the simconnect.msi files have been installed,(in FSX I think they are in the SDK, which is on one of the install discs), and also start with only the PMDG aircraft loaded into memory, in other words don't start with one aircraft and then choose a PMDG one. The PMDG support area on their website, and read-me files that come with the aircraft, have hints and tips about these sort of issues. In the far off past when I used FSX, I remember PMDG said you should start with a default aircraft, but now it seems best to start with the PMDG aircraft you intend to fly, rather than change it after loading the sim. This is certainly the case with P3D, but perhaps not with FSX. I may well be wrong but I doubt it is something to do with Voxatc that is causing the problem.

Please disregard my post about MCE and the latest "44" hotfix for P3d 2.5 not working. I reinstalled MCE 2638 and it is working fine now. My error somehow, apologies.

Unfortunately the latest hotfix for P3d 2.5 has caused MCE, and some other things, to stop working again. So if you want to keep using MCE in the meantime, I would not install today's, 3rd March, hotfix from P3d, yet.

I am afraid the Dll.xml file modification did prevent P3D from starting. I put back the original backed up version and the sim started fine. Have to wait for the update!

I have used Fs2Crew for a number of years with various aircraft, and think I have the hang of it but I am stumped at the moment. I downloaded the new PMDG 777 installer, and installed it into FSXSE without issue. I also installed the 1.2 version of Fs2Crew 777. I read through the manual and everything seems to be set up and installed properly, but when I start FSXSE, the 777 and then Fs2Crew I can work my way through the procedure OK, the green bar indicates what I am saying correctly and FA responds to my "yes" about starting the boarding.....but when I call for any checklist there is absolutely no response. The Fs2crew mode window is indicating which check list I should be asking for and I have tried cycling the mode back and forward without success. It will be something very basic no doubt that I have not done correctly, but I have never had this difficulty in other versions of Fs2crew. Getting older doesn't help, I suppose, but if there are any ideas out there as to what I may be doing wrong it would be a great help!

Yes Steve I had FSX installed, but just for the 777. I always use P3D except for when using the 777. I removed FSX before installing steam.