Did you file a ticket with Zendesk yet? And if so, what are they saying?
Id love to…which gamertag should I report it under? 
.23 here as well.
How do you say “Hope ain’t a strategy!” in French?
I don’t see the logic in that whatsoever. This problem was such a big one because people stayed in the beta program.
Their solution is to simply kick people out of the beta, so why would you immediately opt back in if you’re concerned about version number conflicts again?
This whole situation brings two problems to light:
- beta branches of FS24 carry higher than usual risk for end users.
- if you do opt in, support will be minimal.
Which begs the question, why would any end user accept the risk of beta testing going forward? Seems like it’s not worth the trouble.
“Flighting” is a pretty common old-school terminology for beta testing software. Sometimes developers launch overlapping waves of betas, individual beta “flights”, sent to separate groups to test separate things. Separating users into “flights” or cohorts/groups is part of that. In fact, there’s an iOS app called “Test Flight” that I’ve been using for many years to beta test stuff on iPads and iPhones - it allows developers to push out non-public software releases to provisioned devices running Test Flight while keeping their mainline release, if any, on the primary App Store distribution channel for non-testers to download.
Anyway, “flighting” is just old school computer software test terminology, nothing more complicated than that.
My situation is different: Following @hobanagerik ‘s intervention above, I was able to avoid the carnage created by the 8.7 download early Saturday morning. Afterwards I had the two line items in Insider Hub like everyone else, similarly, now I only have one line item, therefore I am still opted-in from before Friday night.
The outcomes I wish to avoid now are (1) triggering the download if it is still live, which is doubtful but I shall not test that; and (2) being on the wrong version number for whatever comes next, which is a hypothetical related to their stated rationale for the whole shebang.
As to the balance of your concerns, while I get your point-of-view, I do not share it nor do I disparage it. To each their own path forward. Thanks for your concerns, however, and good flying today! I am treating myself to a PMDG 738 flight in 2020 today, the first in a week, to get away from 24 for a well deserved treat!
after the update the sim was completely reset, the community folder completely deleted and without authorization!! what the hell are those at microsoft doing? deleting people’s data in their computer without consent?!?! Really??!!
isn’t it a little illegal??
You mean, you have NOT been removed by MS as they indicated in Jane’s post yesterday? That’s … odd.
Exactly my concern.
Why didn’t they just increase the version number as normal??? I found it odd when it happened but I figured they knew what they were doing. but…
If I understand the rationale correctly, the last beta version that was marketplace-free was .24, which was public beta. They must have tested the marketplace in a closed group which would have been .23 and when it was time to close the beta .24 would have lacked the marketplace, right? So a rollback to .23 was crafted before release and that rollback had unintended consequences starting last Friday. A versioning problem which we hope has ended, but I’m not clear what comes next just yet.
They should have compiled a .25 and I doubt any of this would have happened.
so the SU2 beta its postponed ?
Yes, that might have been best.
Possibly reviewing their Beta rollout strategy, and how to avoid this situation from happening again, which is no bad thing.
you cant, it doesn’t work
I have reread the statement so many times trying to understand the thought process and the options available at the time. What I do get is that they were trying to find a way to release with minimal inconvenience to end users. There were unintended consequences to that which reminds me of the old saw that no good deed goes unpunished, right?
That happened to me and I was befuddled. I had forgotten I had created two accounts with MS using outlook and gmail. Once I figured out which email address was the correct one to log in with, all was good. In my case it was the outlook one that was the correct one.
I haven’t either.
I wonder if they auto-removed people who ended up in the second of the two groups and left the others that were in the first group (or vice versa).
I think this is more down to MS than Asobo, Who control the servers? Who release updates ?