Buttons and FSUIPC

[Morten]

P3Dv4.5
Profile: PMDG 777
FSUIPC 5.157
 

Hi there

Just got rid of my old throttle quadrant and bought me a new Honeycomb Bravo Throttle Quadrant.
Then disabled controllers in general and erased all axis inside the P3D options. Then, as usual, calibrated and assigned all the Honeycomb Bravo Throttle Quadrants axis inside FSUIPC and all is good!

However my question is now, if I in full consequence, also need to assign all the Honeycomb Bravo Throttle Quadrants BUTTONS through FSUIPC in order to get everything straight forward stabile?!

The reason why I'm asking is, that I occasionally have experienced some strange random, irrational, fall outs on the FSUIPC assigned axis....
Thinking that it might could be caused by buttons which are not (yet) assigned in FSUIPC.

Cheers,
Morten           

[John Dowson]

On 3/20/2021 at 10:44 PM, Morten said:

Thinking that it might could be caused by buttons which are not (yet) assigned in FSUIPC.

No, that won't be an issue. If a button isn't assign, it just means that FSUIPC will not do anything when you press the button (except maybe log).

On 3/20/2021 at 10:44 PM, Morten said:

that I occasionally have experienced some strange random, irrational, fall outs on the FSUIPC assigned axis....

That shouldn't be happening. Can you explain what you were doing when this occurred? You could activate logging for axis events, and the next timne it happens, show me your FSUIPC log fie, as well as your ini.

Note also that your FSUIPC version is out of dat - the latest version is 6.0.13, so please update. There is also a beta version available, v6.0.14, which has support for yp to 128 buttons, and as the bravo has button numbers > 31 you may want to try this version that should allow you to assign all the butons. Its avaiilable here:

 

 

[Morten]

Hi John

Thanks indeed for your answer!

10 hours ago, John Dowson said:

That shouldn't be happening. Can you explain what you were doing when this occurred? You could activate logging for axis events, and the next timne it happens, show me your FSUIPC log fie, as well as your ini.

Thinking it over, I guess that the irrational fall outs on the FSUIPC assigned axis was a result of implementing an Aerosofts so called "BFC_Throttle_Config_PMDG_T7.json"  optional setup file into the Honeycomb-Configurator. Seems to messing up with FSUIPC. 

Thanks for the lua scripts. However for now I will prefer to just settle for the core FSUIPC axis only (+ them little reverser buttons on the throttles), and stick to the rest of the buttons already animated on the screen according to the particular aircraft.

Cheers,
Morten