Jump to content
The simFlight Network Forums

How do i connect a program (on a client pc written for fsx 32 bit) to MSFS on the host pc?


Jasper

Recommended Posts

How do i connect a program (on a client pc written for fsx 32 bit) to MSFS on the host pc?

I have a simkits built cockpit which i would like to use in MFSF.
The problem is that the software/drivers etc only work on a 32 bit system only (compatibility on the host 64 bit does not work!!)
Therefore i made a network running FSX on the client (32 bit windows 10 through widefs) and fsx on the host,and everything works all soft and harware.
But,I would like to use my hardware on MSFX,that was the whole idea:)

When I'm starting the software for simkits (simconnect) on the client, and then start MSFS on the host,the program on the client can not make a connection to MSFS.
All versions of simconnect are installed on both PC's.
I'm also using FSUIPC7 and widefs7...

Would be great to make everything work on MFSF,I hope I'm close but can not find the last steps....

Thanks in advance!!!!!!!

Link to comment
Share on other sites

17 minutes ago, Jasper said:

When I'm starting the software for simkits (simconnect) on the client, and then start MSFS on the host,the program on the client can not make a connection to MSFS.
All versions of simconnect are installed on both PC's.
I'm also using FSUIPC7 and widefs7...

So the simkits software is a simconnect client, and not an FSUIPC client?

If its a simconnect client, you can set-up a networked simconnect connection. To do this, you need to configure a network simconnect connection in yuor MSFS SimConnect.xml, and also provide a SimConnect.cfg file for your client, and the client must be configured to use this connection. I have provided instructions on how to do this for FSUIPC7 (i.e. to run FSUIPC7 on a client machine) here: 

 

If your client software is an FSUIPC client, then as you have a WideServer license, you can download WideFS6 and use the 32-bit WideClient.exe included with that, as the protocol between WideClient and WideServer is the same for 6 and 7.

John

Link to comment
Share on other sites

Thanks a lot!

The simkits requires simconnect+FSUIPC.

I have tried what you suggested (and have not copied across my FSUIPC7.ini. to the (new) folder on my client.as suggested).

However,when I open the the FSUIPC.exe on the client (windows 7, 32bit) to make a FSUIPC7.ini it tells me "the version of this file is not compatible with the version of windows you are running.Check to see whether you need a 32bit or 64bit version of the program  "...

Am I overlooking something?

 

Thanks again!

 

Edited by Jasper
Link to comment
Share on other sites

6 minutes ago, Jasper said:

However,when I open the the FSUIPC.exe on the client (windows 7, 32bit) to make a FSUIPC7.ini it tells me "the version of this file is not compatible with the version of windows you are running.Check to see whether you need a 32bit or 64bit version of the program  "...

Am I overlooking something?

Yes... FSUIPC7 is a 64-bit program, you cannot run that on a 32-bit OS. I posted a link to that post to show you how to run a simconnect client (such as FSUIPC) on an FS client PC. It shows how you configure your simconnect client for a networked connection. That post obviously shows you how to do this with FSUIPC7, but the procedure is the same for any simconnect client, i.e. your simkits.

9 minutes ago, Jasper said:

The simkits requires simconnect+FSUIPC.

If it requires FSUIPC, then you need to use the 32-bit WideClient, available in the WideFS6 download.

John

Link to comment
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
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.