Jump to content
Sign in to follow this  
reevesy

P3DV5 VA interface

Recommended Posts

Good Morning All

 

Can you confirm the current VA interface will work with P3DV5 or will an update be required.

 

Many Thanks

 

David Reeves

Share this post


Link to post
Share on other sites

Need an Update, but once again, no response from VA Support...

Share this post


Link to post
Share on other sites

Hi all,
Although it's extremely sad and poor how VA is absolutely not replying on tickets, emails, topics etc. Maybe I can hint you guys somewhere into the right direction. I was trying out aviaCDU (well, actually didn't start it up yet, just installed it). I noticed that it made a few different changes in the 747QOTSII_Options.ini (C:\Prepar3D v5\PMDG\PMDG 747 QOTS II) as per below:

[SDK]
EnableDataBroadcast=1
EnableCDUBroadcast.0=1
EnableCDUBroadcast.1=1
EnableCDUBroadcast.2=1
EnableEFBBroadcast.0=1
EnableEFBBroadcast.1=1

It appears that the app is now functioning again. I tested this on the 2.27 build with the latest PMDG update on P3Dv5, so far no complaints.

Hope this helps.
Regards,
Yassin KULK

Share this post


Link to post
Share on other sites
3 minutes ago, r0xbeat said:

What should we do guys? I didn't understand 🤷‍♂️

Hi @r0xbeat,

Step 1: Go to your main Prepar3D v5 Folder --> PMDG --> PMDG 747 QOTS II (my structure looks like this: C:\Prepar3D v5\PMDG\PMDG 747 QOTS II)

Step 2: Right-click 747QOTSII_Options.ini and click on EDIT

Step 3: Scroll all the way to the bottom of the ini file, and paste the below block right under it:

[SDK]
EnableDataBroadcast=1
EnableCDUBroadcast.0=1
EnableCDUBroadcast.1=1
EnableCDUBroadcast.2=1
EnableEFBBroadcast.0=1
EnableEFBBroadcast.1=1

The last block in my .ini was [Panel State]. So, by adding the above code at the bottom of the file, it should look something like this:

[Aircraft Config]
FixedConfig=
[Panel State]
StartupPanelState=
[SDK]
EnableDataBroadcast=1
EnableCDUBroadcast.0=1
EnableCDUBroadcast.1=1
EnableCDUBroadcast.2=1
EnableEFBBroadcast.0=1
EnableEFBBroadcast.1=1

That should be it. Try to fire up Prepar3D v5 and VAInterface, and hopefully it all works. Ensure that in Prepar3D V5, if it doesn't automatically recognize the aircraft (which I think it should anyways), to select PMDG747 as the aircraft.

Good luck!
Regards,

  • Like 1

Share this post


Link to post
Share on other sites
21 minutes ago, r0xbeat said:

Thanks YKULK, well explained 👍

Hi @r0xbeat,

More than welcome. Maybe interesting to let everyone know if it works for you too. You'll help the others as well! :D

Cheers!

Share this post


Link to post
Share on other sites

Hm, didn't work for me, with P3dV5 VA2.28.1 and the latest 747 update.

Share this post


Link to post
Share on other sites
15 minutes ago, r0xbeat said:

Hm, didn't work for me, with P3dV5 VA2.28.1 and the latest 747 update.

Hi @r0xbeat,

Hmmmm. To double-confirm, you are on the Prepar3D v5 latest hotfix? And the PMDG is updated to 3.01.0303 or above? They released a new minor update over the weekend that also sorted out the SDK that was broken in the patch before.

Last thing you could try, is that I tested it with VA2.27 instead of 2.28.1.

Fingers crossed, the best of luck!

Share this post


Link to post
Share on other sites

I'm having a rather frustrating issue.  About 1/2 the time the Interface fails to launch.  Another 1/4 the time it launches but it doesn't connect to the sim.  The last quarter it connects to FSX SE (I'm running P3Dv5).  Sometimes I'm able to get my table to connect other times not.  Even if it doesn connect it doesn't do anything except say its connected as the Profile is set to Default.  Regardless.  After 1 min the Status of the Intervace changes to Inactive and FS goes to Not Connected. 

 

Any input?

Tons of Event Errors

Faulting application name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x4b90
Faulting application start time: 0x01d62e275d3ebeaa
Faulting application path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe
Faulting module path: unknown
Report Id: bfa586a0-018c-42e0-89ca-1cd9f2f06ed6
Faulting package full name: 
Faulting package-relative application ID: 

 

Faulting application name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x3908
Faulting application start time: 0x01d62e27a7347314
Faulting application path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe
Faulting module path: unknown
Report Id: 2506ae88-bc0c-40dd-a6b5-19f892df14c1
Faulting package full name: 
Faulting package-relative application ID: 

 

Faulting application name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x2fe0
Faulting application start time: 0x01d62e27bb79d4cf
Faulting application path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe
Faulting module path: unknown
Report Id: b381d36d-3c87-440b-bb28-3d2c7e32de68
Faulting package full name: 
Faulting package-relative application ID: 

 

Faulting application name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x4e60
Faulting application start time: 0x01d62e27d879c694
Faulting application path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe
Faulting module path: unknown
Report Id: bec3d7a5-9b9d-4765-b4da-e38cd7ea75a9
Faulting package full name: 
Faulting package-relative application ID: 

Faulting application name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x1f58
Faulting application start time: 0x01d62e27f0d1610a
Faulting application path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe
Faulting module path: unknown
Report Id: 2829e98e-e7f5-4034-aff6-905e88bce905
Faulting package full name: 
Faulting package-relative application ID: 

 

Faulting application name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45
Faulting module name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45
Exception code: 0xc0000005
Fault offset: 0x000286db
Faulting process id: 0x4de0
Faulting application start time: 0x01d62e28142cb9d1
Faulting application path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe
Faulting module path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe
Report Id: 475daec3-e6e4-4104-8631-e28ceedd7535
Faulting package full name: 
Faulting package-relative application ID: 

 

Faulting application name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45
Faulting module name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45
Exception code: 0xc0000005
Fault offset: 0x000286db
Faulting process id: 0x12a8
Faulting application start time: 0x01d62e283e0baf72
Faulting application path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe
Faulting module path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe
Report Id: a4273a06-e7e9-4b56-bcc9-67aff5995c6d
Faulting package full name: 
Faulting package-relative application ID: 

 

Faulting application name: VAInterface.exe, version: 2.27.0.66, time stamp: 0x5b8972fa
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x3cac
Faulting application start time: 0x01d62e291aceabdc
Faulting application path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe
Faulting module path: unknown
Report Id: 02a972c5-a72e-46f4-b6a0-f07edee4a17c
Faulting package full name: 
Faulting package-relative application ID: 

 

I got about 6 more than this.  Each one has different Data.

Further Edit: I checked with P3Dv4 on the 777 still works as advertised only issue I see right now is P3Dv5.

Edited by thibodba57

Brian Thibodeaux | B747-400/8, C-130 Flight Engineer, CFI, Type Rated: BE190, DC-9 (MD-80), B747-400

beta.gif   

My Liveries

Share this post


Link to post
Share on other sites

Goodday @r0xbeat and @thibodba57,

I'm sorry that you're still struggling with this. Unfortunately, as goes for everyone, we need VAInterface's official support on a new build to natively support P3DV5. All I can say is that I find it strange that it works on my side with the above mentioned steps, so maybe not all options have been exhausted yet on your side to match my set-up (I don't believe in luck when it comes to software :D). Do note as well that on my PC, the VAInterface.exe also shows FSX:SE (Steam Edition) when connected to P3Dv5, but it doesn't limit anything on my end.

Just to resume the steps:

  1. Are you sure that you are utilizing 2.27? And not 2.28.1? My testing was with 2.27 build of the software, I can't confirm if 2.28.1 works.
  2. Are you sure that you have installed all the SimConnect redist libraries? (Prepar3D Main Folder --> redist)
  3. Are you sure that you have edited the PMDG747 Options.ini file (as per above explanation) properly to include the [SDK] block at the bottom of the file?

If the above is done properly and it still doesn't work, I'm afraid I can't be of any help :(. You might want to check-out Remote CDU/AviaServer (https://www.avsim.com/forums/forum/742-remote-cdu-for-phone-tablet-official-support-forum/) who have native P3Dv5 support since a few days.

  • Like 1

Share this post


Link to post
Share on other sites

Thx YKULK,

will try it again, step by step.

I use the MCP373, so I have no alternatives like for CDU.

Their support just sucks, I mean this is a 600$ item, and u have to wait weeks or even longer for updates, to get it work with new P3D versions.

Edited by r0xbeat

Share this post


Link to post
Share on other sites
4 hours ago, r0xbeat said:

Thx YKULK,

will try it again, step by step.

I use the MCP373, so I have no alternatives like for CDU.

Their support just sucks, I mean this is a 600$ item, and u have to wait weeks or even longer for updates, to get it work with new P3D versions.

Hi @r0xbeat,

Totally agree with you. Sorry that I didn't pay attention to the fact that you were using the MCP373. Anyhow, I see @bcrawley57 managed to get it to work, as he mentioned for the CDU, MCP and EFIS controls, so hopefully it should work for you as well.


I just checked the SDK PMDG manual again, and see no other parameters needed in the .ini to enable the broadcasting. Be sure to launch the PMDG Operations Center 2.0 and to check if you have any aircraft updates as well. When PMDG 747 was launched for P3Dv5, they accidentally broke the SDK. It's only with the last version (3.01.0303 for both 747-400 and 747-8 QOTSII versions) that the SDK was repaired again. You can refer to this forum post for more details about that: https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/pmdg-747-queen-of-the-skies-ii-forum/61108-sdk-changes

I'm really out of ideas otherwise 😞

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...