CH Control Manager not working since update

[Crockett]

I have a CH Combat Stick USB, CH Pro Throttle USB and CH Pro Throttle USB and use CH Control Manager for key mapping. However, it’s no longer working properly in the game since I downloaded an update last night. It’s been several  months since I’ve fired the game up but the last time I played IL2 Sturmovik Kuban it worked fine. Last night I started the game and it began a very large download of an update – so I went to bed while it updated. Tonight, before playing the game, I bought Flying Circus but I don’t think that’s the problem because CH Control Manager isn’t working in Flying Circus quick mission or in Kuban quick mission -- so it must have been the update! Just to be sure, I fired up RoF and CH Control Manager worked as it should. When I realized I had problems in IL2 Sturmovik Kuban, I checked  “settings/input devices/ joystick” and joystick was selected – so that’s not the problem.

When I start the game, a screen pops up that says –

Attention

New controller 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 Pedals USB

CH Combat stick USB

CH Pro Throttle USB

Cancel or Accept

The first time I saw this, I selected CH Pro Pedals USB and started the game and CH Control Manager didn’t work correctly.

When I try the quick mission in Flying Circus or in Kuban, the trigger in the Combat Stick fires the guns but the rudder pedals don’t work, nor the ailerons or flaps using my Combat Stick. My Throttle doesn’t change my engine speed but the views on it work. So parts of Control Manager works while other parts don’t work. However the up/down/right/left keys work the ailerons and rudder.

So I restarted the computer, in case a reboot was the problem and re-started CH Control Manager and then the game. This time I chose CH Combat stick USB and had the same problem. The next time I restarted the game and when the “New controller found” screen popped up, I didn’t select any of them but the CH Control Manager was still acting the same.

How do I fix this?

 

 

 

 

 

[BB5000]

I have the CH throttle quad + Yoke (not using the yoke in BOX that much, I have a Ravcore Javelin). Anyway, I have previously used CH Control Manager in mapped mode for different flight sims but with the arrival of the Javelin I decided to clean things up and only use the CH HW in direct mode. I also removed a Logitech Force 3D from my setup.

I had some issues with joystick detection when I started BOX with the new setup..Win10 detected the devices OK, but not BOX. So then I examined a config file , the ”data\input\devices.txt” I think it was. That file contained a list of recognized devices...I removed the ”old” devices (CH Control Manager Device 1 and 2 + the Force 3D) and edited the joystick assignment number for the remaining devices...and then it worked. I think it’s also possible to remove the devices.txt file and let BOS find them again..of course, the mapping has to be re-done.

Edited August 28, 2018 by BB5000

[Crockett]

22 hours ago, BB5000 said:

I have the CH throttle quad + Yoke (not using the yoke in BOX that much, I have a Ravcore Javelin). Anyway, I have previously used CH Control Manager in mapped mode for different flight sims but with the arrival of the Javelin I decided to clean things up and only use the CH HW in direct mode. I also removed a Logitech Force 3D from my setup.

I had some issues with joystick detection when I started BOX with the new setup..Win10 detected the devices OK, but not BOX. So then I examined a config file , the ”data\input\devices.txt” I think it was. That file contained a list of recognized devices...I removed the ”old” devices (CH Control Manager Device 1 and 2 + the Force 3D) and edited the joystick assignment number for the remaining devices...and then it worked. I think it’s also possible to remove the devices.txt file and let BOS find them again..of course, the mapping has to be re-done.

BB5000 -- you solved my problem. I ended up deleting the "devices" txt file and started BOS and my controllers worked just fine! I flew several missions with the Spad, Dr1 and a Yak-1b! Had a blast! Thanks for the suggestion!

[Pea_Shooter]

Thank you BB500 !! That worked !!!  (and thank you to Crockett for letting us know it worked for you)

 

After the last Microsoft Windows update, and having to reinstall the CH Contol Manager program every week , it seemed,  I had to uninstall the CH mgr software all-together.  So now I just use the CH Combat stick and pedals. 

 

 

[Relix]

deleting the devices.txt worked for me too

thanks

[[IB]Zulu]

CH control manager DO work under Win10 1903 for me. It can switch(load\unload) normally different profiles in MAPPED mode with only one exception: the number of used CH CMS devices should be the same in all profiles thus not forcing windows to re-enumerate them on-the-fly and make them invisible for CH software.

 

Hope it helps.

To be more precise. For example you have two profiles for mapped mode: one with two CMS devices, and next one with three CMS devices.  In order to switch flawlessly between them assign one more dummy or active CMS device for whatever control in 1st profile to make it use three devices as in 2nd profile. After that you can switch between them without problems.

Edited September 25, 2020 by [IB]Zulu
typo

[Voyager]

He's running into a different problem. Basically IL-2 can handle up to a certain number of controller inputs then it can't talk to new controllers. I want to say the number was around 16(?). 

 

I ran into something similar a few months back, and this was basically what I had to do too, to fix it. Though in my case it was a new pair of MFG pedals that pushed it over the edge lol

 

This comes up more with the CH Control Manager because it can make a lot of different virtual controllers, which makes it easier to accidentally fill up your inputs list.