I did that for years here in these forums. I don’t know how many bugs I reproduced and sent up, but it was in the four-figures range. Recently, user AndyXPO started a thread because one of his bug reports got closed as “won’t fix,” and that got me searching. I discovered nearly 100 such bug reports that were closed. By a quick sampling, about 50% of these bugs were sent up by me:
Some of those bugs are simple fixes, as far as I can tell, like fixing a line in a .cfg file, so I don’t know why they were closed, but I will tell you that that list had me fuming.
I just did a look around today and there are approximately 1262 open MSFS 2024 bugs in Bug Reporting Hub , of which 50 are marked as feedback-logged and 43 are marked as bug-logged . As a percentage, that’s 7.4% of bugs that have been recorded. Now, having spent a lot of time in that category, I know that a lot of those bug reports are probably user error or add-on-related or duplicates, but even if you cut the denominator in half to make it generous, that would still mean that 85% of the real bugs in Bug Reporting Hub haven’t been recorded.
I don’t know who’s looking at all the bugs. There used to be a few people, and I have stopped paying attention to that, but the team is not big. If you average it out, Bug Reporting Hub has gotten about 90 new bug reports per day since launch. That number will go down over time, and in fact, has already gone down (the first week had about 120-150 bug reports created per day). It’s doable with the right people, but I don’t know the appetite of the team to actually sift through them and follow through with them when the bug report is ambiguous or not detailed enough. There are also tons and tons and tons and tons of MSFS 2020 bug reports that will likely never be looked at in these forums.
And unfortunately, even if they all did get logged, history shows that they might just get closed one day as a “won’t fix.”