[WIDEFS7 sees HOTAS 52 Buttons but not Axes]

Hi Pete again,

That's good to get confirmation from you. I did have a vague memory of someone on a forum saying that they did this, but  my 86-year old memory can never be trusted.

Unfortunately, my 737 cockpit was never sophisticated enough to justify taking up a Prosim737 subscription, version 2.1 covered all the function I needed and I am too old to justify spending more.

I have never found a satisfactory rationale for which system is best to take sole? responsibility for flight controls, P3D, FSUIPC5, or Prosim737.   My inclination was to FSUIPC5; you are implying that Prosim737 V3 is now the best, but not necessarily at the earlier level, or was always the best choice?

  My intention is to purchase  P3D V5 and install it on my new powerful 24-core system along with the WideFS7 server, and keep  Prosim737 on its existing registered system along with a WideFS7 Client. This avoids the hassle of re-registering and also re-assigning the hundreds of Prosim737 configuration parameters. The question then arises, "who is best to take responsibility for the physical flight control hardware?".  The choice is, the new P3d V5 system using either P3D itself or FSUIPC5, or the old system using Prosim737 V2???   At first, my answer would be attach all control hardware (  CH Yoke, Saitek Pedals, Bodnar BU836X controlled Throttle quadrant, ) to the new system and use FSUIPC5 for them all. Are  you suggesting that the direct Prosim v2 option would be better? 

  Thanks for any advice. 

Cheers, the still soldering-on, NobbyH

[WIDEFS7 sees HOTAS 52 Buttons but not Axes]

Hi Pete,

Thanks for the prompt response. The remote joystick was not an important reason for purchasing WideFS7, so no problem. My main reason was to allow Prosim737 to talk to P3DV4/5 on a separate system; I presume this should be OK???

Cheers NobbyH

[WIDEFS7 sees HOTAS 52 Buttons but not Axes]

Hi,

Just purchased WideFS7 to go with my longstanding FSUIPC5 and successfully registered. First thing I tried was a Saitek/Logitech HOTAS 52 joystick and throttle on a second system. The buttons were instantly recognised and assignable, but the axes are completely ignored. Have I missed out on some extra detail?