Yes!

 

Very good news!

 

 

Can we have the change log please?  :rolleyes:

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.

Hello !

Thank's for this idee.

When you say "edit" the copied file to convert it to a .flt format, you mean we can use FSX ? 

When you say "edit" the copied file to convert it to a .flt format, you mean we can use FSX ?

 

No.  I mean using the find / replace functionality found in most text editors.

 

(But using flt's from FSX should work.)

ok

Yes!

 

Very good news!

 

 

Can we have the change log please?  :rolleyes:

 

+1 for the change log! I'd love to see what's in the pipe!

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.

Just made the transition to P3D V2.1 today. Very sad that I can't have a working version of VOX as it is an integral part of all my flying.

 

I followed this thread and tried to do the above fixes. I have the same issue...No copilot option and it assumes I am doing a local VFR flight everytime.

 

When you reinstalled did you do so with the migrator tool?

 

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?

 

Thank you so much for any help you can provide.

 

- Adam

"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?

Thank you for the help!

 

I do have the Estonia Migration Tool

 

And I do have a working version of FSX....However I did delete my VOX off my FSX installation...but it seems like that doesn't matter.

 

- Adam

When using P3D, make sure that the EMT has virtual FSX turned ON.  If using FSX it must be OFF.

 

The following are all things to try (and you might want to check the other P3Dv2 and VoxATC post for further info):

 

OK.  If you create an IFR flight in fsx with a flight plan and copy the files (*.flt, *.pln, *.wx) over to the p3d folder, does it work then (i.e. you are asked to get the ATIS, then your clearance, etc)?

 

When you run the indexer, does it scan inside of your P3D directory, and does it complete?  There is a SimulatorSelection.exe (or something like that, going from memory) in the VoxATC folder that you can use to switch simulator.

 

In P3D, make the flight the default flight, and in general settings turn off the setting that enables starting P3D in the Scenario Builder, i.e. make it so that as soon as P3D starts, it loads the flight you want to test automatically.

 

As far as I can tell VoxATC only refers to the flt file, so that is the one that matters the most to us.  Of course the pln and wx are needed by the sim.

 

The following files need to be in your P3D gauges directory vagauge.gau, vainfo.gau.  Though I assume you've got those as the gauges appear to be loading for you.

 

For the installer to work, I needed to have Simconnect installed.  The installer (msi) is in the P3D directory \Lockheed Martin\Prepar3D v2\redist\Interface\FSX-SP2-XPACK\retail\lib.

 

Reinstall VoxATC, removing all old files.  By this I just mean the 6.20 installer, not the voices (I have never had a need to reinstall these, and they've been on my system for years now).  Uninstall first, then delete (but backup first, just in case) the contents of %appdata%\Internal Workings\VoxATC X.  Also delete any remaining files in the VoxATC main program folder.  Note that you will lose all your settings, and have to reconfigure again.  When installing make sure that virtual FSX is turned on in EMT, BUT select P3D whenever the installer asks if you have FSX or P3D.

 

Are you using navdata for SIDs / STARs?

 

It can be a fit flaky to get working, but once it does, for me it appears to work just like it does in FSX.  Let's just hope the update comes soon.

 

If you're in a situation where you have both an fxml and an flt for a flight, move the fxml out of the P3D flights folder.

 

"However I did delete my VOX off my FSX installation...but it seems like that doesn't matter." - For what we're trying to do it shouldn't matter.  If you still want use VoxATC in FSX as well, you just need to have the gauge files in the FSX gauges folder.  I believe you need to run the indexer and repoint it each time you want to switch between sims.

 

And, sorry if I'm stating the obvious / making too many assumptions, I have no idea of your level of experience with fsx/p3d.

IT WORKS!

 

Thank you so much for the help!

 

I uninstalled and reinstalled making sure the simconnect from P3D was installed.

 

Went ahead and created and saved the flight I wanted in my already installed FSX...then ported the files to the P3DV2 folder. I loaded it as the default flight, restarted P3D and it works perfect! I even have the First Officer option working.

 

Can't wait to start flying regularly with it in P3D while we wait for the official patch.

 

Thanks again,

Adam

Also I was able to get a fully functioning flight even without setting the loaded flight to the default flight in P3D. I would be interested in the .exe file you have to convert the fxml files so I don't even have to run FSX.

 

I will PM you.

 

Thanks,

Adam

I've sent (I hope, I'm not entirely sure the upload worked) the file up to the avsim file library.  I don't know how long it takes until it becomes available.  It's called FxmlToFlt and categorised under Prepare3d utilities. 

 

UploadID:         319336

Awesome...

 

Just another quick note for anybody else going through the issue.

 

You must disable virtual FSX in the P3D Migration tool in order for VOX ATC to get access to the .FLT files. If you have Virtual FSX enables Vox will crash due to fatal error in FSX.

 

- Adam