WIDEFS7 sees HOTAS 52 Buttons but not Axes

[NobbyH]

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?

[Pete Dowson]

5 minutes ago, NobbyH said:

The buttons were instantly recognised and assignable, but the axes are completely ignored. Have I missed out on some extra detail?

WideFS has never read and transmitted axis values. This is because of the latency involved across a network. Axis requirements are always best on the main Sim PC.

The prime purpose of WideFS is to allow FSUIPC client applications to interface to FSUIPC on the sim PC. The transmission of button presses was added as an 'extra', but the need for axis transmission has never arisen -- for the above-stated reason.

In cases where response time is not important, it is possible to have a Lua plug-in to read the device axes (and buttons) directly (using the com library Hid facilities) and sending the results to user offsets, or even directly to Sim offsets.

Pete

 

[NobbyH]

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

[Pete Dowson]

14 hours ago, NobbyH said:

My main reason was to allow Prosim737 to talk to P3DV4/5 on a separate system; I presume this should be OK???

Yes, and you can assign your axes and calibrate them in Prosim. In fact since Prosim V3 it is important for Prosim to have the controls as it allows it to do what it needs more precisely.

Pete

 

[NobbyH]

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

[Pete Dowson]

23 hours ago, NobbyH said:

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.

That's fine -- with Version 2 it was also recommended, but not mandatory, to assign and calibrate all the main aircraft control axes in Prosim itself. Those facilities are actually mostly unchanged in V3.

23 hours ago, NobbyH said:

Are  you suggesting that the direct Prosim v2 option would be better? 

Yes, I think so. But by all means ask on the Prosim forum.

Pete