Jump to content

Sign in to follow this  
pipsara

Voxatc with Prepar3D v2

Recommended Posts

Any body managed to get it working with P3D v2? 

I can't find a way to install it. 

Sent a request to the support site. 

Mike 

Share this post


Link to post
Share on other sites

It works ok for me.  Or I should say, it works as far as that I've only just installed it, it loads in fsx and recognises my voice.  I haven't done any full flights yet or checked SIDs, etc.

 

I must add that I used the Estonia migration tool for installation.

 

http://www.flightsim.ee/products/migration-tool#download

 

I can post more details on my installation if required, but from first impressions it appears to work fine and even appears faster than it did under FSX.

Share this post


Link to post
Share on other sites

And I've just noticed that by mistake it was version 6.05 that I had installed.  I will try upgrading to 6.20 and see if it still works, but 6.05 definitely does.

Share this post


Link to post
Share on other sites

Installing 6.20 and it didn't work.  For some reason the gauge files were not in the P3D\gauges directory.  Copying the files VAGauge.gau and VAInfo.gau from the voxatc\p3d\gauges folder to the P3D\gauges folder sorted it for me.  I suspect that is what is suggested in the thread referred to above.

 

...as it does, just seen it.

Share this post


Link to post
Share on other sites

Hmmm.  Not so good, it doesn't appear to be picking up my flight plan (only offers local flight and circuits).

 

"and even appears faster than it did under FSX".  And scratch that - frame rates are taking a pummeling.

Share this post


Link to post
Share on other sites

Please can anyone confirm whether they've got it working so that it picks up their flight plans correctly?

Share this post


Link to post
Share on other sites

I managed to get it working as far as having the program respond, moving the gauge files fixed that. It doesn't recognise the flight plans however. 

So its a no go at this stage for me as well. 

Mike 

Share this post


Link to post
Share on other sites

Just a guess, but has the flight file format changed from p3d v1.x to v2?  I think VoxATC uses the flight file to get some of its info - in which case I wouldn't be surprised if it doesn't work.

Share this post


Link to post
Share on other sites

OK - starting to get somewhere.  If I copy flt (and associated) files from my old fsx installation (or should I say its backup, as I've uninstalled - bit hasty methinks?) into the p3d folder, those CAN be loaded into p3dv2, and VoxATC appears to work as expected.  Much more testing needed though.  I'll report back after I try some full flights, but looks promising.

 

This is as opposed to using newly created p3dv2 fxml files, which was what I was doing, and which wasn't working for me.

 

It also appears to be necessary to keep the old flt files (i.e. copies) in their original locations, as the original path is referenced within the files.

Share this post


Link to post
Share on other sites
"It also appears to be necessary to keep the old flt files (i.e. copies) in their original locations, as the original path is referenced within the files."

 

Only reference I could find was in the flt file and changing it to the new location cleared the issue:

 

[GPS_Engine]

Filename=C:\Users\USER_NAME\Documents\Prepar3D v2 Files\FLIGHT_PLAN

Share this post


Link to post
Share on other sites

Flew an entire flight, using my fsx flight files, and it seems to work just like it did with fsx,

 

There's more of a frame rate hit than I was expecting / hoping.

Share this post


Link to post
Share on other sites

"but I get a fatal VoxAtc error"

 

When I've seen this I think it was because there was something about the flight I was using that VA didn't like.  Like loading one of the VA demo flights where the aircraft does not exist in P3Dv2.

Share this post


Link to post
Share on other sites

As far as I can tell loading a .fxml flight doesn't work, loading an .flt one does.

 

Luckily P3Dv2 seems to save both an .flt and an .fxml file if an flt.file (of the same name) already exists.   If the fxml file is then deleted, the flt file can be loaded.

 

Sorry if I'm just stating the bleeding obvious, I'm completely new to P3D (any version).

Share this post


Link to post
Share on other sites

"but I get a fatal VoxAtc error"

 

When I've seen this I think it was because there was something about the flight I was using that VA didn't like.  Like loading one of the VA demo flights where the aircraft does not exist in P3Dv2.

 

Also, not having the virtual fsx installation (Estonia) enabled also caused this for me. 

Share this post


Link to post
Share on other sites

I have the virtual fsx installation enabled.  I have the navdata installed.  I can't figure out why it doesn't work for me.  Maybe I should reinstall.  Anyhow, I'm thinking of putting P3D V2 aside for a while as with FTX Global installed I have little white boxes all over the landscape that I really don't care to see every time I start the simulator. 

Share this post


Link to post
Share on other sites

I installed PROATC X with the Estonian migration tool and it has worked fine. The only problem I have found is that I get no reaction for it when I fly the Carenado B1900D, I.e, when I change the comms radion, PRO ATC X does not see this

Share this post


Link to post
Share on other sites

It works ok for me....  I haven't done any full flights yet or checked SIDs, etc.

 

I must add that I used the Estonia migration tool for installation.

 

[... appears faster than it did under FSX.

But, does it require running p3D in legacy mode?

Share this post


Link to post
Share on other sites

But, does it require running p3D in legacy mode?

 

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.  

Share this post


Link to post
Share on other sites

I get the "fatal error" but only at a few different locations/airports..  biggest issue is not having the voxatc panel on some aircraft.. i dont think the installer knows to patch panel.cfg.. in fact. some aircraft dont have a panels or panel.cfg.. anyone noticed this?  If i run the panel config tool though, it acts as if there are no aircraft to modify, even though some clearly dont have or cant be modified.. maybe i'm misunderstanding panels with p3d v2..

 

One example of an aircraft that does have the panel.cfg but no mod was made during install is the IRIS Raptor Driver.  There are very few that i have found that dont have a panel folder/cfg though.. 

 

So i guess one would need to hand modify any aircraft missing the vox atc lines like:

 

[Window Titles]

Window100=VoxATC
Window101=VoxATC Recent Comms
 
////<VoxATC
[Window100]
visible=1
size_mm=400,200
pixel_size = 400, 200
position=4
background_color=0,0,0
ident=14077
zorder=5
alpha_blend=0.65
gauge00=VAGauge!VoxATCPrompt,0,0
////>VoxATC
 
 
////<VoxATC
[Window101]
visible=0
size_mm=400,600
pixel_size = 400, 600
position=5
background_color=255,255,255
ident=14078
zorder=5
gauge00=VAInfo!VoxATCInfo,0,0,400,600
////>VoxATC

Share this post


Link to post
Share on other sites

But, does it require running p3D in legacy mode?

Since then, the following...it now has native support for Prepar3D v2...

 

 

My current problems - after one year of waiting to see the upgrades and an install of version 6.49:

 

This could be such a cool ad on if everything worked right!

 

1.the VOXATC screens disappear after first connection to Clearance. I have to go to View, instruments and re-choose the toolbox ATC windows.

N.B. I didn't see it anywhere in the documentation, but there is a set up program inside of the root directory for VoxATC that allows you to set up a push to talk button on your joystick ....make sure you get rid of any reference that you may have made through FSUIPC for the space bar keyboard press through a joystick button.

 

 

2. After clicking from one VoxATC window to another, a curious + shows up instead of the cursor which destroys my ability to use any kind of mouse click...loading a plane or any plane does not clear The + cursor.

A. The only way to get rid of the + cursor is to restart P3-D.

 

3. Changing the font for the two VOXATC windows changes the size but not the spacing and therefore it is triple spacing inside of the two box ATC windows... as if it were expecting a larger font.

 

4.Once voice recognition is loaded, and minimized, I noticed some weird interaction happening between my screens. Just my voice seems to act as if the Windows SAPI5 voice recognizer is supposed to be working in Windows 7-64 bit...and throw to the screen either different windows that I did not ask for within P3-D or actual Windows applications that I certainly did not ask for via voice....bug? Or more training?

 

I would really love to get this working, after my great IFR experience with Pilotedge, but the + cursor substitution bug is a dealbreaker.

 

Any ideas?

 

Happy new year to all!

 

 

Chas

 

See the complete VOXATC update info since my last post on the subject.

 

http://voxatc.com/Home.aspx/News

 

End of VOXATC update Feb 2014

 

C

Share this post


Link to post
Share on other sites

1. Did you change view when the vox window disapeared? You can avoid this by right clicking on the window title bar and undock the window so it stay on top.

 

2. The + is the the yoke mouse mode indicator. Just click right on your screen and you can untick this option. It happens sometimes to me also and I have to untick it twice in row to restore normal operation.

 

3 and 4 no idea...

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...