MB FFB Joystick not fully operating with new 3080 PC

[Blitzen]

Recently I bought a new PC with a 3080 graphics card, for better playing with VR. I reinstalled GB with no problems...except now the throttle control on the MSFFB joystick is not fully operable.In single engined aircraft it barely operates at all at any setting and averages at about 38-51% and dit doesn’t seem to matter where the slider is positioned.Occasionally it will go up to 98% if I slide the slider up, but then immediately falls back to a lower figure. In 2 engined aircraft one throttle control will stay at a high setting while the other falls back to a lower setting. I thought this migh be a factor of “Select an Engine “ key setting but that makes no difference.I’ve tried re-setting the key setting repeatedly with no effect.

  I thought it might have been a flaw in the MSFFB install but it works properly with CLoD and the old I’ll-2 1946, so I know it is working at least with a couple of other sims.

Any ideas what to do next? reinstall? Contact Microsoft for new update on the Joystick? I need help.Thanks!

[Blitzen]

Recently I bought a new PC with a 3080 graphics card, for better playing with VR. I reinstalled GB with no problems...except now the throttle control on the MSFFB joystick is not fully operable.In single engined aircraft it barely operates at all at any setting and averages at about 38-51% and dit doesn’t seem to matter where the slider is positioned.Occasionally it will go up to 98% if I slide the slider up, but then immediately falls back to a lower figure. In 2 engined aircraft one throttle control will stay at a high setting while the other falls back to a lower setting. I thought this migh be a factor of “Select an Engine “ key setting but that makes no difference.I’ve tried re-setting the key setting repeatedly with no effect.

  I thought it might have been a flaw in the MSFFB install but it works properly with CLoD and the old I’ll-2 1946, so I know it is working at least with a couple of other sims.

Any ideas what to do next? reinstall? Contact Microsoft for new update on the Joystick? I need help.Thanks!

[DD_FT-]

To me this sounds like a double bound axis: some other axis of the stick (or maybe another controller, or a key) is bound to the throttle. The twisty bit maybe?

 

Check all throttle key-settings, 'Engines Throttle control' but also, lower down you will find 'Engine 1 throttle control', and 'Engine 2'... etc 

 

Good Luck!

 

 

[DD_Arthur]

Hi James,

Firstly, no new drivers for the MSFFB from Microsoft for donkeys years, so nothing to update.

 I’m presuming you’ve calibrated it in Windows devices?

Do you plug it into a USB 3 socket on your motherboard?

Friends of mine have had problems when moving to new systems too and have successfully run their sticks through powered and USB hubs.

 

 

[Dakpilot]

+1 on a powered USB2 hub, I had issues which turned out to be a USB3 socket 

 

Worth a look if you are indeed using a USB 3

 

Cheers, Dakpilot 

[Blitzen]

1 hour ago, DD_Arthur said:

Hi James,

Firstly, no new drivers for the MSFFB from Microsoft for donkeys years, so nothing to update.

 I’m presuming you’ve calibrated it in Windows devices?

Do you plug it into a USB 3 socket on your motherboard?

Friends of mine have had problems when moving to new systems too and have successfully run their sticks through powered and USB hubs.

 

 

Found that out after an hour with Microsoft...they did however upgrade all drivers.I’m not sure they needed it, but what the heck.Not sure about the USB3 socket..I’ll find out.

I am thinking of taking everything back to “Default “ & re-doing key mapping fresh...

[Blitzen]

2 hours ago, DD_FT- said:

To me this sounds like a double bound axis: some other axis of the stick (or maybe another controller, or a key) is bound to the throttle. The twisty bit maybe?

 

Check all throttle key-settings, 'Engines Throttle control' but also, lower down you will find 'Engine 1 throttle control', and 'Engine 2'... etc 

 

Good Luck!

 

 

Perhaps knocking everything back to default & starting again, might be the most quickest way to solve this?

[DD_FT-]

2 hours ago, Blitzen said:

Perhaps knocking everything back to default & starting again, might be the most quickest way to solve this?

Possibly, yes.

Though having never done this, I cannot be too sure