SU1 beta bug reports of bugs which were not fixed now getting locked and archived

Well since there does not seem to be a lot of paid Q&A testers in Asobo (obviously) they only rely on unpaid members of the community :wink:

4 Likes

As far as I’ve been able to tell, you didn’t fill out a bug report, or didn’t do it properly, and that’s why your bug post was moved to general discussion.

I would be happy to fill out a bug report on your behalf but the 207A is not showing in my aircraft selection even though it’s showing streamed in my library. I will give it another shot later unless someone else would like to help you out.

I know filling out bug reports can be confusing for some so my intent with this post is not to belittle you in any way.

1 Like

I prefer strict definitions, so I keep the topics of pre-release testing and Beta releases separate.

They got paid for pre-release testing, and by corollary, we chose to pay them.
I don’t know of any software company that pays users to test a Beta release.

If you want to call the Nov 19th release a Beta, Alpha, Pre-Alpha - whatever… feel free. But you’re defining words - specifically, “Paid Beta Tester” - based on feelings.

Also, if you were paid, would you feel any better? Would it somehow make it fairer since you got paid, or would you still complain about the things that weren’t fixed? If it’s the latter, then the money really has no affect on the emotional outcome.

1 Like

I’ve put a lot of thought into this. I cannot comprehend how any company would be able to discover all the bugs in a sim as complex as MSFS unless they hired tons of beta testers, and I can see that creating chaos amongst them. And how many of them would have a passion for aviation like we do. Add to that some play in VR, some use Tobi, the variety of controllers, and Xbox and PC users, and so on.

I feel that we as users of a product as complex as this are best qualified to find bugs and fill out bug reports. Some of us are pilots in real life, some of us are pilots in the sim, and some of us are armchair players that just have fun…that’s me. We have a very diverse community. Furthermore, beta testing is entirely optional. If I want to join beta testing, I can…noone is forcing me to.

However, I am not in favor of archiving bug reports. I feel that policy needs to be revised. I like the idea of moving bug reports somewhere where they will still get the attention they deserve.

Sure, it’s easy to copy and paste and fill out a new bug report. But there is more to it. Someone actually took the time and, in most cases, did some research before filling out the bug report. Many take the time to include screenshots. There is effort taken to fill out bug reports and I simply find it stunning any outstanding bug reports get archived!

6 Likes

I did fill out a bug report. It had 2 votes too! Not sure what the point of reporting bugs is if they just close them out or move them to user support.

Guess it clears the plate for them. SU1 beta they had 46654? bugs, post SU1 they only have 2 bugs reported. Looks like progress while nothing getting addressed.

Guess just report the bugs in the bug report section instead of SU x.x beta bug report, that way the bug won’t get closed out, IDK :man_shrugging:t2:

10 Likes

They will move bug reports to the beta section, if it’s a new bug in that beta.

I really can’t understand, why they not just add the unfixed reported ones to the regular bug section. I understand, that this takes some kind of time and effort, but mods generally check for duplicate reports anyway, if the bug reporter didn’t check in advance (which they should have).
I’m not going to file any bugs anymore in future betas, if they just get brushed under the rug (archived and never looked at again).
And actually expecting us to start new bug reports for the same issues, is just ridiculous.
Have they lost their minds. No wonder this hole thing is such a mess.

6 Likes

We appreciate the feedback that everyone here has provided about the post-beta archival process. A reminder: please keep further conversation civil and constructive.

As my fellow Community Manager @SeedyL3205 mentioned earlier - it’s our standard practice to archive threads from the beta subforum. This is to keep conversation directed towards the proper categories and subcategories for the live build. Having bugs be re-submitted after the beta ends also gives us a better view of what bugs have persisted and get a more accurate look at how many people are experiencing them now in the live build.

That being said, I definitely understand that it is frustrating, especially when it seems like we’re wiping it all clean and dusting off our hands. Please just know that logged bugs from the beta that have not yet been resolved are still logged in our system.

Once again, thank you for the feedback here. I can’t make any promises, but we’ll take it into consideration when we hold our next beta.

5 Likes

If they had employees doing QA, these would get paid, no?
The point is they don’t seem to have many if at all. And they don’t respect the work of those doing it for free, by archiving bug reports, a way to make these go away obviously.

3 Likes

I’m sorry but this exact issue was brought up a couple of years ago regarding beta reports being archived, then having to resubmit the report in another section. Only to still see those bugs in the next beta build for the next sim update, the whole beta bug reporting process (not to mention overall implementation) is and has been poor for some time and needs urgent review from top to bottom.

Fundamental changes are needed, as Microsoft you should have a better understanding of these beta procedures than what has been in place for MSFS2020 and now MSFS2024, it requires vast improvement. Thanks

9 Likes

I just wish people did not always assume they know, when they don’t. I can understand if you are new, but after a while it should be evident that the people involved with this product are not evil, or stupid, least of all do they want to screw us over.

Good grief people, these guys have worked their proverbial behinds off with hundreds and hundreds of bug fixes. I have a special one that has been around since the launch of 2020 and has never been fixed (or at least I still think so): the shadows under the bridges. Should I now start a tirade against the CMs, Asobo and Microsoft because of that? No, I understand the bigger picture, and have utmost respect for all the work they have been doing to improve the sim, 2020 and this one. I understand that me and my personal issue is not the most important one. I start the sim and experience it as it is, without concentrating on my personal issue. And you know what? I enjoy it. Both 2020 and 2024.

I cannot understand, especially after seeing the release notes, how people can still claim they don’t want to or even know how to improve the sim, just because some bugs were not fixed.

3 Likes

Unless you have some inside knowledge of the Microsoft and Asobo corporate structure, your second sentence is pure speculation.

And believing that the archiving of bug reports is an intentional attempt to dismiss them is an accusation that - while you have the right to express it - seems to me to be based on purely on feelings, not facts. If you have knowledge about the actual reasons that the rest of us don’t have, please, by all means share it.

3 Likes

Might want to check the definition of “seem” ? In no way did I write that I know it, which makes your first sentence rather unnecessary. As to your second, you might agree that what is archived and locked simply disappears into the abyss of this forum.

At the end of the day, they did, even if it wasn’t their intention, they sold us something with thousands and thousands of bugs and many announced features are not present or in an unusable state. (real life world ship traffic, usable atc, real world traffic with correct liveries and flight plans, etc, etc)

2 Likes

My open SU1 regression bug ticket from the beta forum was moved by someone to the appropriate bug reporting subforum.

Thank you, that’s the way to go for open bugs. :+1:
I guess those of you who still have open bug tickets in that forum can do this manually if they are not yet locked.

With beta 1 related pure discussions … well, for me it’s OK that they get achieved because no votes are lost.
Just my 2c.

2 Likes

Alright, I’ll walk back my first sentence. Using the word ‘seems’ does make it less declaratory.

As for the archiving issue. Yes, those bugs are being intentionally archived. But I disagree that they are being intentionally dismissed forever. They are simply no longer being actively addressed once the Beta release has ended. Kind of a ‘preemptive strike’, clearing the board for the active SU1 release, if you will.

The community Manager iinKWest spelled it out in a post above.

Yes, that means that bugs that went unresolved in the Beta release will have to be reported again, which is frustrating. But how big do we want the bug list to get? Personally, I want them working on priorities.

1 Like

Many of the bug reports now being locked and archived have not received a “bug-logged” tag. In essence, if we want these fixed, it essentially means that someone will have to repeat the task of creating a new topic. It would be more efficient if such original reports would be moved to an appropriate forum section instead of simply locking and archiving these.
I agree that my second sentence was provocative and is in no way backed by evidence of any kind.

5 Likes

The entire game is still a beta as it is. Why it was not released as an early access release is beyond me!

7 Likes

The sky looking overexposed is now a “thing” with SU1. The original game version never had this. They changed the HDR auto exposure values in one of the beta updates and people were complaining like mad about it, there was even a dedicated thread. I guess you missed that? Very surprised by your response, I must say.

So, no, it’s not my TV, a QLED which does both HDR 10 and DV.

2 Likes