F1® 23 - Patch 1.09 Discussion Thread

For me, since this patch and starting a new save (driver career)  formation lap, safety car and red flag settings get disabled and locked after every race. I have to remember to check before every race weekend then temporarily set to 100% distance, change the settings to on then switch to 35%. Will work for that weekend but gets disabled the next so always have to remember to check.

I have had audio issues that I didn’t have before. The driver of the day is never right. Always shows one thing on the screen but a different name when spoken. Every race so far has done this. Also wrong about some analysis during the pre race voice over like saying I made a big mistake last race when I haven’t. I really don’t care about this stuff but it is a bug.

Getting over taken by AI during safety car and then not being allowed to pass them. I’ve had this issue in all the F1 games I have ever owned (2017, 2021,22 and 23). This one is frustrating but at least I can flashback.

Mid race save issue. Only had this one once as I had to go somewhere and when I came back and tried to resume, it looks like all will be fine, I see the replay and get to the point where it says to flashback but right when I get control I get an error message on the screen (don’t recall exactly what it said) and then it just starts the race again with the lights about to go out. Tried a bunch of times and same thing happened so just did the race again. 

This isn’t a bug or anything but during weather cross over periods wear I’m on slicks and track starts to get wet and lose grip but still not ready for inters, I am sliding around like crazy and can barely tap the brake or throttle without locking up or losing the rear yet the AI just blow by me like it’s nothing and by the time I pit for inters my race is done. A frustrating experience.

Night race cockpit view blurry textures. This one is very distracting and hopefully gets resolved soon. If you can’t resolve, at least turn off volumetric fog on consoles.

Handling is great and my favourite so far in the games I have owned. I do love this game just for the driving. Idon't play multiplayer, don’t care about F1 world or Braking Point and just play, Career, My Team, TT and GPs. Bugs that don’t affect gameplay don’t bother me but it does show the lack of polish and care that I would have expected from a big company, especially bugs that I have seen over and over again and ones that get patched in past games but reappear in the new ones. That is just unacceptable imho. I am lucky I haven’t had issues with my wheel or any bug that is game breaking. Feel for those who have and are still waiting for fixes.

Just my 2 cents.

I am trying to do some TT laps my force feed back went dead 4 times in one lap.

I have reported this time and time again.

This game is £100 a year!

That is iracing money.

Guess what game I am getting next..

F1 22 took it out of me, F1 23 bugs have now killed this game for me.

Also, I have to say, if it's true that Codemasters uses 2 different teams building 2 separate games from one set of code every 2 years, as opposed to taking one game, fixing that and then using that as the base of next year's game, then the problem's right there. Blindingly obviously so (again, assuming it's true). Hence why 23 has all the same bugs that were already fixed with F1 22. They're having to start all over again and it's a massive waste of time, effort and resources. It doesn't make sense. Left hand doesn't know what the right hand's doing on a blank canvas. If it's true, I can't imagine getting my head around the reasoning they would give for it.

Also, everyone who mods the game knows about how there's so much left over code from the older games, some of it way back from the 2012 era, having the game in such a mess also causes problems. I've seen multiple instances of a bugfix being, essentially, something that's been done back to front. There's also possibly fixes being implemented where there's still leftover code the current team forgets about or isn't aware of which then causes a conflict and prevents the fix from working correctly. I remember when as an 11yr old, I tried getting into coding text adventures. A whole differen't thing, I know, but the number 1 rule I was taught was, in so many words, "keep it tidy, because if there's a problem, you want to be able to know exactly how to fix it. A game in a mess is going to be a lot harder to fix." Literally a number 1 golden rule for an 11 year old, and Codies, a multi-million £££ company haven't done that. The game is, quite literally, a mess.

The terrible thing about all of this is the only way to truly fix it is to start from scratch, 1 team for continuity's sake and, again presumably the first point I make is true, only ever work upon an existing game. Fixes will stay implemented, continuity will carry knowledge of existing code through, time and effort wasted on refixing already fixed bugs will no longer be a thing. I mean, it just makes sense, right?

@s00zster That story about being two teams... Every time I see that thrown around – and I see that a lot and everywhere, from Discord to Reddit – and can't help but feel a bit sorry for it. Back when people mostly complained about reoccurring bugs from year to year, I made one of those "whatever, have nothing better to do with my life anyway" posts of mine with diagrams and bold and italicized text and all that jazz saying how common it is in the games industry and annualized franchise to have two teams focusing on different features so that every new game has something seemingly fresh to offer.

Call of Duty and Battlefield, FIFA and PES, Assassin's Creed, Far Cry, etc. All are or used to be for a good while annualized franchise. But even then, every game took 2-3 years to make. How do they pull that? By having different studios always working on their respective entries in the case of the big ones, or different teams in the same studio working on different features to always have a constant stream of new headlines for marketing to spiel year on year in the case of "smaller" ones.

When you have such a structure, say you've got a team of devs, animators and storywriters working on a feature like Braking Point. And you've already established that this mode won't feature on every new release. So you can have that team working every day on this project that usually takes 2 years to complete, and be done with it.

Now you want every new entry to feature a new Braking Point volume? Well, you can't/shouldn't cram a 2-years project in a 1-year pipeline, so you hire more people, have someone to spearhead the whole project and oversee a the main thread, and have two teams working so that every year there's one 2-years project being shipped. All those folks are still working every single day, and their output still takes 2 years to ship, but since they're on different timeframes so to speak we've got one brand new volume in the BP saga every year.

Now just expand that for all the different aspects of the game. Everybody is working non-stop, but they have different focuses and different timeframes, and you've got people managing it all from a step or two higher in the ladder.

What happens if a bug is flagged in a string of code that affects a main aspect of the game? It depends. If it was flagged and fixed by a small, focused taskforce that had only to offer post-release support for say the 2022 title, it will most definitely be flagged to all relevant teams, but they're not sitting idly there. They're working on their own list of tasks and goals, so for the 2023 game to ship with that specific line of code patched already whoever is responsible for that part needs to have received the memo from the small post-release team and have worked their way through it.

Shifting environments, I'm a lawyer. All of my firm's documents have a specific, standardized layout with headers and typefaces and footnotes. Say I'm working on this appeal for the last 10 days, it is due in 5 more days, and I'm swamped. Then the people responsible for our branding changes the layout for all our documents today, the 10th day of my 15. No one's going to touch my doc, it's sensitive and it's a work-on-progress. And will I interrupt my workflow to implement those new beauty marks and layout? Heck, no! I'll keep on working my backside off until deadline. If it happens that I complete this project in time, have worked my way through all other priorities and pending tasks, and have finally come across the "adopt new document template" task of my agenda, then ok: from now on all my output will be in the new style.

Bottomline is, no one's going to touch my pending docs to change that for me because it's sensitive and their changes unintentionally affect something, they don't want to take the heat and I don't want to do the necessary rework. Even something as mundane as a highlighted note to myself being reformatted to plain text can mess things up big time.

Yep, the franchise is most definitely a mess. But it is never as simple as Joe and Mike working on different days of the week and simply not talking to each other.

Obviously don't mean to imply that you @s00zster is painting this picture like that, I know you get it and can envisage how complex game development can be 😉

But I often get genuinely baffled by the ridiculous reductionism ad stultitiam people often insist on.