MS/Asobo officially admit they "rushed a little bit" regarding updates in their last video

Discussion Hub General Discussion
1

Hi,

I don’t know if you took the time to watch the last Twitch video with Jorg Neumann, head of Microsoft Flight Sim and Sebastian Wloch, CEO/CO-Founder of Asobo yesterday, but it was very interesting.

For me, the most interesting thing was that for the first time, I noticed that MS and Asobo finally recognized that they rushed their work.

In fact, @ 11.55 min Jorg Neumann admits about the updates “We rushed a little bit, and there were some regressions”.

At least they know, they have recognized it.

And they also explained how they will fix things.

Now back to work guys !

Here is the link for the video : Twitch

9 Likes
2

You missed the more important part, which is how they’re addressing this:

  • Longer periods between large updates to allow for more testing
  • Smaller and more frequent updates for critical issues
  • Going back to beta-testing builds with a ring-fenced group
9 Likes
3

I can imagine why they say that infos heh…

4

Hi I agree, as I said that was very informative. But for me admiting they rushed, was equaly important.

2 Likes
5

With my long experience as a game developer ( 0 years and 0 month :upside_down_face:) i could tell that it is better to use testing beta builds and hotfixes before this update disaster happened..

6

I’m not sure I was questioning that it was/wasn’t better. I said what they were going to do.

7

Okay, they recognized it, that they have rushed their work! Thats a first step to the right way!

longer periods between updates? Okay, thats good! Better good stuff than worse!

BUT, before they start from new, they have to provide us to roll back to 1.8.3.0 or even 1.7.12.0, so we can even a little enjoy the Sim. They can´t let us with the 1.8.3.0 and all its broken stuff!

5 Likes
8

This should be compulsory viewing for everyone on these forums

3 Likes
9

Back to Alpha 1. That was the best iteration to date.

10

I rather not have 10 feet airport vegetation back.

11

But obviously not scalable

12

Yet a release build will never come bugless.

Also, they said “more testing” which implies they did test but not enough, right?

Asobo probably got pushed a little by Microsoft which is a common thing to happen between a developer and their publisher so let’s stay fair.

3 Likes
13

Good they have recognised the issues, and taken steps to improve releases in future. Hopefully they can get on top of the problems that have occured due to this latest update, and get us all back to flying again. For me personally the last week or two prior to this update were fine.. Still cannot fly properly due to this strange jump all of a sudden to a zoom camera view which usually ends up with a CTD

14

It was a forgone conclusion they would NEED to rush the first couple of patches, and it would have been totally ridiculous not to have done so, and patch cadence naturally slows and increases in quality as things mature and they can focus on the finer details.

People like to make mountains out of molehills.

15

Gotta rush those milk bottles out for those whining babies…

16

You mean the paying consumers? Fixed that for you.

3 Likes
17

The admission that they rushed is definitely not news to anyone who’s experienced the results of said rushed work. But it was good to see them admit to their mistake and want to rectify it. I hope they can make more frequent patches / bug fixes and keep those separate from content. Having players wait weeks for the “next big patch” when there are serious bugs is not cool.

Chances are Asobo had to meet hard, inflexible deadlines set in place by Microsoft who set out a release roadmap they had to abide by. And what we got on those dates was “what they had ready”, bugs and all. That’s the only reason I can see they released the last patch complete with a CTD bug they were aware of and even mentioned in the patch notes.

Being in software development for the last 25 years (not game-related), I’ve been on the wrong end of that many times when management has decreed that something will be released on a certain date come hell or high water (typically with unrealistic timelines) while providing no extra resources to the dev team to accomplish said task. And then everyone wonders why there are bugs or things don’t work as intended upon release.

18

Correct! There is another thread this morning about how all this complaining, frustration, anger, could have been totally avoided if the product had been released as a “work in progress” or “early access” for a reduced price with the acknowledgement that the “full” version would come in the future. That’s all they had to do. (Honesty).Then, those that some idiots here like to call “whiners” would not have a reason to complain and those who wanted a finished product could have waited.
“Rushing” anything in life brings problems. They advertised one thing and sold us another. They deserve to be admonished for it. That being said, the video gave me much hope and encouragement.

2 Likes
19

Right and then everybody would have bought it at the reduced price and still complained. This makes absolutely no sense.

I have done a lot of early access and open betas. NONE have been " for a reduced price" you dont get it cheaper, just sooner. Maybe a free dlc or something but never for less than retail.

20

Agree! I suggest them this yesterday: Rolling back to 1.8.3. At least we could fly now it’s near impossible… I just can’t believe they are not saying right now : “Ok, we make a mistake, let’s go back to the previous version until we correct it!” That at least would prove that they care a little about their customers… (as we paid for a release version … no ?)

1 Like