Thrustmaster driver update

It seems since the last patch in the game had gotten awful at recognising my pedals. Yes I have the updated driver for TM, I’ve reinstalled it numerous times following the correct procedure. I’ve also reinstalled the game today clearing all F122 files on my machine along with all the TM files but I’m getting the same issue.

My wheel won’t work when booting up the game on PC while TLCM pedals are plugged in via USB, I take them out and my wheel works. I plug them in and my game crashes, I have the latest install/firmware/drivers for TM-PC which is the 1.TTRS.2022 with firmware 13.00 and driver 2.10.87.0. 

I’m at a loss what I can do now, I’ve followed all the guides and troubleshooted as much as I can. I have this issue with no other game and I find it frustrating that it’s as simple as having 2 USBs plugged in. 

I also have no other controllers installed. Any help would be appreciated. 

---

@Kelevra-LFC wrote:

It seems since the last patch in the game had gotten awful at recognising my pedals. Yes I have the updated driver for TM, I’ve reinstalled it numerous times following the correct procedure. I’ve also reinstalled the game today clearing all F122 files on my machine along with all the TM files but I’m getting the same issue.

My wheel won’t work when booting up the game on PC while TLCM pedals are plugged in via USB, I take them out and my wheel works. I plug them in and my game crashes, I have the latest install/firmware/drivers for TM-PC which is the 1.TTRS.2022 with firmware 13.00 and driver 2.10.87.0. 

I’m at a loss what I can do now, I’ve followed all the guides and troubleshooted as much as I can. I have this issue with no other game and I find it frustrating that it’s as simple as having 2 USBs plugged in. 

I also have no other controllers installed. Any help would be appreciated. 

---

T-LCM_RJ12-pedal_set_mode_detection.pdf (thrustmaster.com)

I suggest switching the TS-PC to non T-LCM mode, basically if the LED flashes 10 times when you power on the TS-PC it is expecting T-LCM via RJ-12 pedals.

Attaching T-LCM by RJ-12 is auto switching, but the reverse is not. If you unplug them, you need to reset the wheel mode.

A workaround is to use the T-LCM via RJ-12 until you sort that out.

If there are still issues, there is possibly an issue with your physical USB setup or the USB / chipset drivers in software.

I use USB pedals without issue with the TS-PC, but I don't have T-LCM and the wheel resets to standard mode when using the Ferrari F1 rim when using a firmware higher than v11.

v11 firmware is possible with 2020_TTRS_2 here but then driver 2022_TTRS_1 must be used with the T-LCM according to Thrustmaster.

I'm still convinced v12 and v13 are buggy firmwares, so if you want to try v11 and feedback, I'd be grateful. You don't say which wheel rim you have but the TM Open Wheel is the default for the TS-PC (which I don't have as I bought servo base only), no?

---

@ClutchAnderson wrote:
@Kelevra-LFCI have a similar issue. The game will not recognize my wheelbase if I have the TLCMs connected via USB. I can start the game w/ just the wheelbase plugged in and can actually play for about 10-15 minutes if I plug the TLCMS after getting to the menu but they eventually stop working and I have to keep unplugging and replugging to get them to work. The game finds both peripherals even before replugging as I confirmed it by connecting my Xbox controller via bluetooth. I have the most recent TM driver package also.

---

I am starting to think that this really is an issue with the Thrustmaster firmware. 

If you follow my recommendations in the post above about the wheel mode and feedback your experience along with details of your wheelbase (you don't say it is TS-PC but you use T-LCM - I digress, but this is exactly why EA are wrong not to have people post dxdiags and do proper bug reports @EA_Kent )

What I think is happening is that any wheelbase cannot detect the RJ-12 pedals until they have the updated firmware. The issue is stemming from the fact you don't use RJ-12 pedals.

I believe on TS-PC firmware v11 that the RJ-12 port is still able to detect an input from any pedalset. However, as it is not 'forced detecting' the pedalset, the axis stays at zero and the axis from the USB pedals is unimpaired.

FYI - I customise the wheelbase control schema with inputs from my USB pedals (G923 with LeoBodnar USB), it is not configured as a separate device. I am forced to do this, otherwise I get a controller not recognised message in-game (all F1 games exhibit this AFAIK).

What happens if you unbind the pedal controls on the wheelbase? (If you can successfully unbind this would be interesting - I suspect you will get the 'You can only map menu controls for devices that have no preset control scheme.' error.)

I have other older firmwares available for all wheelbases. Downgrades are possible as above.

So instead, what I think is now happening is that the newer driver does include detection of that axis in the driver but only with the newer firmware. So the game detects not only the unused wheelbase axis but the USB pedal axis as well and becomes confused, crashing the game, sending the USB bus into overdrive and / or making the USB pedals useless // conflicting.

Thrustmaster Support ticket 

RQT-050975-2022

updated

P.S. Thank you (in advance) for reading, Thustmaster Support! 😬

I'm not 100% sure I fully follow you but I don't customise wheelbase control schema's so that would make sense.

What I'm confused about is that I had a few niggling issues pre patch 1.07 but since the new patch dropped it's just constant. When I boot the game is will just detect the Wheel, I can then tab out of the game and back in which then the game will recognise the TLCM pedals but not the wheel. I tab back out and in and it will recognise the wheel and not the pedals. Just a constant back and forth, I would need to replug both USBs and boot up the game many many times to get the game to recognise them both and even then it's not without it's issues. Had the pedals drop out during a race the last time I played this way. I would like to confirm this is not happening in iRacing, no issues at all which feels like a dream after the launch of F1 22.

Interestingly, when this issue occurs where it won't detect both USBs. It appears that when I close the game, either the correct way of backing out or even ALT-F4 it totally crashes my F1 game and gives me an ego dumper.

I've done all the troubleshooting I can find.

1) I've tried a different USB hub or a USB directly on the PC

2) Uninstalled/removed all traces of F1 22 and TM FFB files from my PC

3) Followed guides while installing to ensure it's done correctly with all restarts of the machine etc.

4) Done the simple processes that never really do anything to help such as ensuring the game has Admin rights, High priority on the game, turned down graphics etc.

I've connected the pedals back with the RJ-12 for now and it works seamlessly plus the game isn't crashing. I'm new to sim racing but i've always been informed it's better to connect via USB due to the bitrate so it's frustrating as i'd rather get what I paid for. Even if I can't notice the difference i'm planning on moving to DD soon so it doesn't give me confidence that if I switch these back to USB with a DD that I won't have this issue.

What happens if you unbind the pedal controls on the wheelbase? (If you can successfully unbind this would be interesting - I suspect you will get the 'You can only map menu controls for devices that have no preset control scheme.' error.)

I can test this later this evening but yes, I get that error a lot when trying to change anything other than the racing keybinds. Strangely when in the key bind profiles, that despite the TLCM inputs not being recognised it does load the profile in game with a green tick alongside my TS-PC profile. So the game is picking up the pedals but like you said it seems to not register the inputs almost like it's on the different Axis.

I'm not going to sit and F this or F that even though this launch as been frustrating but it would be nice for either EA/CM/TM to be more vocal with such things with the community but I guess F1 life takes up too much time :P Couldn't resist.

I have a similar problem. I have the T300 RS wheel, and TLCM pedals connected by USB, not to the the base, but my base is configured to work with the TLCM in firmware if I connect them to it. In order to get both working, I start the game with only the base connected. When I reach the menu, I connect the pedals to USB, then base and pedals work as intended without any disconnects neither game crashes.

The suggestion to change the setting in the base about the pedal set connected to the rj12 connector is interesting, and makes sense in the way the base might be reporting it to the game, which in turn expects the TLCM being connected to rj12, but the game finds it connected to USB instead so not initializing them correctly. I will try changing that setting in firmware and report back in case starting the game with both devices connected work as intended.

---

@Kelevra-LFC wrote:

I'm not 100% sure I fully follow you but I don't customise wheelbase control schema's so that would make sense.

What I'm confused about is that I had a few niggling issues pre patch 1.07 but since the new patch dropped it's just constant. When I boot the game is will just detect the Wheel, I can then tab out of the game and back in which then the game will recognise the TLCM pedals but not the wheel. I tab back out and in and it will recognise the wheel and not the pedals. Just a constant back and forth, I would need to replug both USBs and boot up the game many many times to get the game to recognise them both and even then it's not without it's issues. Had the pedals drop out during a race the last time I played this way. I would like to confirm this is not happening in iRacing, no issues at all which feels like a dream after the launch of F1 22.

Interestingly, when this issue occurs where it won't detect both USBs. It appears that when I close the game, either the correct way of backing out or even ALT-F4 it totally crashes my F1 game and gives me an ego dumper.

I've done all the troubleshooting I can find.

1) I've tried a different USB hub or a USB directly on the PC

2) Uninstalled/removed all traces of F1 22 and TM FFB files from my PC

3) Followed guides while installing to ensure it's done correctly with all restarts of the machine etc.

4) Done the simple processes that never really do anything to help such as ensuring the game has Admin rights, High priority on the game, turned down graphics etc.

I've connected the pedals back with the RJ-12 for now and it works seamlessly plus the game isn't crashing. I'm new to sim racing but i've always been informed it's better to connect via USB due to the bitrate so it's frustrating as i'd rather get what I paid for. Even if I can't notice the difference i'm planning on moving to DD soon so it doesn't give me confidence that if I switch these back to USB with a DD that I won't have this issue.

What happens if you unbind the pedal controls on the wheelbase? (If you can successfully unbind this would be interesting - I suspect you will get the 'You can only map menu controls for devices that have no preset control scheme.' error.)

I can test this later this evening but yes, I get that error a lot when trying to change anything other than the racing keybinds. Strangely when in the key bind profiles, that despite the TLCM inputs not being recognised it does load the profile in game with a green tick alongside my TS-PC profile. So the game is picking up the pedals but like you said it seems to not register the inputs almost like it's on the different Axis.

I'm not going to sit and F this or F that even though this launch as been frustrating but it would be nice for either EA/CM/TM to be more vocal with such things with the community but I guess F1 life takes up too much time :P Couldn't resist.

---

Thanks for posting back.

Use USB directly on the PC, USB 2.0 if possible.(for the wheelbase, the pedals are so low bandwidth that 1.1 is actually OK)

Installing the TM driver pack should remove the installed TM driver and reboot then finish the install then ask to reboot to finish. I have used USBDeView to remove redundant entries.

Yeah the received wisdom of Admin rights, High Priority, Low settings really is a persistence.

I have fully tested and the game will play on a Standard account without issue (provided Steam and the game are installed in an Admin account, with UAC elevation in W10/11)

High priority is basically a cop out for Nvidia stutter, set up the PC properly and update the driver and firmware as necessary and it should work fine with the odd crash (usually ppl setting a setting that they've always set and never really know why)

Low settings should only be used if the PC really is bottlenecking or struggling somewhere but as much can be found from changing individual settings. Ray tracing is a performance killer as are reflections. DLSS and FSR should pick things up but any kind of scaling is usually bad. Either it's ugly or you get dips in FPS.

Tabbing in and out of the game isn't really all that good for it. I find overlays will work in Fullscreen and that way the performance is highest. Discord and Afterburner are my mains after Steam and the AMD Driver. Occasionally they break but get fixed in the end.

---

@nangu22 wrote:
Well, I tried by changing the setting in firmware, to no avail. Pedals still not registered if I start the game with them connected to USB.

Patch 1.08 seems to have introduced a new problem for me, or may be it was there but never happened before: When in a race, suddenly the game stops registering throttle inputs. Throttle get stuck at 100%, or 0%. Only way is to quit and restart the game, only to have again the same problem after a while when driving.

Took me four restarts to try to finish an ongoing Career race until I resigned in rage and closed the game.

Lots of infuriating bugs are plaguing this game sadly.

Would you mind downgrading to firmware v30?

Can be found on my dropbox here and can be loaded using the TM Firmware Updater in your current driver when copied to C:\Program Files\Guillemot\tmfwupdater\firmware

Can be used with current driver 2022_TTRS_1. When you have tested it, you can revert using the same firmware routine as the v34 firmware will also be shown.

(I advise a restart of the machine after loading the firmware).

You will see from the following that firmwares v31 through v34 actually add nothing for the T300 except this actual detection of pedals on RJ-12. 

* T300: Firmware V31 - !Warning!: with these new firmware, the racing wheel's bases now handles (and detects) differently the type of pedal set connected (via RJ12) to the base. Check out the important note and information here: http://ts.thrustmaster.com/download/accessories/Manuals/T_LCM/T-LCM_RJ12-pedal_set_mode_detection.pdf

* T300: new Firmware V32 - Added support for the Formula Wheel Add-On Ferrari SF1000 Edition - Fixed a compatibility issue on PlayStation®3

* T300: new Firmware V33 - Formula Wheel Add-On Ferrari SF1000 Edition screen protocol open for new NATIVE upcoming games !Important! Also requires to install new Firmware V5.51 on the Formula Wheel Add-On Ferrari SF1000 Edition

* T300 - new Firmware V34: Led color change + New method for inverting your pedals + Switching between PS5 mode & PS4 mode * LED Colour Change: on PC, the LED color is now GREEN instead of red / When the pedals are successfully inversed, the LED flashes once every 8 seconds * New method for inverting your pedals: Hold MODE + L3 + R3 for 5 seconds for pedals inversion * Switching between PS5 mode and PS4 mode: Press and hold the MODE button for 5 seconds to update PS4 mode (ORANGE LED) to PS5 mode (RED LED).

Just a FYI to this one, I replicated the bug with the v13 firmware on the TS-PC Racer using the Fanatec CSL-E LC Pedals. Fanatec Driver 439 and CSL-E LC firmware 1.10.

When the wheelbase is restarted it always reverts to Normal Mode with the Ferrari F1 Rim. In game F1 22 looks like this

With the wheel in Advanced Mode it looks like this

This is only possible with firmware v11 - v12 and v13 force the TS-PC into Normal Mode each time the PC starts with a USB pedalset attached and the picture reverts to the first.

I named the saved schema with the Leo Bodnar Pedals.

I'd really like a PC user with a Thrustmaster Servo Base that uses the F1 Rim and USB pedals to try the older firmware. Any wheelbase, I'm convinced the Thrustmaster firmware is faulty at v12 and v13 where they've basically added SF-1000 support in and this confounded T-LCM pedals detection that detect any USB pedalset and revert the F1 Rim to Normal Mode.

T300, T500, TX and TS-XW particularly.

Have firmwares, will share.