19 minutes ago, flying_carpet said:

Will you now permanently edit you post? Originally it was only about 2 posts.

I apologise. it has increased to a "vast" staggering 5 likes.

since your post doesn't add anything to the analysis of this bug nor is it helping any user, I will now leave this thread to you and the "vast" amount of users.

Edited March 23, 20251 yr by turbomax

1 hour ago, turbomax said:

like the few likes for your comment.

Funny how you keep editing the like count. Jfc. 

38 minutes ago, Claudius_ said:

I think they have big internal problems in their team.

That seems to imply problems with individuals which we can't possibly judge.

It's a magnificent creation but big problems with the organisation of their workforce when it comes to systems of feedback, quality control and responsibility - or lack thereof - means they've yet to turn it into a magnificent product. 

 

 

 

2 hours ago, DD_Arthur said:

That seems to imply problems with individuals which we can't possibly judge.

It's a magnificent creation but big problems with the organisation of their workforce when it comes to systems of feedback, quality control and responsibility - or lack thereof - means they've yet to turn it into a magnificent product. 

 

 

 

A rogue update having any possibility to be pushed out to thousands in and of itself points to big internal problems. If you worked in our industry that would be blatantly obvious. 

Kind of funny seeing a bunch of armchair "experts" telling a highly successful gaming company how to conduct their business. 

 

Kind of funny seeing a highly successful gaming company totally screw their helpful/unpaid beta testers. Just think of the number of man-hours lost * the number of users recovering from this mess.

Edited March 24, 20251 yr by Adamski_NZ

3 hours ago, Adamski_NZ said:

Kind of funny seeing a highly successful gaming company totally screw their helpful/unpaid beta testers. 

+ some of them, still unpaid, white knighting said company in every thread. 

Absolutely pathetic.

There they are again, the defenders. MS/Asobo never do anything wrong, it's always the user. Silly ...
Alright, so we're the 'armchair experts' and MS/Asobo are the real experts, right? Then such gross blunders shouldn't happen to them. It's understandable that Asobo doesn't know much about aviation, they're just a game developer. But they should at least be software experts and get a lot of things (very) right.

19 minutes ago, flying_carpet said:

There they are again, the defenders. MS/Asobo never do anything wrong, it's always the user. Silly ...
Alright, so we're the 'armchair experts' and MS/Asobo are the real experts, right? Then such gross blunders shouldn't happen to them. It's understandable that Asobo doesn't know much about aviation, they're just a game developer. But they should at least be software experts and get a lot of things (very) right.

For sure what they did was unintended and was wrong - I believe no one denies it?

Yet, it happened to users on the beta branch, and did not affect users **already** on the "stable" version. 

If one uses a "beta" branch one adheres to the "conditions" for using it, and accepts any consequences... That's how I've been doing it, but finally decided to leave the "beta" and stay only with final releases, unless some really major / important feature I might be willing to test is made available through the beta branch some day in the Future.

So, throwing this kind of arguments as a demonstration of "how bad" ASOBO / MS are doing there work is simply ** not fair **

For me at least MSFS has been as stable and rewarding as my other general purpose flight simlator : Xp12. I'm happy with 90% of the stuff I get from MSFS ( excluding the feel of flight / flight dynamics and ground physics which I don't like as much as in Xp12 ).

I also believe MSFS has stepped in the right direction, with all of the technical consequences it may have because it's significative step, regarding a "stream-based" flight simulation platform. It's probably THE FUTURE! Easy to setup and use, providing **unique** World Scenery detail, great weather depiction (even if not perfect), and a **lot of functionality** for all flightsimmers, and offering this all for prices which are considerably lower than they used to be until now on pretty much all platforms I have used.

Can you, as a MSFS user, point something positive about it? Because otherwise I have to ask why you are still using it? Doesn't make sense to me...

 

Edited March 24, 20251 yr by jcomm

14 hours ago, flying_carpet said:

Doesn't MSFS has millions of users? I know, I have exaggerated a little for dramaturgical reasons 😄.

That wasn't a little exaggeration. Sounds like you didn't do your homework and rushed to a conclusion.

1 hour ago, jcomm said:

Yet, it happened to users on the beta branch, and did not affect users **already** on the "stable" version. 

I'm not sure this is correct. I was on the beta branch, but out of town when this problem first appeared, so my system was off for a couple of days. I read this forum post yesterday and went into XBox Insider to pull myself out of the beta. After restarting and going back into the Insider app to confirm that I was no longer in the beta, I started MSFS 2024. An 8GB download ensued, and when it was done, my Community folder had been moved to the default position (leaving my custom folder intact). I reestablished the custom Community folder, so the content appeared again, but some of my settings were reset, especially the custom camera views.

MSFS 2024 is a true technological triumph, but its implementation leaves more than a little to be desired. I don't think this will require that I do a full uninstall/install cycle, but I also can't believe that this is the best that MS/Asobo can do.

11 minutes ago, jrw4 said:

I'm not sure this is correct. I was on the beta branch, 

That's why I wrote : **already**

There were indeed users who became aware of it and tried to exit the beta before facing the "ghost" update. 😕

I left the beta now, and will probably stay with the major branch from now on to avoid such quirks.

As a matter of fact I even had a login problem one of the times I tried to start MSFS 2024 yesterday, already on the stable branch and having used it for a couple times...

Wow, so you seem to be suggesting that once the rogue update went live that it was impossible for anyone to get off of the beta branch. If true that's quite an impressive software engineering error.

 

Just a side note for at least some of users who fell into this trap. It appears that getting back to speed will only require resetting a bunch of switches and reprogramming the custom cockpit views to get all the way back. Annoying nonetheless.

1 hour ago, jcomm said:

Yet, it happened to users on the beta branch, and did not affect users **already** on the "stable" version. 

Again this is incorrect, users who left/unenrolled the beta long before Friday last week (once SU1 went live) - so that were on the "stable" version - still suffered from this weekends fiasco even though they were NOT enrolled in the beta anymore.

Regarding the infamous 8.70GB update, when checking your beta status on xbox insider hub, verify that you are checking MSFS24 and not just MSFS20, because the majority of us were in MSFS24 SU1 Beta.