Sign in to follow this  
adn

VAInterface and X-Plane 10 Issues

Recommended Posts

Folks, 

I have just received my MCP737-R + EFIS737 Pro and installed VAInterface (Win7 64bit Ult SP1). It looks all is fine with FSX but I have issues with X-Plane 10 (10.50). 

When loading VAInterface after opening X-Plane I am getting the following message:

 

Not able to connect to VAInterface.dll, please restart VAInternace. 

 

Reloading does not help. I am attaching one of my log files. It refers to X-Plane on drive F: but in reality it is on drive G:. I do not have any reference to X-Plane on drive F: in the registry.

Any hint how to overcome the issue?

Cheers,

Adam 

 

-------------START----------------------------------------------------------------------------

09/10/16 20:03:27 (       0) - VAInterface -  Version 2.20.3.11642 
09/10/16 20:03:27 (       0) - Config - Processor architecture = x64 
09/10/16 20:03:27 (       0) - Config - OS Version = 6.1.7601 SP=1.0 
09/10/16 20:03:27 (       0) - Config - Steam Co-Existence flag = 1 
09/10/16 20:03:27 (       0) - Config - FS9 path = [NOT FOUND] 
09/10/16 20:03:27 (       0) - Config - FSX path = E:\FSX\ [OK] 
09/10/16 20:03:27 (       0) - Config - P3D path = [NOT FOUND] 
09/10/16 20:03:27 (       0) - Config - P3DV2 path = [NOT FOUND] 
09/10/16 20:03:27 (       0) - Config - P3DV3 path = [NOT FOUND] 
09/10/16 20:03:27 (       0) - Config - STEAM1 path = [NOT FOUND] 
09/10/16 20:03:27 (       0) - Config - STEAM2 path = C:\SteamLibrary\steamapps\steamapps\common\FSX\ [OK] 
09/10/16 20:03:27 (       0) - Config - X-PLANE path = F:\X-Plane 10\ [ERROR] 
09/10/16 20:03:27 (       0) - Config - VAInterface.dll on FSX     : 3.1.0.11027 [uP TO DATE] 
09/10/16 20:03:27 (       0) - Config - VAInterface.dll on STEAM2  : 3.1.0.11027 [uP TO DATE] 
09/10/16 20:03:27 (       0) - Config - SDK data broadcast on E:\FSX\PMDG\PMDG 737 NGX\737NGX_Options.ini : ENABLED 
09/10/16 20:03:27 (      16) - Config - SDK data broadcast on E:\FSX\PMDG\PMDG 777X\777X_Options.ini : ENABLED 
09/10/16 20:03:27 (      16) - Config - SDK data broadcast on C:\SteamLibrary\steamapps\steamapps\common\FSX\PMDG\PMDG 737 NGX\737NGX_Options.ini : ENABLED 
09/10/16 20:03:27 (      16) - Config - SDK data broadcast on C:\SteamLibrary\steamapps\steamapps\common\FSX\PMDG\PMDG 777X\777X_Options.ini : ENABLED 
09/10/16 20:03:27 (      16) - vainterface - getIPAdress => WSAStartup 
09/10/16 20:03:27 (      16) - vainterface - getIPAdress => gethostname 
09/10/16 20:03:27 (      16) - vainterface - getIPAdress => hostname = COSMOSII 
09/10/16 20:03:27 (      16) - vainterface - getIPAdress => address 0 = 10.0.0.16 
09/10/16 20:03:27 (      16) - VAInterface - Available IP(s) : 10.0.0.16  
09/10/16 20:03:27 (      16) - vainterface_core - Initializing objects ... 
09/10/16 20:03:27 (      16) - vainterface_core - Initializing VATokens ... 
09/10/16 20:03:27 (      16) - vainterface_core - Loading Aircraft profiles ... 
09/10/16 20:03:27 (      16) - vainterface_core - Updating devices ... 
09/10/16 20:03:27 (      31) - DeviceMgr - Device Driver 3, Descriptor : Virtual Avionics MCP737R  
09/10/16 20:03:27 (     390) - vainterface_core - Device MCP 737R sw:15 hw:02 boot:03 
09/10/16 20:03:27 (     421) - DeviceMgr - Device Driver 3, Descriptor : Virtual Avionics EFIS737  
09/10/16 20:03:27 (     671) - vainterface_core - Device EFIS Control 737 sw:0a hw:03 boot:03 
09/10/16 20:03:27 (     702) - SocketMgr - Created 
09/10/16 20:03:27 (     702) - SocketMgr - Running threadid=8668 
09/10/16 20:03:27 (     718) - SocketMgr - id=21dc Listenning on port 9000 
09/10/16 20:03:27 (     718) - BroadcastListener - Created 
09/10/16 20:03:27 (     718) - BroadcastListener - Running threadid=8092 
09/10/16 20:03:27 (     718) - BroadcastListener - Listenning on port 12080 
09/10/16 20:03:28 (     749) - WinFW - Firewall is on. 
09/10/16 20:03:28 (     780) - WinFW - Application listed and enabled in the firewall. 
09/10/16 20:03:28 (     780) - FSCommMgr - Unable to create comm 
09/10/16 20:03:39 (   12433) - FSCommMgr - Unable to create comm 
09/10/16 20:03:49 (   22433) - FSCommMgr - Unable to create comm 
09/10/16 20:03:59 (   32433) - FSCommMgr - Unable to create comm 
09/10/16 20:04:09 (   42448) - FSCommMgr - Unable to create comm 
09/10/16 20:04:19 (   52448) - FSCommMgr - Unable to create comm 
09/10/16 20:04:29 (   62463) - FSCommMgr - Unable to create comm 
09/10/16 20:04:32 (   65427) - vainterface - Shutting Down!!! 
09/10/16 20:04:32 (   65552) - BroadcastListener - recvfrom failed with error 10004 
09/10/16 20:04:32 (   65552) - BroadcastListener - Finished receiving. Closing socket. 
09/10/16 20:04:32 (   65552) - BroadcastListener - closesocket failed with error 10093 
09/10/16 20:04:32 (   65552) - SocketMgr - Accept failed: 10004
09/10/16 20:04:32 (   65552) - vainterface - getIPAdress => WSACleanup 
09/10/16 20:04:32 (   65552) - VAInterface - Closing 
----------END----------------------------------------------------------------------------------------------------

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Hello Adam,

 

The issue here is that VAInterface is not finding the X-Plane installation path.

It retrieves that information from the file  x-plane_install_10.txt

 

Please review the contents of that file and make sure it reflects the actual installation path for X-Plane in any of its lines (you may have more than one copy of X-Plane, but each one must be represented by its own line describing the installation path).

 

Best Regards,

 

Ricardo.

 

VA Support Team

 

 

Share this post


Link to post
Share on other sites

Ricardo, Many thanks. The file contained a reference to F: drive. I have changed to the actual location and it works. Br, Adam

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