F1 23: v1.08 Update Does Not Address FFB Issues

F1 23 Update v1.08 Hungaroring Tsunoda Magnussen.jpg
The latest F1 23 update is here - but it does not address the Force Feedback issues many sim racers have raised: While they had been under investigation last week already, it does not seem that EA Sports and Codemasters were able to solve them in time for v1.08 - instead, players receive numerous smaller fixes and a nice addition to league races.

Image credit: EA Sports

Version 1.08 introduces AI opponents to league racing, letting players fill the field if there are not enough human racers taking part to have a full grid on track. This adds more depth to the mode and should make for more interesting races with more realistic grid sizes.

Two-Player Career mode also sees a vital fix, as players had reported wrong tire allocations for feature races in weekends that also have a sprint race on the schedule. Meanwhile, the qualifying Practice Programmes have been adjusted to be not as unrealistically hard as they were to date.

F1 Replay Mode Now Available​

Scenarios also make their debut with the addition of F1 Replay mode, which allows players to compete in the same circumstances as in a real race weekend, providing them with additional challenges. New scenarios will be available shortly after a Grand Prix weekend.

F1 23 Hungarian Grand Prix Update.png

New scenarios for every GP weekend will be continually added to F1 23, providing extra challenges in F1 Replay mode. Image credit: EA Sports/Codemasters

FFB Problems Persist​

However, the big fix many racers are still waiting for concerns Force Feedback issues: Users of Thrustmaster T300 as well as Logitech G923 and Pro wheel bases have reported a loss or complete absence of FFB, which EA and Codemasters are looking into according to the community-raised issues thread on the EA forums.

As these wheel models are relatively common, these issues affect a large number of players - and potentially even more when taking the point of "other various Force Feedback issues across multiple platforms" on the list of investigations into account. Considering this, the next update should mostly focus on these issues in order not to have large amounts of the player base facing problems because of their peripherals.

In the meantime, a workaround for T300 wheel bases might make lives for users of this particular hardware a bit easier:


Other issues that are still due to be patched include equal performance permanently being set to "on" in LAN races, texture and performance issues, and goals in F1 World being locked.

Since the launch of F1 23 on June 16th, patches have been released in a two-week rhythm, except for v1.08, which followed a week after the release of v1.07. Whether or not the addition of new scenarios for F1 Replay has any influence on the frequency of fixes being patched in remains to be seen - the Belgian GP is coming up this weekend already, so another update could be on the cards early next week.

You can find the full changelog for v1.08 below.

  • Addition of F1® Replay Event Type in F1® World
  • Addition of AI drivers to League Racing
  • Fixed an issue where, in some instances, unrealistic lap times could be set in Time Trial after triggering an Instant Replay. All Time Trial Leaderboards have been reset.
  • Fixed an issue where in Two Player Career drivers would receive an incorrect tyre allocation at weekends following one with a Sprint
  • Fixed an issue where Qualifying Practice Programmes would be much harder than other programs in Career
  • Fixed an issue where the pit lane speed limit in Jeddah was incorrect
  • Fixed an issue where some session start times were incorrect at Bahrain and Jeddah
  • Fixed an issue where 'Rival Telemetry mode' in Time Trial was not working
  • Fixed an issue where too many resource points were awarded despite the settings being set to 'reduced' in Career modes
  • Fixed an inaccuracy where the DRS light would be present on some F2 cars
  • Fixed an issue where DRS could be activated when behind another driver as soon as they leave the pitlane at Austria
  • Fixed an issue where timer may display incorrect time when spectating qualifying sessions
  • Fixed an issue where, in some instances, Invite Friends list would be blank when having a large number of friends
  • Fixed an audio issue where, in some instances, Max Verstappen would be given Driver of the Day instead of the actual awardee
  • Fixed an issue where the race engineer would be hopelessly optimistic
  • Fixed an issue where 'Resource Rundown Screen' would not show all earned Development Resource Points and Boosts in Career modes
  • Improved AI speed when set above 100 difficulty
  • Fixed an issue where players would be unable to join a LAN game
  • General Stability Improvements
  • Various Minor Fixes
  • Like
Reactions: dwightyone
About author
Yannik Haustein
Lifelong motorsport enthusiast and sim racing aficionado, walking racing history encyclopedia.

Sim racing editor, streamer and one half of the SimRacing Buddies podcast (warning, German!).

Heel & Toe Gang 4 life :D

Comments

I don't buy any of the F1 games so as an impartial observer I would simply say that in my opinion if a new version is published every single year then it should be released bug free.

With a shelf life of a year before the next one comes out (and presumably punters will be expected to buy the new version to replace the current one) , I don't think its acceptable for any of the user experience to be impaired because of bugs during the games short shelf life.
 
Last edited:
EA. need I say more. ;-)
you don't have to, because its wrong from first word.
EA is the owner, Codemasters are the devs. They are the lazy loosers.

If you blame directly, its the same as if you own a Porsche, but blame VW for your problems.
Because VW owns Porsche, Seat, Skoda, Audi and many more.
 
you don't have to, because its wrong from first word.
EA is the owner, Codemasters are the devs. They are the lazy loosers.

If you blame directly, its the same as if you own a Porsche, but blame VW for your problems.
Because VW owns Porsche, Seat, Skoda, Audi and many more.
EA decides what the dev's can spend their time on. Their priorities count, not the dev's priorities that's how it works. So he's not wrong.
 
EA decides what the dev's can spend their time on. Their priorities count, not the dev's priorities that's how it works. So he's not wrong.
We really don't know how the organization is. It is impossible tonmake such assumptions. To be more accurate, devs work for CM which is owned by EA. Who inside these organizations do what is unknown. What it seems (I haven't touched any F1 game since F1 2019) is that updates publication rythm has increased a lot.with this iteration, which is better support than the usual CM support before EA.

All of this could.be caused by a single management individual somewhere at CM or EA who just tries to meet some objectives to get his full bonus, as much as it could be a big EA nonsense decision (when you invest so much money in a company, you don't cut its legs to make it fail immediatly, but irrationnal decisions are a common thing).

What is sure is that these F1 games have always had issues,.often never fixed (remember the F1 2015 deadzone on a wheel, was it so hard to fix it as it was the same engine.than before? It is just an example and CM never had to wait for EA to anadoned their games. At least, it seems that F1 23 gets more support.
 
Last edited:
Premium
Its always amazed me that people think they know how companies operate internally.

Highly doubtful they even know what contracts are in place in their own places of work.
 
We really don't know how the organization is. It is impossible tonmake such assumptions. To be more accurate, devs work for CM which is owned by EA. Who inside these organizations do what is unknown. What it seems (I haven't touched any F1 game since F1 2019) is that updates publication rythm has increased a lot.with this iteration, which is better support than the usual CM support before EA.

All of this could.be caused by a single management individual somewhere at CM or EA who just tries to meet some objectives to get his full bonus, as much as it could be a big EA nonsense decision (when you invest so much money in a company, you don't cut its legs to make it fail immediatly, but irrationnal decisions are a common thing).

What is sure is that these F1 games have always had issues,.often never fixed (remember the F1 2015 deadzone on a wheel, was it so hard to fix it as it was the same engine.than before? It os just an example and CM never had to wait for EA to anadoned their games. At least, it seems that F1 23 gets more support.
In the end it's simple if you understand how a company works: The major shareholders of EA+their CEO/COO/CFO decide what the strategy is so how the end product should be and what the budget is to achieve that goal.

So the management of CodeMasters is instruced by EA's strategy/endgoals. The management of CodeMasters tells the dev's in the end where to spend their time on and what to prioritize and what not. This is in broad lines how a business works.

So in the end it's EA that's responsible for what's going on, because they have the power to change "what's going on within CodeMasters", so what to prioritize, who to fire, who to hire and what goals need to be set etc. If someone doesn't function well, they can fire them and hire someone new. The F1 disaster is going on for years, it's not a short term fail so it cannot be blamed on an individual within CM, if that was the case then he would have already been fired years ago and it's up to the HR department of EA to hire the right people to run CM.

So in the end it's EA to blame for the F1 disaster(for me it's a disaster, it's the worst VR implementation ever, it even topped ACC). In the meantime there could possible be small issues within CM, but EA has the financial deciding power to change/fix that. They are responsible in the end.
 
In the end it's simple if you understand how a company works: The major shareholders of EA+their CEO/COO/CFO decide what the strategy is so how the end product should be and what the budget is to achieve that goal.

So the management of CodeMasters is instruced by EA's strategy/endgoals. The management of CodeMasters tells the dev's in the end where to spend their time on and what to prioritize and what not. This is in broad lines how a business works.

So in the end it's EA that's responsible for what's going on, because they have the power to change "what's going on within CodeMasters", so what to prioritize, who to fire, who to hire and what goals need to be set etc. If someone doesn't function well, they can fire them and hire someone new. The F1 disaster is going on for years, it's not a short term fail so it cannot be blamed on an individual within CM, if that was the case then he would have already been fired years ago and it's up to the HR department of EA to hire the right people to run CM.

So in the end it's EA to blame for the F1 disaster(for me it's a disaster, it's the worst VR implementation ever, it even topped ACC). In the meantime there could possible be small issues within CM, but EA has the financial deciding power to change/fix that. They are responsible in the end.
Theory is not reality. Management and strategy styles vary a lot, and shareholders power is hugely overestimated, as the decisions theyvmade are generally based on false promises and false accounts and balance sheets. And one should never underestimated the power some.individuals can have in an.organization, without being part of the top management team.

As I said, stating theories and fantasies to explain an organisation we absolutely don't know anything about is just childish and uninformative. No offense but it is just true.

What I see is that with EA , the F1 series, with rhis new game, has been trying to make a step up, much more than before. It is obviously a hard task, but it must have been expected from a team who has been doing the same game for years. It is another way of working, culturally and in terms of processes. It should not be a surprise, and that's probably why the team is allowed to update the game more regularly than before. I see that as a positive thing, being an EA or CM decision. Unfortunately, the team do not have 4 years to update the game like other racing sims, this is where all of this becomes risky. Good luck to the developpers...

I must state that unfortunately buying this game was a bad customer decision, knowing the team was changing the physics, implementing new things ; it was obviously too much for a yearly release (when you think about the issues each copy paste game year after year has brought each time). Those who have paid for this game unfortunately probably have financed an experimentation which positive results will probably make their way only to the next games.

The day customers will not buy these unfinished games at day one, everything will change and these companies will re1lly invest in R&D taking real rewarding risks as they should do. Until then...
 
Last edited:
I said it when it happened and it's only getting worse...

EA is going to drive this series into the ground...
 
I don't buy any of the F1 games so as an impartial observer I would simply say that in my opinion if a new version is published every single year then it should be released bug free.

With a shelf life of a year before the next one comes out (and presumably punters will be expected to buy the new version to replace the current one) , I don't think its acceptable for any of the user experience to be impaired because of bugs during the games short shelf life.
Software development doesn't work like that... No game of that scope will ever be bug free.
 
The latest patch also BROKE the LOOK LEFT AND RIGHT ability in COCKPIT view!! All other views you are able to look left and right..cockpit view is LOCKED NOW! Not only on PC but the forums are filling up with complaints on various platforms with the same problem!!
 
So they farted out this years smegma.. that will just stay yet another broken raging dumpster fire.. again? No!? say it isnt so?!
download (5).jpg
 

Latest News

Article information

Author
Yannik Haustein
Article read time
2 min read
Views
4,322
Comments
15
Last update

Shifting method

  • I use whatever the car has in real life*

  • I always use paddleshift

  • I always use sequential

  • I always use H-shifter

  • Something else, please explain


Results are only viewable after voting.
Back
Top