Hippo

"working version of VOX as it is an integral part of all my flying.". I completely agree. "When you reinstalled did you do so with the migrator tool?" - Yes I did. "And can you give a better description of what you are doing to the .fmxl files and the sequencing of what needs to be done when and where?" If you open up an fxml file you will find sections that look like this <Section Name="Kneeboard"> <Property Name="PageId" Value="2" /> <Property Name="Visible" Value="False" /> <Property Name="Location" Value="0, 0" /> </Section> The equivalent section in an flt file looks like this [Kneeboard] PageId=2 Visible=False Location=0, 0 It's just a case of (for instance) using find and replace in a text editor to strip out the xml tags. There are a few other details, for example lat/long punctuation is different. If you open up an flt and and fxml in a text editor you should see what I mean. I wrote a little exe that takes an fxml and spits out an flt, I can send it to you if you like (PM me). Another alternative is to create your flights in FSX and copy the files over to your P3D folder. Before I go into more detail, please can you answer the following: Are you using the Estonia Migration Tool? Do you still have a working FSX installation on the same system?

I'm pondering buying Vector 1.1, but not buying the Pilots Global FTX mesh. So I'd be using the default mesh. What issues (if any) can I expect to see? (I am using FTX Global Base).

I'm pondering buying Vector 1.1, but not buying the Pilots Global FTX mesh. So I'd be using the default mesh. What issues (if any) can I expect to see? (I am using FTX Global Base). Double post pls ignore

Are you using FSX? Assuming that you are, the usual process I follow is: 1. Set myself up so that I'm parked on the apron at my departure airport. 2. Create a flight plan and save it. 3. Save the flight. 4. Load the flight and start VoxATC. That usually works fine for me.

When uninstalling have you tried completely clearing out the %appdata%\Internal Workings\VoxATC X\ folder as well as the VoxATC program folder before attempting to install again? Worth a go, but bear in might you will lose your config settings.

Adding to my previous comments. I had to reinstall and I'm getting different behaviour now - I don't know what's going on with this. All things to try if you're trying to get this working while waiting for the update. "when exiting the flight, P3D v.2.1 appears to edit the flt and empty it out". This has now stopped happening to me - I haven't the slightest as to why. The method as described above now only works if the flight is loaded automatically when starting P3Dv2.1. If I try to load it manually or start with the scenario builder it doesn't work. However, as the flt file is no longer getting trashed, the fxml can be deleted, and this does work if I load using the flt. Go figure.

The utility to set the keystrokes does not appear to allow key combinations.

In the meantime, the following worked for me: Change the registry key (or create it if you don't have FSX installed): [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Flight Simulator\10.0] SetupPath=D:\FSX\ changing the path to whatever your P3Dv2 installation path is then run "simulatorselection.exe" from the VoxATC folder and select FSX. The indexer should run again and complete. If it's already set to FSX, then close it just run the indexer. Once indexing is complete, change the registry key back. (The Wow6432Node will only be there if you're running 64-bit).

"Why do you want to get rid of them?" Because I've assigned joystick buttons, and would like to free up the keys to use for other assignments. Is there any way to release them?

No. I mean using the find / replace functionality found in most text editors. (But using flt's from FSX should work.)

I do have the Saitek driver installed, and use FSUIPC, and always have to turn the wheel a few times for it to be recognised.

After playing around with this a bit more, the following works for me with 2.1 and VoxATC 6.22 and doesn't require FSX at all: 1. In P3D v.2.1 setup a flight and flight plan. 2. Save flight plan and flight. 3. Make a copy of the flight file (.fxml). 4. Rename the copied file to .flt. 5. Edit the copied file to "convert" it to .flt format. 6. Unfortunately, when exiting the flight, P3D v.2.1 appears to edit the flt and empty it out, so 3 - 5 have to be done again / file has to be set as read-only / backed up. I put together a little exe that takes care of 3, 4 and 5; PM me if you want me to e-mail it to you. Otherwise it's pretty simple e.g. to setup a macro in notepad++ to do all the required find/replaces, as the file formats appear to be very similar.

Not sure if you've tried the following, but I believe the flight has to be saved for things to work correctly. Once you have set up your flight plan and are sitting in the aircraft ready to go, save the *flight*, then start and enable VoxATC. To be on the safe side you might want to reload the flight as well. All I can think of.

For creating a flt files with p3d you create a file with notepad, for example and you overwrite it with p3d ? Because there's no way to create a flt file with p3d Correct... with v2.0. Unfortunately doesn't work in v2.1.

OK - works fine if I load an FLT, PLN, WX file combo created in FSX. However, if I attempt to save the flight (overwriting it), then it no longer works. Whereas in 2.0 I could save into an FLT file if one already existed, this doesn't seem to work in 2.1 (the existing flt file is deleted, and replaced with an fxml file).

Managed to get 6.20 to install and run in the sim by installing Simconnect as described in the following thread: http://forum.avsim.net/topic/434937-problems-simconnect-may-not-have-been-installed/ from the location \Lockheed Martin\Prepar3D v2\redist\Interface\FSX-SP2-XPACK\retail\lib Now to see if flight plans work...

With 2.0 I did have to use PLN files from FSX, but could use FLT files created from P3D as described above.

Just tried to install VoxATC into 2.1, and I'm having problems. 6.20 refused to installing saying that I didn't have FSX SP2, did I want to download it. 6.05 has installed but I get a fatal error as soon as I click Enable in the VoxATC window. I spent a lot of time getting VoxATC to work with 2.0, and at the moment I don't think I can be bothered to go through it all again to get it working with 2.1. I'll probably just wait for the next update. So you've got further than I have with 2.1. Good luck.

I entirely agree it has its risks (hence "you may want to investigate"), which are clearly explained in the documentation. It also creates a backup of all the files it changes, so it's quite easy to revert. I only found out about this utility on the LM forums recently (so only started using it recently with P3D v2.0). I have installed all European navaids, and the intersection data, and have not had any problems. I was practicing approaches, etc, in the south of Spain area and was having issues with navaids not matching current plates. After updating with this utility everything was correct. I am very happy with the results, although my usage has been very limited.

You may want to investigate the following: http://www.aero.sors.fr/navaids3.html

I believe that the following are necessary for this to work (and I haven't tried VoxATC in 2.1 yet, will let you know how I get on when I do): As well as the flight plan file (.PLN), you need an FSX-style flight file (.FLT). P3D by default creates and fxml files and I don't think VoxATC can handle these. However, it will also write to an FLT file if you save to overwrite an existing FLT file. I prefer to then delete the fxml file just to keep things tidy. Use the Estonia Migration Tool, with it set to virtual FSX. If you don't have this, I don't know exactly what it is doing that makes it work. But it didn't work for me if I did not have virtual fsx enabled. Be careful of the PLN. file being amended by P3D. With 2.0 I always kept a backup and overwrote the file if it was amended by P3D (check date stamp). This might have been fixed in 2.1 though. When creating a flight, and then importing the flight plan it is necessary to then save the flight. In P3D if you make sure that you save it as an FLT (I create a blank FLT file and overwrite it), this should work - but remember that the PLN file will be amended and you may want to overwrite with your backup. I'm not sure if the above are correct (so many variables), but it's what I found worked for me with 2.0. Hope it helps, sorry if it doesn't. Hopefully the developer will release an update soon.

Hi. As per the title, the plane works fine in v2.1, it's just that at night the VC is so dark that the instruments are unusable (this is with cabin light on). Also, while the cabin light does work but is nowhere near bright enough, the instrument lighting doesn't appear to work at all. Just hoping someone might know of a workaround. Thanks for any suggestions.

Are / Were you running Ezdok?

I don't know what the "legacy mode" you refer to is. Perhaps you mean running with virtual FSX enabled in Estonia - if so, then I believe the answer is yes. I think that not only is voxatc looking for the flt file, but that it expects to find it in the default "Flight Simulator X Files" folder (in My Documents). Anyway, IIRC, disabling virtual FSX caused it to fail for me.

Many thanks for taking the time to do this