Forum Discussion
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 wrote: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...
This is often repeated but isn't actually true. See the following clip (should start at the right point) for what actually happens:
- 2 years ago@Ultrasonic_77 Thanks for that. I see now at the 31 minute mark, he talks about an extra third of the team starting a year ahead, and then the rest of the team catches up, like a caterpillar movement I guess, but still one team.
I don't even know where or how the rumours of two separate teams originally started, but while it's good to know that it's one integrated and dynamically operating team, there's less of an excuse for everything being so disjointed and broken now! 😁- Ultrasonic_772 years agoHero
@s00zster wrote:
@Ultrasonic_77Thanks for that. I see now at the 31 minute mark, he talks about an extra third of the team starting a year ahead, and then the rest of the team catches up, like a caterpillar movement I guess, but still one team.
I don't even know where or how the rumours of two separate teams originally started, but while it's good to know that it's one integrated and dynamically operating team, there's less of an excuse for everything being so disjointed and broken now! 😁The 2 year thing is something that I'd seen mentioned for years on the Codemasters forum but I've no idea where it started. That video I linked to was the first time I'd ever seen any genuine info. on the subject though.
- P4st3l1ak2 years agoSeasoned Ace@Ultrasonic_77
Well, regardless how many internal teams they have, they are - clearly - not communicating properly. Otherwise we would not have repeated issues.
I still think EA/Codies have priorities which don't align with gamers' expectations.
About F1® 23
Recent Discussions
- 4 hours ago
- 3 days ago
- 24 days ago
- 30 days ago