CPFlight and P3D

[JoeFackel 760]

I don't have the NGXu, only the former NGX.

There you have to set the enablebroadcast to get hardware working.

[JoeFackel 760]

32 minutes ago, GSalden said:

That I do not agree with. The few times I needed support I sent an email and got a reply within 1 day...

Yeah, i also got one reply. One, further questions haven't been answered, regardless of the thousands of EUR i have spent on CPFlight hardware.

[SteveW 1,792]

I don't know which SimConnect is involved but you could check in c:\windows\winsxs and search for "SimConnect". If one is missing could be that one needed.

microsoft.esp.simconnect: 1.0.20.0, SimConnect.dll: 1.0.195.0 = p3d version
microsoft.flightsimulator.simconnect: 10.0.62615.0, SimConnect.dll: 6.2.62615.0
microsoft.flightsimulator.simconnect: 10.0.61242.0, SimConnect.dll: 6.2.61355.0
microsoft.flightsimulator.simconnect: 10.0.61259.0, SimConnect.dll: 6.2.61637.0

Older PCs running P3D worked without fiddling with SimConnect if they had FSX installed at some point

With new PCs and no previous copy of FSX installed we should install the four simconnects as Joe mentioned.

[GSalden 4,656]

10 minutes ago, JoeFackel said:

Yeah, i also got one reply. One, further questions haven't been answered, regardless of the thousands of EUR i have spent on CPFlight hardware.

Here exactly the opposite: I remember an issue and my second email was answered very quickly. After a week I got an email if I was able to solve my issue ...

 

[Mac1 1]

Paolo now tells me that P3D v4.5 does not need that file!  Out of date manual!  I’ve had a few replies today from Paolo so things are looking up!  Just need to sort the NGXu options ini out to experiment further.....

[Mac1 1]

Thanks Steve for your input

[Mac1 1]

Thanks Joe for your help.  Guess I’ll have to go to the P3D forum to sort the ini problem out.

 

Martin

[SteveW 1,792]

7 minutes ago, Mac1 said:

Thanks Steve for your input

You're welcome.

 

The SimConnects don't necessarily show up in Control Panel.

Another thing is they can be found in the WinSxS as files, but that still does not mean they are operational, as there are other settings made in the system to allow apps to find them.

 

Might be a good idea if all else fails to double click the .msi's:

C:\Program Files\Lockheed Martin\Prepar3D v4\redist\Interface\ESPv1\SimConnect.msi

C:\Program Files\Lockheed Martin\Prepar3D v4\redist\Interface\FSX-RTM\retail\lib\SimConnect.msi

C:\Program Files\Lockheed Martin\Prepar3D v4\redist\Interface\FSX-SP1\retail\lib\SimConnect.msi

C:\Program Files\Lockheed Martin\Prepar3D v4\redist\Interface\FSX-SP2-XPACK\retail\lib\SimConnect.msi

 

[JoeFackel 760]

59 minutes ago, Mac1 said:

Thanks Joe for your help.  Guess I’ll have to go to the P3D forum to sort the ini problem out.

 

Martin

You're welcome, but i would suggest to go to the PMDG forum instead.

[Mac1 1]

Yes, it would make more sense wouldn’t it!  I get so confused!  At least they’re great for response.

[dutchkip 4]

On 2/11/2020 at 2:00 PM, Mac1 said:

Yes, it would make more sense wouldn’t it!  I get so confused!  At least they’re great for response.

Did you get it sorted in the end?