F1 23 Logitech G923 not working / very low FFB

---

@ha6hk3w77mwj wrote:
@SteveJacksonIt never seize to amaze me how you “champions” stick up for EA even tho it’s clear to everyone that they messed up releasing a broken piece of * with bugs that where present in the beta. What’s even the point of an open beta if you don’t fix the bugs? No gamer with a G923 or G Pro is able to play the game they paid for because the force feedback doesn’t work. Get of your high horse

---

It's my personal opinion that the open beta is too close to release to really catch anything but absolute showstoppers. Not my call.

There are other open issues that are being tracked against the Logitech wheels, so it's not straightforward. These are joint issues. Not solely within EA control.

I'm not on a high horse. But the fact is that there are too many open Logitech G* FFB threads, there is not enough moderation and there is too much noise. I try to advise, but moderating is beyond my remit.

Don't know for example how many times people have been advised to update the wheels and not to use rest/snooze/quick resume modes on consoles.

It's very easy to be critical. I'm not a programmer, but I take ownership of configuring my device to work. Like it or not, consoles are like cut-down custom PCs these days.

The G923 and G Pro wheels are not finished product when you buy them. The option of updating for future compatibility is both a benefit and a hazard.

@RVladimiro F1 22 had trueforce support.

---

@RVladimiro wrote:
@ha6hk3w77mwjI have a Logitech G923 and I'm affected by all of these issues but, for what is worth, it's important to notice the differences. F1 22 did not support Trueforce and F1 23 does support Trueforce. Of all the racing games I played on Xbox only Dirt Rally 2.0 and F1 23 fully support the capabilities of the G923 wheel like all the buttons, lights and (hopefully) improved FFB.

All of this is to say that the fact that it works in F1 22 doesn't mean much in F1 23. It's a completely new implementation of the wheel that is obviously bringing new problems. It's not a question of putting the partial blame on Logitech because 1) it is a new implementation and 2) Logitech is in fact working with EA/CM to solve the issue and has even delivered a patch that will be available in a future F1 23 patch.

I'm not defending anyone, I'm upset with all of this as much as you are and would happily live without people saying I need to update the firmware of a wheel that is fully updated. I'm just setting the record straight so we are all on the same page.

---

As I’ve repeated more than once the advice to update the wheel is sound. I stand by it. 

I’m not claiming it will fix this issue. I asked to ensure people following the thread had done it - it’s a first step BEFORE posting a bug, have you done all you can to ensure it’s not on your end?

Also as I’ve repeated, others read the thread seeking answers. For the amount of people that haven’t considered these steps or aren’t even aware that they are possible, I repeat the advice.

Posters from inside CM/EA are offering the same advice, update your wheel, await the patch. 

It’s clear that some people clearly can’t grasp that and therefore it’s crossfire from the issue that some people want to take issue with me for some reason. 

I’ve only ever given advice that is helpful, I’m not trying to mislead anyone or obfuscate any issues - I speak my mind. 

Out. 

Temporary fix I've found (without TrueForce though) so the FFB works, but is not as accurate as in F1 22. Also found this thanks to @BlackNinja a few posts back.

Works for the G293
No idea if the Logitech G PRO edition this will work.

Step 1:
De-install GHub completely, also don't save any settings as this might * things up.
After GHub is de-installed press "Windows key + R" type %appdata% press enter and find any related LGHub folder in Local/Roaming and subfolders and delete them aswell.

Step 2:
Plugin the wheel, open the game and turn FFB completely OFF in calibration/FFB settings on startup. (should pop up since you deleted anything GHub related)

Step 3:

Re-install Logitech GHub with the game being "OPEN" in the background.

Step 4:
Re-enable the FFB settings through the games option settings. (If you can't use the wheel to navigate the menu, that's completely fine, it happens in this case restart your game)


Step 5:
Disable TRUEFORCE Settings in GHub.


Step 6 Optional:
Go back into %appdata% put the entire folder to "READ ONLY" so next time you boot up LGHub it doesn't overwrite settings.

Now you should have FFB back, not superdetailed but it's there and somewhat playable. Was really annoyed so have been tinkering with settings quite alot today and got it to work for Steam PC.


Keep in mind that Step 6 is optional for one reason only, that way when you restart your PC you don't have to do all this over again, but when there's finally a official fix, you'd have to UNDO read only and most likely re-install GHub again so the fix EA and Bugmasters provides works.

I really hope EA and Codemasters gets their stuff together, Since I and many other F1 Fans don't have any other alternative for F1 games, and with this pricetag it's just unacceptable that it doesn't work and we the consumer have to find workarounds for their incompetence.

Maybe one day an indie Dev makes an actual F1 game and saves us this hassle..

I just hope this is to some use to other G293 users on PC.
No clue how it works on console though, hope you get a fix soon.

Those are all valid points. I too have done everything that's been mentioned.. tried all of it before coming here to see what I'm missing. Still nothing.... this is killing my league racing. 

@RVladimiro If that were the case then how come I didn't had FFB at all when just turning TrueForce off?

If you have to believe that list, then everyone on the wheel would have 0 issues, but it isn't the case.

I've always kept TrueForce on with F1 22 and it really made a difference compared to shutting it off in the GHub.

Literally the first thing that pops up when you google it:

---

@SteveJackson wrote:

---

@RVladimiro wrote:
@ha6hk3w77mwjI have a Logitech G923 and I'm affected by all of these issues but, for what is worth, it's important to notice the differences. F1 22 did not support Trueforce and F1 23 does support Trueforce. Of all the racing games I played on Xbox only Dirt Rally 2.0 and F1 23 fully support the capabilities of the G923 wheel like all the buttons, lights and (hopefully) improved FFB.

All of this is to say that the fact that it works in F1 22 doesn't mean much in F1 23. It's a completely new implementation of the wheel that is obviously bringing new problems. It's not a question of putting the partial blame on Logitech because 1) it is a new implementation and 2) Logitech is in fact working with EA/CM to solve the issue and has even delivered a patch that will be available in a future F1 23 patch.

I'm not defending anyone, I'm upset with all of this as much as you are and would happily live without people saying I need to update the firmware of a wheel that is fully updated. I'm just setting the record straight so we are all on the same page.

---

As I’ve repeated more than once the advice to update the wheel is sound. I stand by it. 

I’m not claiming it will fix this issue. I asked to ensure people following the thread had done it - it’s a first step BEFORE posting a bug, have you done all you can to ensure it’s not on your end?

Also as I’ve repeated, others read the thread seeking answers. For the amount of people that haven’t considered these steps or aren’t even aware that they are possible, I repeat the advice.

Posters from inside CM/EA are offering the same advice, update your wheel, await the patch. 

It’s clear that some people clearly can’t grasp that and therefore it’s crossfire from the issue that some people want to take issue with me for some reason. 

I’ve only ever given advice that is helpful, I’m not trying to mislead anyone or obfuscate any issues - I speak my mind. 

Out. 

---

"Await the patch"

Yeah great, we all paid £30 extra for early access to be told to await a patch for the game to be usable. Excellent advice thanks so much. 

The problem is this

• EA has released a racing game that doesn't work with one of the biggest steering wheels in the market. That's completely insane. I will note that Logitech should have had a bit of input here as well. I mean if I was the wheel manufacturer I would have been communicating with EA (especially as it is the first new game released that will work with TrueForce so a big opportunity to show it off) and making damn sure it works
• Then the problem is made worse by them telling us that we need to go and update our steering wheels and all that crap. Do they think that we who have spent $2k on a wheel would not be smart enough to figure that out. And if you are giving a solution, maybe check if it works or not? I have read so many "solutions" but none of them work. Coupled with that is the fact that they seem to think telling us it's not just their fault is insane. The simple fact is, my wheel works in any other game perfectly. So that means it's not the wheel or my Xbox. It can only be the game. These things insult my intelligence.
• And then lastly they say, wait for the patch. ok, fair enough. Even with the above issues, I recognise that mistakes happen an not all releases happen as smoothly as you would hope. But let us know for goodness sake. Something as simple as, "We recognise that there is an issue with TrueForce wheels, we are working on it and a fix will be released in the first patch which we should be releasing 2 weeks after launch." Then at least we know. For me while I would still be disappointed, I could handle that......

Even if you update them they still dont work on this game. It is a game faalt Just admit it and get of your high horse.

Had contact with logitech and ea logitech responded ea deleted al my concerns about this problem they don't want to face it have friends with fanatecs who have the same issues it is on pc xbox and ps the problems and only with f1 23 not with other racing games so dont tell it is an update issue because we update them on a monthly bases and kalibrate them using the right tech.

It's a game issue and ea/codemaster need to fix it asap logitech already needed to step in and send ea/codemaster what to do in the early acces stages but where is the patch no ea Just don't make it in the game so please be honest and dont defend such a major fault

Day 7 of waiting for a fix… i’m a very patient person but this is beyond a joke now. We need information regarding how we can claim a partial refund for the 3 days of early access which has now turned into a week of unplayability. 

Thats what i love about the franchise, it caters to all levels of player, from novices to elitists. I have to be honest I just skipped passed all the F1 World stuff and customisation. I havent played against AI for about 3 games now. But no matter your reason for playing, when you have the inability to do so its just frustrating. I hope its all fixed soon for us G923 players. 

Yet again it's another shambles from EA releasing a half baked game.

Still waiting on these morons to give us a reply and a timeframe as to when we can expect this to be fixed.

On a side note, have people seen the yellow heading at the top of the EA Answers page where it says they are doing maintenance on F1 23 until 11:00 UTC?

Could this be to address the FFB issues?

thats just online server work. It wont be for a patch.