Game will not accept joystick (ThrustMaster) binds.

by SlimReaperTC
Reply

Original Post

Game will not accept joystick (ThrustMaster) binds.

★★ Novice

Game will not accept joystick (ThrustMaster) binds.  I can bind the throttle on the joystick, but not x-y-z of joystick.

Message 1 of 5 (598 Views)

Re: Game will not accept joystick (ThrustMaster) binds.

Community Manager

@SlimReaperTC I'm seeing some posts recently about input issues. Can you play normally with keyboard and mouse?

If you restart with a Clean Boot, does that have any effect on your binding issue?

https://help.ea.com/en-us/help/faq/how-to-clean-boot-your-pc/

David.png
Stay and Play.png
Message 2 of 5 (586 Views)

Re: Game will not accept joystick (ThrustMaster) binds.

★★ Novice

Yes, keyboard and mouse seem to work OK, now.  The joystick x-y-z axis will not bind, nor will any of the buttons on the joystick.  Buttons for the foot-pedals and throttle will bind, however.

Message 3 of 5 (573 Views)

Re: Game will not accept joystick (ThrustMaster) binds.

Community Manager

@SlimReaperTC Thank you. It looks like a lot of people have had some issues in the past with joysticks, and it's not a smooth process to get it running. 

Can you try the following? Start by removing/disabling your hardware, starting the game, and logging into the campaign, then go to the binding section.

 

Clear out all Joystick bindings in the infantry/vehicle section
Clear out all buttons for keyboard/mouse in the JetsHelicopters section


Close the game, then connect/enable your hardware.

Now pop back in and set up your joystick bindings as you wish. 

There are also community solutions/3rd party settings programs, but with such things using them is at your own risk. 

David.png
Stay and Play.png
Message 4 of 5 (551 Views)

Re: Game will not accept joystick (ThrustMaster) binds.

★★ Novice

I already found those solutions on your forums and none of them worked.

If you review my previous posts, they go back to when the game was published.

 

At this point, don't even bother replying because it's quite evident that EA has no intentions of resolving the issue...too many instances, too many complaints, too many disgruntled customers.

Message 5 of 5 (541 Views)