numbering of the buttons change

[hieu abc]

Good morning all

 

With Prepar3D V4, Fsuipc5 (recorded), iFly2Fsuipc, iFly 737, share twice the numbering of the buttons on my Thrustmaster T 1600M Throttle has changed for no reason, a number shift of all the buttons,

I specify my problem originally at the first power up with the Throttle Thrustmaster T 1600M button N ° 1 of the Thrustmaster manual was recognized N ° 1 by Prepar3D and Fsuipc.

Now and after several Simu sessions and without season, it is still recognized as N ° 1 by Prepar3D OK, but problem N ° 0 by Fsuipc and so on for the other buttons in Fsuipc.

I did a reset of Fsuipc5 but this reset did not solve the problem. it is therefore necessary to repeat the assignment of all the buttons each time.

Note: I don't do the same button assignments in FSUIPC and in P3D,

thanks in advance

[Thomas Richter]

Hi,

button and axis numbering in FSUIPC is the logical numbering where the first button or axis is 0(zero). P3D and Windows in controller panel show the first button as 1(one).

So in Windows controller panel the Button 1(one) is the actual Button 0(zero) you see in FSUIPC.

Thomas

[Pete Dowson]

5 hours ago, hieu abc said:

With Prepar3D V4, Fsuipc5 (recorded), iFly2Fsuipc, iFly 737, share twice the numbering of the buttons on my Thrustmaster T 1600M Throttle has changed for no reason, a number shift of all the buttons,

Button numbers are determined not by FSUIPC but by the data read from the USB device.  It is impossible for FSUIPC to change them, and once assigned the button number in the assignment can't change by itself.

As Thomas says, FSUIPC numbers the buttons from 0 to 31. Internally Windows does the same, but it adds 1 for display,  giving 1-32. This has always been the same and does not change by itself.

If you assign in FSUIPC you should disable controllers completely in P3D otherwise you will get conflicts and the sort of confusion you are currently suffering.

Pete