Jump to content
Sign in to follow this  
Followers 0
gorkemsinirlioglu

Not able to connect VAInterface.dll

By gorkemsinirlioglu, in Virtual Avionics Support Forum

Recommended Posts

gorkemsinirlioglu    1

gorkemsinirlioglu
Posted

Hello Forum!

 

I bought the product Virtual CDU 737 today. Unfortunately the VAInterface software on my computer does not connects to Prepar3d. Anyone can help? I'm sending screenshots

 

Jq8nB5.jpg

 

l3Pv8g.jpg


Here is my log:

 

10/01/17 17:53:37 (       0) - VAInterface -  Version 2.22.0.11621 
 
10/01/17 17:53:37 (       0) - Config - Processor architecture = x64 
 
10/01/17 17:53:37 (       0) - Config - OS Version = 6.2.9200 SP=0.0 
 
10/01/17 17:53:37 (       0) - Config - FS9 path = [NOT FOUND] 
 
10/01/17 17:53:37 (       0) - Config - FSX path = [NOT FOUND] 
 
10/01/17 17:53:37 (       0) - Config - P3D path = [NOT FOUND] 
 
10/01/17 17:53:37 (       0) - Config - P3DV2 path = [NOT FOUND] 
 
10/01/17 17:53:37 (       0) - Config - P3DV3 path = C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\ [OK] 
 
10/01/17 17:53:37 (       0) - Config - STEAM1 path = [NOT FOUND] 
 
10/01/17 17:53:37 (       0) - Config - STEAM2 path = [NOT FOUND] 
 
10/01/17 17:53:37 (       0) - Config - X-PLANE path = [NOT FOUND] 
 
10/01/17 17:53:37 (       0) - Config - VAInterface.dll on P3DV3   : 1.0.3.11033 [uP TO DATE] 
 
10/01/17 17:53:37 (       0) - Config - SDK data broadcast on C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\PMDG\PMDG 737 NGX\737NGX_Options.ini : ENABLED 
 
10/01/17 17:53:37 (       0) - Config - SDK data broadcast on C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\PMDG\PMDG 777X\777X_Options.ini : ENABLED 
 
10/01/17 17:53:37 (       0) - vainterface - getIPAdress => WSAStartup 
 
10/01/17 17:53:37 (       0) - vainterface - getIPAdress => gethostname 
 
10/01/17 17:53:37 (       0) - vainterface - getIPAdress => hostname = DESKTOP-V2O2NVR 
 
10/01/17 17:53:37 (      16) - vainterface - getIPAdress => address 0 = 192.168.2.107 
 
10/01/17 17:53:37 (      16) - VAInterface - Available IP(s) : 192.168.2.107  
 
10/01/17 17:53:37 (      16) - vainterface_core - Initializing objects ... 
 
10/01/17 17:53:37 (      16) - vainterface_core - Initializing VATokens ... 
 
10/01/17 17:53:37 (      16) - vainterface_core - Loading Aircraft profiles ... 
 
10/01/17 17:53:37 (      16) - vainterface_core - Updating devices ... 
 
10/01/17 17:53:37 (      16) - vainterface_core - No Device Found 
 
10/01/17 17:53:37 (      16) - SocketMgr - Created 
 
10/01/17 17:53:37 (      16) - SocketMgr - Running threadid=3512 
 
10/01/17 17:53:37 (      16) - SocketMgr - id=db8 Listenning on port 9000 
 
10/01/17 17:53:37 (      16) - BroadcastListener - Created 
 
10/01/17 17:53:37 (      16) - BroadcastListener - Running threadid=7624 
 
10/01/17 17:53:37 (      16) - BroadcastListener - Listenning on port 12080 
 
10/01/17 17:53:37 (      47) - WinFW - Firewall is off. 
 
10/01/17 17:53:37 (      47) - FSCommMgr - Unable to create comm 
 
10/01/17 17:53:47 (   10047) - FSCommMgr - Unable to create comm 
 
10/01/17 17:53:57 (   20047) - FSCommMgr - Unable to create comm 
 
10/01/17 17:54:07 (   30047) - FSCommMgr - Unable to create comm 
 
10/01/17 17:54:17 (   40047) - FSCommMgr - Unable to create comm 
 
10/01/17 17:54:27 (   50047) - FSCommMgr - Unable to create comm 
 
10/01/17 17:54:37 (   60047) - FSCommMgr - Unable to create comm 
 
10/01/17 17:54:47 (   70047) - FSCommMgr - Unable to create comm 
 
10/01/17 17:54:56 (   78281) - SocketMgr - Connectect to 192.168.2.100:46311 
 
10/01/17 17:54:56 (   78297) - IPComm - ThreaProc id=dac, socket=792 
 
10/01/17 17:54:56 (   78297) - IPComm - Connected to Virtual Avionics VCDU alias=vcdu serial=ce0616060a59990203 hwver=6.0.1 swver=1.10 type=0
 @ 192.168.2.100:46311 
 
10/01/17 17:54:56 (   78297) - DeviceMgr - Device Driver 0, Descriptor : Virtual Avionics VCDU  
 
10/01/17 17:54:56 (   78375) - vainterface_core - Device Virtual CDU 737 sw:110 hw:601 boot:00 serial:0 
 
10/01/17 17:54:57 (   80047) - FSCommMgr - Unable to create comm 
 
10/01/17 17:54:58 (   80281) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:00 (   82250) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:02 (   84266) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:04 (   86250) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:06 (   88281) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:07 (   90047) - FSCommMgr - Unable to create comm 
 
10/01/17 17:55:08 (   90266) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:10 (   92281) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:12 (   94297) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:14 (   96328) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:16 (   98297) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:17 (  100047) - FSCommMgr - Unable to create comm 
 
10/01/17 17:55:18 (  100281) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:20 (  102297) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:22 (  104297) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:24 (  106297) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:26 (  108313) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:27 (  110047) - FSCommMgr - Unable to create comm 
 
10/01/17 17:55:28 (  110313) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:30 (  112313) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:32 (  114313) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:34 (  116297) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:36 (  119125) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:37 (  120047) - FSCommMgr - Unable to create comm 
 
10/01/17 17:55:41 (  123625) - IPComm - Keep alive socket 792 
 
10/01/17 17:55:47 (  130047) - FSCommMgr - Detected Flight Simulator prepar3d.exe, hproc=390 
 
10/01/17 17:55:47 (  130047) - LoadSimConnect - Looking for simconnect.dll 
 
10/01/17 17:55:47 (  130047) - SimConnect - Loaded 'C:\WINDOWS\winsxs\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\simconnect.dll' 
 
10/01/17 17:55:47 (  130047) - FSXComm - Attached to SimConnect 
 
10/01/17 17:55:47 (  130047) - FSXComm - Waiting for Sim Start ... 
 
10/01/17 17:55:47 (  130047) - FSComm - VAIPC OK 
 
10/01/17 17:55:48 (  130266) - FSComm - Not able to ping VAIPC 
 
10/01/17 17:55:48 (  130375) - FSComm - Not able to get VAIPC version 
 
10/01/17 17:55:53 (  135375) - FSComm - VAIPC OK 
 
10/01/17 17:55:53 (  135594) - FSComm - Not able to ping VAIPC 
 
10/01/17 17:55:53 (  135703) - FSComm - Not able to get VAIPC version 
 
10/01/17 17:55:58 (  140703) - FSComm - VAIPC OK 
 
10/01/17 17:55:58 (  140922) - FSComm - Not able to ping VAIPC 
 
10/01/17 17:55:58 (  141031) - FSComm - Not able to get VAIPC version 
 
10/01/17 17:56:05 (  148000) - vainterface - Shutting Down!!! 
 
10/01/17 17:56:05 (  148000) - FSCommMgr - Unable to attach comm 
 
10/01/17 17:56:05 (  148094) - FSXComm - Detach SimConnect 
 
10/01/17 17:56:05 (  148094) - SimConnect - SimConnect.dll unloaded 
 
10/01/17 17:56:05 (  148094) - SocketMgr - Accept failed: 10004
 
 
10/01/17 17:56:05 (  148094) - BroadcastListener - recvfrom failed with error 10004 
 
10/01/17 17:56:05 (  148094) - BroadcastListener - Finished receiving. Closing socket. 
 
10/01/17 17:56:05 (  148094) - BroadcastListener - closesocket failed with error 10093 
 
10/01/17 17:56:05 (  148094) - IPComm - id=dac Disconnected res=-1, wsa=10053 
 
10/01/17 17:56:05 (  148094) - vainterface - getIPAdress => WSACleanup 
 
10/01/17 17:56:05 (  148094) - VAInterface - Closing 

Share this post

Link to post
Share on other sites

Dutra    8

Dutra
Posted

Hello,

 

I believe this is related to the DLL.XML not being correctly configured or being corrupted.

 

I just replied to the ticket you created suggesting this.

 

If the DLL.XML does not have the following data:

 

  <Launch.Addon>
    <Name>VAInterface</Name>
    <Disabled>False</Disabled>
    <Path>Modules\VAInterface.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>

 

, add it before the </SimBase.Document> - this should be the last thing in the file.

 

Best Regards,

 

Ricardo.

VA Support Team

Share this post

Link to post
Share on other sites

gorkemsinirlioglu    1

gorkemsinirlioglu
Posted

I have changed it now and have written it to the bottom before the </SimBase.Document> and nevertheless I'm getting the same failure.


In the control panel of VAInterface, there is "FS: NOT CONNECTED" but in devices I can connect my phone

Share this post

Link to post
Share on other sites

edpatino    1,960

edpatino
Posted

No one has an idea?

 

Have you disabled your firewall?.

Cheers, Ed

Cheers, Ed

MSFS Steam - Win10 Home x64 // Rig: Corsair Graphite 760T Full Tower - ASUS MBoard Maximus XII Hero Z490 - CPU Intel i9-10900K - 64GB RAM - MSI RTX2080 Super 8GB - [1xNVMe M.2 1TB + 1xNVMe M.2 2TB (Samsung)] + [1xSSD 1TB + 1xSSD 2TB (Crucial)] + [1xSSD 1TB (Samsung)] + 1 HDD Seagate 2TB + 1 HDD Seagate External 4TB - Monitor LG 29UC97C UWHD Curved - PSU Corsair RM1000x - VR Oculus Rift // MSFS Steam - Win 10 Home x64 - Gaming Laptop CUK ASUS Strix - CPU Intel i7-8750H - 32GB RAM - RTX2070 8GB - SSD 2TB + HDD 2TB // Thrustmaster FCS & MS XBOX Controllers

Share this post

Link to post
Share on other sites

SteveW    1,792

SteveW
Posted

Presuming there's no complications for the .dll with latest versions of P3D. Note that there are two dll.xml files with P3D v3 so please check them both and make sure there's only one with the VAInterface section added:

 

C:\ProgramData\Lockheed Martin\Prepar3D v3\

C:\Users\[you]\AppData\Roaming\Lockheed Martin\Prepar3D v3\

Steve Waite: Engineer at codelegend.com

Share this post

Link to post
Share on other sites

gorkemsinirlioglu    1

gorkemsinirlioglu
Posted

Presuming there's no complications for the .dll with latest versions of P3D. Note that there are two dll.xml files with P3D v3 so please check them both and make sure there's only one with the VAInterface section added:

 

C:\ProgramData\Lockheed Martin\Prepar3D v3\

C:\Users\[you]\AppData\Roaming\Lockheed Martin\Prepar3D v3\

The both are with the VAInterface section added. Is it false?

Share this post

Link to post
Share on other sites

SteveW    1,792

SteveW
Posted

Only one should have it.

Steve Waite: Engineer at codelegend.com

Share this post

Link to post
Share on other sites

SteveW    1,792

SteveW
Posted

Makes no difference as long as you only have one, leave one in AppData.

 

Looks like you've set everything correctly, all you can do, the Simconnect works, firewall is off, seems the dll doesn't communicate - contact support give them your P3D version.

Steve Waite: Engineer at codelegend.com

Share this post

Link to post
Share on other sites

fernandinho    2

fernandinho
Posted

Don't ask me why :fool:  but today I updated my VAInterface from 1.5 (working fine) to Version 2.22.0.11621

And now I have the same issues you're talking about: Not able to connect to VAInterface.dll.  

 

Any solutions?!

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  
Followers 0
Go To Topic Listing

  • 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...