G29 Stopped working after installing content manager?

[Excellency]

I was trying content manager earlier today and realised when I launched the game that the wheel wasn't working, I did a quick preset load in content manager for g29 and with the default ffb settings it started working, as soon as I tinkered with the ffb settings it stopped recognising the wheel inside the game again.

I uninstalled content manager and removed it's app data, manually launched assetto corsa and it stopped working there as well.

Anyone who has had a similar issue or knows how to fix this?

[Yeyo]

try this (a friend had the same issue this week) switch the starter from appID to official and see

[Excellency]

So I fixed it, I believe the problem is that content manager messes with the controller.ini files, in this case Logitech_G29_noshifter.ini file when you load up a preset, modify it and try to save it anew. It's a bug that can cause massive problems for people because even after clean installing assetto, getting rid of cm, and cleaning up the my document/appdata files the wheel still wasn't getting recognized while trying to use the default g29 preset within assetto corsa. I found the preset file had a wheel/controller name edit, which changed it from Logitech G29 Driving Force Racing Wheel to Logitech G29 Driving Force Racing Wheel USB.

The wheel was working on all other games.

A quick fix is to manually use the wheel setup calibration and creating a new custom wheel setup file, the wheel is recognized and will map to all new settings. If you want the default g29 settings you can just copy the g29.ini text values into your new custom.ini file and you should have all the default settings with your wheel working.

Anyone about to download content manager should be prepared to face these issues and rectifying them takes awhile because a steam integrity check does not fix your files in this case. The last time I downloaded cm it messed up my ffb settings and the cars felt extremely different. However once you get around these minor issues it's much better than the default launcher and completely worth it.

[rui]

@triplesgans thank you so much for helping me with this issue. cant believe i had to go through that many steps to fix the game.

Originally posted by TripleSGans:

So I fixed it, I believe the problem is that content manager messes with the controller.ini files, in this case Logitech_G29_noshifter.ini file when you load up a preset, modify it and try to save it anew. It's a bug that can cause massive problems for people because even after clean installing assetto, getting rid of cm, and cleaning up the my document/appdata files the wheel still wasn't getting recognized while trying to use the default g29 preset within assetto corsa. I found the preset file had a wheel/controller name edit, which changed it from Logitech G29 Driving Force Racing Wheel to Logitech G29 Driving Force Racing Wheel USB.

The wheel was working on all other games.

A quick fix is to manually use the wheel setup calibration and creating a new custom wheel setup file, the wheel is recognized and will map to all new settings. If you want the default g29 settings you can just copy the g29.ini text values into your new custom.ini file and you should have all the default settings with your wheel working.

Anyone about to download content manager should be prepared to face these issues and rectifying them takes awhile because a steam integrity check does not fix your files in this case. The last time I downloaded cm it messed up my ffb settings and the cars felt extemely different. However once you get around these minor issues it's much better than the default launcher and completely worth it.

Originally posted by TripleSGans:

So I fixed it, I believe the problem is that content manager messes with the controller.ini files, in this case Logitech_G29_noshifter.ini file when you load up a preset, modify it and try to save it anew. It's a bug that can cause massive problems for people because even after clean installing assetto, getting rid of cm, and cleaning up the my document/appdata files the wheel still wasn't getting recognized while trying to use the default g29 preset within assetto corsa. I found the preset file had a wheel/controller name edit, which changed it from Logitech G29 Driving Force Racing Wheel to Logitech G29 Driving Force Racing Wheel USB.

The wheel was working on all other games.

A quick fix is to manually use the wheel setup calibration and creating a new custom wheel setup file, the wheel is recognized and will map to all new settings. If you want the default g29 settings you can just copy the g29.ini text values into your new custom.ini file and you should have all the default settings with your wheel working.

Anyone about to download content manager should be prepared to face these issues and rectifying them takes awhile because a steam integrity check does not fix your files in this case. The last time I downloaded cm it messed up my ffb settings and the cars felt extemely different. However once you get around these minor issues it's much better than the default launcher and completely worth it.

[Swansonhart]

Also had the same issue. The way I fixed it is different and simple: in Content manager go to->Settings->Controls->Axis, then click on all peripherals to test your device (steering, throttle, brakes, clutch), save preset and it works. I don't know why it solved the problem, but here you go. Trying other fixes didn't help.

[Swansonhart]

This is off topic, but maybe it will help to someone. Also happens when you use content manager only. Sometimes AI gets stuck on grid. It seems to be connected with AI difficulty in content manager, so try settings it to something like 70 +-5, 78 +-5 etc (it shouldn't be strictly 70 for example). That seems to have solved it. Weird how many issues content manager has.

[Rajesh]

I'm kind of stuck how do I do this?

[ybs.mike]

I know this is old, but I had the same problem. All I did to fix it was go into my Logi App, and select Assetta Corsa in the pre-made settings, and tht fixed it. I first tried going into CM Setting, axis nd re-saving first, but it did not work for me.

[Johnny Speed]

Happened to me last week. I launched AC normally thru steam (not content manager) and re set my controls for my wheel, saved the settings and rebooted my computer. Everything has been fine since.

[k@ramba]

My solution:

Cm->asseto corsa->control->Axes->check on left if iyour device is defined for each part, throtle, brake, clutch in other case change it ans record ur preset

[Redwingz]

thnx for the help