I mean, it would make sense to have just a beta megathread instead of a thread for each beta release, wouldn't it?

New posts would refer automatically to the latest release, and considering that it's possible to opt out of the beta but not possible to get back to a previous beta version, only the newer posts are relevant. Quite pointless to continue discussing today about the issues of beta 10 when beta 13 is out now.

What do you think?

I see your point, but I kinda like the new thread tells me it's a new update.

Soon we will have an update daily..  😉

3 hours ago, MrFuzzy said:

I mean, it would make sense to have just a beta megathread instead of a thread for each beta release, wouldn't it?

New posts would refer automatically to the latest release, and considering that it's possible to opt out of the beta but not possible to get back to a previous beta version, only the newer posts are relevant. Quite pointless to continue discussing today about the issues of beta 10 when beta 13 is out now.

What do you think?

One stickie for all MSFS betas and updates.

I don’t have the time to involve myself in Beta builds, but I’ll love to know what issues were addressed by Asobo from those Beta users as more updates come out … maybe a stick list that can be added to?

That would just be confusing. Like someone else said, I like having a new thread pop up to let me know there's new stuff, and it limits conversation to just that release.

The individual thread allows one to know there is a new update and comment on each build with refreshing honesty that is not available on MSobo.

Let's just have one big MSFS2020 thread too. 

9 hours ago, SayAgain said:

I don’t have the time to involve myself in Beta builds, but I’ll love to know what issues were addressed by Asobo from those Beta users as more updates come out … maybe a stick list that can be added to?

Asobo introduce so many regressions that you’d constantly be ticking and removing ticks from that list. 

That wouldn't work for me Fuzzy.  I'll tell you why.

Firstly, like others have said, I like to know when a new update is available, and this is announced in the forum with the new release number, i.e. 1.5.13.0 like the last one.

Two, the combined thread would get massively long, and most of that thread will also be completely obsolete information and irrelevant conversation. 
At the moment, an old thread such as for 1.15.10.0 drifts into disuse and out the bottom of the forum threads, just as it should.

So my vote would be to leave it as it is - it causes no harm.

Edited July 3, 2025Jul 3 by bobcat999

I see that most people prefer the way it is now... no issues 🙂

7 hours ago, Ianrivaldosmith said:

Asobo introduce so many regressions

You mean they fix something and then break it again later?  That’s common for Beta software, but would still be a nice list that is updated with each beta deployment.

Add-ons add a big dynamic to Beta releases, very difficult for end users to know the source of any problems that come up (aka uncheck).  I wouldn’t attempt using any Beta software with any add-ons as that would invalidate testing of the core product.  The add-on developers would need to manage that dynamic.

Nothing to stop people from testing with add-ons, but wow, that’s A LOT of work and who do you report the issue to if you don’t really know if it’s an Asobo issue or Add-On issue?  IMHO, that seems very unmanageable IF one is testing with add-ons.

1 hour ago, SayAgain said:

source of any problems that come up (aka uncheck).  I wouldn’t attempt using any Beta software with any add-ons as that would invalidate testing of the core product.

Then how would they ever know the addons don’t work upon release? I’ve never understood this logic, and I actually believe they want you to introduce addons to betas, to ensure they function. 

SUX beta indeed XD