Tyre bug after sprint races still exist from F122

This bug still exists? Thats really unacceptable!

Yes it definitely still exists. How the new game has been released with this major issue is beyond belief!

Flagged the issue numerous times in last year’s game.  Hopefully I’ll only have to do it this once 👍

Hey @IanM282,

Would it be possible that you create a full bug report in the F123 section with a video that displays the issue again? 
I know this might have been an issue in the older title, but it would help to get this reported to the current team working on F1 23!

Thanks.

-rephii

@EA_rephiiThank you so much for your reply. I’ve not personally experienced the bug so far in F123 but others have. I have not started a new two player career campaign just yet which is when the bug occurs. 

However there are reports this week from others who have experienced the exact same issue as was previously reported in F122, which disappointingly was never addressed.

This was also highlighted on this forum yesterday by a very popular YouTube player.

Additionally it has also been reported by others this week in the bugs section of this forum. And they have provided a full report detailing the issue. So please take a look at the post there.

I simply just wanted to raise this again as it’s a major concern that will fundamentally have a huge impact and effect on people’s two player career games.

Now that there are 6 sprint races in this years game that means that on 6 occasions this bug will be prevalent and therefore having a huge impact on the integrity of any two player career championships.

This has to be of primary importance to resolve this bug as soon as possible with a patch.

Found the bug report and I have sent this to the team to take a look for the 23 game 🙂 

-rephii

Is there any response yet?

My friend refused to play F1 22 after this issue was not fixed throughout the year and I find it unacceptable for a company to leave game breaking bugs on an old title and new. 

I'm certain we were told it was fixed in a 22 patch too and it wasn't, but then I'm not sure it was fully documented.

It would be good if EA had a bug status list we could see, showing if it's accepted/investigating/planned fix and so on