Controls Stopped Working

Have you tried starting AC with the "Test" button in the Controls menu in CM?

I always have to do that for the first time I load AC. After that I can use the "Go" button in the Drive tab without any issues.
 
Have you tried starting AC with the "Test" button in the Controls menu in CM?

I always have to do that for the first time I load AC. After that I can use the "Go" button in the Drive tab without any issues.
Ive tried that. Still doesn’t work. Logitech G pro here. Using GHUB. Restarted everything. Frustrating
 
I too have the Logitech G Pro (Playstation edition) but playing AC on PC. I occassionally get this problem when Logitech G Hub does a huge update... CM has registered my controller as Logitech G Pro, Logitech G Pro Playstation, and I couldn't recall what other iterations. At these points, I usually have to dive back into and reset all my settings, as profiles are mapped to different named devices (thank Logitech for this on the driver side). But doesn't take very long anymore as I've done this a couple of times. Best to keep a screenshot of your settings so you can quickly remap what you need. Saving a profile might not work if Logitech decides to rename the damn thing to Logitech DD Pro in the drivers.... UGH!!!!
 
I know it's been a few months, but has anyone found a solution to this problem?

I am having a similar issue with my Fanatec wheel. Have been using it for a few years with no problems at all, but then one day I plugged it in and several of the buttons no longer worked in-game. Fantatec Control Panel and the control settings in Content Manager recognize all the buttons as working and correctly mapped.

In my case, it seems to be an issue with Steam/AC and Content Manager not playing together nicely. All the bindings that stopped working are CM-only (pause game, restart session, etc) - the ones that are generic AC shortcuts still work fine.

The only thing that changed, that I can think of, is that I plugged in my XBox controller to play a different game, which I'd never done before. That controller is no longer plugged in, but could it be that Steam is confused because of that? Seems like an odd possibility, but stranger things have happened.
 
Yes, possibly the joy=[device-index] is an issue. Open the documents/AssettoCorsa/cfg/controls.ini and change that on keys that are not working. Maybe there is a more elegant way with ContentManager for this.
 
MaSe87 -

Thanks for your reply. I hadn't considered going into the .ini files, so at first I was sure you were on to something. But I'm not sure what, if anything, I need to change in that file. Here are the bindings that aren't working, as they appear in CM:


CMButtons.jpg



And here is what the .ini file for that wheel preset says about those bindings:

[__CM_PAUSE]
JOY=0
BUTTON=9
BUTTON_MODIFICATOR=-1

[__CM_START_SESSION]
JOY=0
KEY=-1
BUTTON=1
BUTTON_MODIFICATOR=-1

[__CM_RESET_SESSION]
JOY=0
KEY=-1
BUTTON=0
BUTTON_MODIFICATOR=-1

[__CM_SETUP_CAR]
JOY=0
KEY=-1
BUTTON=3
BUTTON_MODIFICATOR=-1

[__CM_EXIT]
JOY=0
KEY=-1
BUTTON=8
BUTTON_MODIFICATOR=-1


They are all obviously off by one, which is, I assume, what the "button_modificator" is all about? But all of the bindings in the whole preset are off like that. For example, these work fine:
CMButtons 02.jpg


And the .ini for those is:

[HIDE_APPS]
BUTTON=10
JOY=0
KEY=0x48 ; H
XBOXBUTTON=-1
BUTTON_MODIFICATOR=-1

[IDEAL_LINE]
BUTTON=11
JOY=0
KEY=0x49 ; I
XBOXBUTTON=-1
BUTTON_MODIFICATOR=-1


Both CM and the Fanatec Control Panel are recognizing all those button pushes correctly when I test them. So I'm kind of at a loss.
 
Okay, not sure. If they are the same index, it should be okay. As CSP may handle that differently ... but shouldn't ... try changing those JOY= on the __CM entries to 1 or 2 just to see if that makes a difference and revert if not. Device indices are assigned from DirectInput, so not something controlled by the app. Configuring and having different amount of devices plugged in / turned on makes a difference and can change those indices and you might run into that situation.

If all fails, remove the controls.ini and redo the config from CM with all devices you use during driving plugged in and plug them in the same USB ports.

Button_modificator is a CSP addition, in CM the "No modifier" and unrelated.
 
Last edited:
Okay, not sure. If they are the same index, it should be okay. As CSP may handle that differently ... but shouldn't ... try changing those JOY= on the __CM entries to 1 or 2 just to see if that makes a difference and revert if not. Device indices are assigned from DirectInput, so not something controlled by the app. Configuring and having different amount of devices plugged in / turned on makes a difference and can change those indices and you might run into that situation.

If all fails, remove the controls.ini and redo the config from CM with all devices you use during driving plugged in and plug them in the same USB ports.

Button_modificator is a CSP addition, in CM the "No modifier" and unrelated.


Thanks again for the reply! I decided to just go for the "if all else fails" method, and deleted the controls.ini and all my preset .ini files, and start from scratch. Redid all the configurations and saved as a new preset. Which you think would have fixed it, but no luck. Very strange! There must be something I'm missing somewhere....
 
Back
Top