Force Feedback T300 not working

@EA_rephii

On the ps4 T300 it continues to have loss of force feedback. I've never played it, it's a legalized theft.

Product: F1 23
Platform:Steam-PC
Please specify your platform model. PC
Summarize your bug If you will minimalize your game, and then come back to it the force feedback is gone and you need to restart your wheel (there was no such an issue in the previous f1 games)
What is your 16 digit Report Code? GCMK-PVXD-KBEG-BBSE
Can you please provide the name of your current internet service provider? UPC
Which area is the bug/glitch in? Single Player
Steps: How can we find the bug ourselves? While being in the game, (or in the pause screen in a single/multi player mode) just minimalize the game (i play in windowed fulscreen mode) and then you have no forcebeedback and you have to restart the wheel (unplug and plug in again) to make it work
What happens when the bug occurs? Force feedback is gone until you are going to restart the wheel
What do you expect to see? I expect the forcefeedback to be there after I will come back to the game

‌

After minimalizing the game I found out that my force feedback isn't working and I had to replug the wheel to make it work. (No such an issue in any other game,  i have T300 RS GT wheel) 

---

@itsfunky11 wrote:

Product: F1 23
Platform:Steam-PC
Please specify your platform model. PC
Summarize your bug If you will minimalize your game, and then come back to it the force feedback is gone and you need to restart your wheel (there was no such an issue in the previous f1 games)
What is your 16 digit Report Code? GCMK-PVXD-KBEG-BBSE
Can you please provide the name of your current internet service provider? UPC
Which area is the bug/glitch in? Single Player
Steps: How can we find the bug ourselves? While being in the game, (or in the pause screen in a single/multi player mode) just minimalize the game (i play in windowed fulscreen mode) and then you have no forcebeedback and you have to restart the wheel (unplug and plug in again) to make it work
What happens when the bug occurs? Force feedback is gone until you are going to restart the wheel
What do you expect to see? I expect the forcefeedback to be there after I will come back to the game

After minimalizing the game I found out that my force feedback isn't working and I had to replug the wheel to make it work. (No such an issue in any other game,  i have T300 RS GT wheel) 

---

Please try the steps in this thread. Check firmware.

Console users will need to attach to a PC to update.

PC users have to have the latest drivers to update the firmware.

Link is to T300RS as this is what the poster has queried. IDK why Thrustmaster don't redesign their page for prominence as the same driver is used on many wheelbases, the supported wheels are in the changelog (Release notes).

We are a bunch of players that has the latest driver and it still does not work!

You can now Alt tab without losing FFB, but when joining a multiplayer or a league game it more or less never works - really embarresing so far after the launch!

Here is another workaround (not ideal either but faster than unplugging etc): pause, then open force feedback settings, go into your preferred setup and leave again. After returning to the race it works (for me). Still a nuisance and an unresolved issue!!! EA, what are you doing?

---

@DarkWarrior32243 wrote:

Here is another workaround (not ideal either but faster than unplugging etc): pause, then open force feedback settings, go into your preferred setup and leave again. After returning to the race it works (for me). Still a nuisance and an unresolved issue!!! EA, what are you doing?

---

Thanks for the workaround.

In answer to your question, this is an ongoing monitored situation.

However, my own personal take is that ALT-TAB and minimisation is pretty much exposing the game to such a change in resources that errors are likely. This is a behavioural bug rather than a coding bug.

As with the pinned notes on console rest mode, my advice would be to uncheck the Fast Shutdown option in Windows (a power setting). If you are gaming, restart / update the machine before a session or with this mode enabled start the machine from a 'Shut Down' scenario.

Thanks for your fast response.
The issue occurs when I

A) start the game

B) when I switch to another mode inside the game (i.e. trial to a race)

C) never in my previous versions of F1

I appreciate your suspicion about the overload of resource changes between apps. But in my scenarios, I only change within the game (swap subcodes instead of a whole app code?). So, logically, if an overload of code changes causes the error, it must be a coding issue in F1 2023 that the previous versions did not have. And it looks like that it mainly concerns the subroutine that loads the T300 FFB setup (the fact that I can manually load it by just addressing it in the setup, supports this idea). Question is, why the FFB setup is not kept when switching to a different mode and has to be reloaded, in the first place,

Well, if you find these ideas lead to a solution (I am willing and ready to test it...), I would gracefully ask for a free version of the next version of F1 :-).

Good debugging!

---

@DarkWarrior32243 wrote:

Thanks for your fast response.
The issue occurs when I

A) start the game

B) when I switch to another mode inside the game (i.e. trial to a race)

C) never in my previous versions of F1

I appreciate your suspicion about the overload of resource changes between apps. But in my scenarios, I only change within the game (swap subcodes instead of a whole app code?). So, logically, if an overload of code changes causes the error, it must be a coding issue in F1 2023 that the previous versions did not have. And it looks like that it mainly concerns the subroutine that loads the T300 FFB setup (the fact that I can manually load it by just addressing it in the setup, supports this idea). Question is, why the FFB setup is not kept when switching to a different mode and has to be reloaded, in the first place,

Well, if you find these ideas lead to a solution (I am willing and ready to test it...), I would gracefully ask for a free version of the next version of F1 :-).

Good debugging!

---

T300 firmware/driver issues are a Thrustmaster joint venture. In the case of errors if they are attributable to non-gameplay environment ie Steam/EA/Microsoft factors that must also be considered then all factors must be met or eliminated before attempting replication (long winded way of saying updated) and verifying replication. 

So basically any behavioural or environmental factors that you can highlight are extremely useful. But the resulting outcome may not be a code fix, it may be along the lines of;

”Doctor, it hurts when I do ‘X’.”

”Don’t do ‘X’.”

Previous game codebases will not have been updated for F1 23 functionality or supported controllers may not make the ‘next game’list. The T300 is a PS3/4 & PC wheel, it has different recommended firmware and driver pack. Each time this occurs, the “didn’t do this in older game” is almost irrelevant to dev purpose. 

Of course the resulting forum / community feedback here is useful to players coming to the game.