CH Controlers not working after 3.012 update

[Crockett]

After the 3.012 update my USB CH Controlers aren't working in the game. After I click enter in the sign in screen, a box comes up that say's  this -

"New Controllers found"

"CH Control Manager Device 1"

"If you want to use the key mapping of an old device for the new controller. please select it in the list and all the bindings of the old device will be moved to the new one."

"CH Pro Throttle USB"

"CH Pro Pedals USB"

"CH Pro Combatstick USB"

"Cancel"                    "Accept"

I can only choose one, either the Throttle, the Pedals or the Combatstick but not all three. I've chosen the Combatstick then clicked accept and the Combatstick isn't recognized in the game. I've clicked cancel with the same result.

How do I get the game to recognize my keymapping for CH Control Manager Device 1?

 

[RedKestrel]

EDIT - Misread response, ignore initial advice!

Just for clarification...the game is seeing CH Control Manager Device 1 as a new controller, and asking you to use the mapping for your individual CH controllers for the new one? I can see why that would cause issues, the Control Manager is the software that CH uses to merge all CH input devices into a single virtual input device. So if you import the old mapping for your CH Combat Stick, the mapping won't match to the proper inputs because CH Manager makes it look like one device with like 20 different axes and a hundred buttons.

Have you always used CH Control Manager for mapping buttons? If so, something has gotten messed up with your mapping or with Control Manager itself. But if you've never used CH Control Manager before, maybe just shut it off or remove it from your system? Maybe then the game won't recognize a 'new device' and will recognize your other devices?

Edited March 25, 2019 by RedKestrel

[Crockett]

>Have you always used CH Control Manager for mapping buttons?

Yes, I've always used CH Control Manager for mapping buttons. It's worked fine until this latest update. However, I seem to remember, in the recesses of my mind, that I had this issue once with RoF -- but for the life of me I can't remember what I did about it! I usually keep a copy in a folder of whatever advice I got that fixed past problems but I can't find anything about this issue!

[Crockett]

OK -- I fixed it!

 

I played around with input settings -- which didn't help. Then I finally just defaulted everything and that fixed it. I assume the 3.012 update  changed something in my input settings which might be why default fixed it. I'm a happy camper now!!!

[RedKestrel]

8 hours ago, Crockett said:

OK -- I fixed it!

 

I played around with input settings -- which didn't help. Then I finally just defaulted everything and that fixed it. I assume the 3.012 update  changed something in my input settings which might be why default fixed it. I'm a happy camper now!!!

Glad to hear you got it fixed!