When will 1.09 be released?
Hello, I would like to know when 1.09 is release? because Automatic gearbox hits rev-limiter for too long before upshifting, Will change the lives of many players, and I'm waiting for that to ...
Forum Discussion
@Man0maN13000 wrote:
And also the games that receive updates several months later are not annual games, if players cannot take full advantage of an annual game before the release of the next one, they will no longer take this annual game, so I think that the annual games have very large and efficient teams for the patches otherwise it kills their license.
Just because a game is an annual release, or not, doesn't change the decision making process that the developers have to do: They either continuously rush patches out and cause new problems (e.g. you're talking about the automatic gears issue that got introduced by fixing other issues like the traction issues / AI straight line speed issues), or they wait a bit longer and try to make sure that nothing worse is introduced. I get that you consider the automatic gears issue to be critical to you, but I'm pretty sure you'd rather wait an extra week to get that fixed if it means it doesn't bring in some new, way worse issue (e.g. imagine them accidentally introducing an issue that corrupts the career save every few races).
@Tribladez As somebody who has worked in the software industry as developer, designer for over 20 years, it's usually not the developers who do these decisions, it's the managers.
The whole problem starts from the top, probably already from the F1 licensing deal that forces them to do yearly releases. They don't have enough time for that, especially if they want to have something new in the game too, so the quality suffers and the get more and more behind every year. It's very ineffecient to fix things using patches usually and take time, and the more time they allocate to this, the less time and resources they have for the next game.
I really wonder do they have somekind of automatic testing system setup at all (I mean some higher level tests, not unit testing), because it's impossible catch regressions without huge effort of manual testing otherwise (which takes a lot of time). Some of the regressions from previous fixes make it sound that they don't... Unless they knew about them, but did the patch anyway
ps. F1 Life has to be EA management demand though, it smells like that miles away and is just so stupid
The whole problem starts from the top, probably already from the F1 licensing deal that forces them to do yearly releases. They don't have enough time for that, especially if they want to have something new in the game too, so the quality suffers and the get more and more behind every year. It's very ineffecient to fix things using patches usually and take time, and the more time they allocate to this, the less time and resources they have for the next game.
I really wonder do they have somekind of automatic testing system setup at all (I mean some higher level tests, not unit testing), because it's impossible catch regressions without huge effort of manual testing otherwise (which takes a lot of time). Some of the regressions from previous fixes make it sound that they don't... Unless they knew about them, but did the patch anyway
ps. F1 Life has to be EA management demand though, it smells like that miles away and is just so stupid
@IleleeeThe annual games should find another format.
I will take the F1 games for example:
I think they have to find satisfactory graphics, a good physics engine and for 5 years bug fixes and only license updates (drivers, teams, cars, everything that needs to be updated) every years and the 5th year, new graphic engine, new physics and new things like F1 life (even if I don't find it incredible in the state) or other like use other driver for F1 hulk, vandoorn, de vries, and other in contract with f1 team.
@Ileleee wrote:
@TribladezAs somebody who has worked in the software industry as developer, designer for over 20 yearsWell, hello fellow designer (I'm also a games designer/programmer for 20+ years) 🙂
it's usually not the developers who do these decisions, it's the managers.I'm also trying to keep the conversation high level so I'm using 'developers' (as in 'development team') to cover the entire team, from the producers to the QA leads to the people doing the actual implementation. Obviously this is a big, complicated problem with lots of moving parts/people involved, and I'm simply responding to the earlier point in the thread of 'why don't they just immediately throw out every fix they have as soon as its ready to go'. We both know that approach is likely to do more harm than good.
Featured Places
