Let’s not use it so it works for all
![]()
I don’t think that can be used as an excuse, msfs2020 also suffers from simple mouse related issues. It’s a failure of direct lead development to repair what is very obviously broken.
Here is an example of a new user trying to report a bug, and the result. I think it is worth discussing constructively:
This isn’t just about MSFS. This is the state of affairs in the software world in general.
- The zillion-dollar French Arianne rocket that blew itself up due to a 16-bit overflow.
- Naval vessels that get stopped in their tracks while in a hostile environment because of a computer crash.
- People have died in aircraft crashes caused by computers.
- Zillions of dollars in lost time by businesses who desk with software balls-ups.
- And so on.
There are two items that are interesting reading.
- They write the right stuff - a paper describing the need for software engineering to actually become an engineering discipline.
- The Inmates Are Running The Asylum - a book that describes, in detail, the importance of technology and our inability to effectively develop it.
MSFS happens to be an egregious example of this, but it is not the only one, not by a long shot.
Did the poster use any of his own words? ![]()
It would be different if consumers had reasonable remedies available to hold software companies accountable.
Out of curiosity, could you point me to the thread about it?
Thank you.
@Paytheon
I received email about your reply, see below.
“You are correct. I’m a software developer with 30 years experience who have worked with Intel, Microsoft, and others. Data is everything in software. Data coming together “CORRECTLY” and on time is a must. AI properly developed ensures everything is correct. There are so many bugs with MSFS 2024 that I can assure you it will take years to fix what Asobo has release. Why? It’s all cloud based. Relying on the Cloud Architecture alone to perform on time is calculation that should have never been taken at this level. Can they fix it? Yes. Everything can be fixed. Question is when and how? At this point in time MSFS 2020 is the best simulator platform out there next to XPlane 12. MSFS 2024 is a complete failure.”
I do not see your answer in the thread.
Did you delete it or it is hidden somewhere and I can not find it?
Or was is moderators?
Just curious how things work here in forums.
This was an ongoing, many user reports with Xbox and mice. It was closed as “won’t fix” since they were never able to replicate it in-house. It used to happen to me all the time.
This is a current, 2024 mouse-related issue:
Here’s another mouse bug:
There are more…
Nope !
Scott
Like for example this annoying issue which carried over to 2024:
Why can I control my plane while panning around in exterior view using right click but am unable to fly my plane while I use that same mouse button to view another bit of my panel?
It is not. I’ve not tried to report many bugs, and I could be wrong… But I can’t remember a single one being fixed. The last time I tried to report a bug, it got moved to MSFS2020 even tho I specified 2024 meaning it for sure will never get looked at.
Because at least for some of us (I’m including myself here), the game is a lot of fun and better than 2020 despite the plethora of bugs.
Why? Well, most of the bugs people report don’t affect me even if I can acknowledge they exist. The game doesn’t crash for me. The streaming works perfectly for me etc etc. Most of the planes that so bug ridden that they barely fly (or don’t) I don’t care about. The career works fine for me too - once I learn not to fly over midnight local. That’s obviously a bug. It was frustrating to me twice, but that was many weeks ago and now I fly about without issue for the most part.
I’m not meaning to make excuses for MS. The release was deplorable, but if one has the attitude, “How can I have fun with this?” it’s very easy to discover ways to do so.
Thank you.
Well, that is kind of ridiculous …
Lucky you. ![]()
I have opened 2 bug reports for 2020 which both referred to problems in localization files, first one for MSFS base which also included ATC-Strings and the second for a totally messed up DC-3 which was released in celebration (!) of the 40th anniversary of the franchise.
| Opened | SU number | closed | SU number | |
|---|---|---|---|---|
| base pack | Oct 3 2021[1] | SU 3/4 | Apr 4 2023 | SU 11 |
| DC-3 | Nov 14 2022 | SU 10 | Sep 28 2023 | SU 13 |
So in the case of an aircraft developed by a subcontractor (Aeroplane Heaven), it took 10.5 months to fix a couple of strings and in order to swap 4 letters (!), Asobo needed 30 months.
bug opened on that date, was persistent at least half a year before that, therefore referencing SU 3/4 ↩︎
Hah. We’re still waiting for fixes to the Boeing 307 too. I’ve not flown it in ages, but unless I miss something it still has two sixes on the altimeter which someone had to have done on purpose along with a messed up fuel system.
First AH told me on Facebook they’d fix it “soon.” Then when I asked again nearly a year later they said they couldn’t fix it because it was up to MS.
Although at this point, I’m a little worried if they do try to fix it it’ll just cause more work for @NixonRedgrave
You and me both! No joke, I’ve seriously thought about this.
FWIW… I used to work at Xbox (I was a software engineer on the Xbox One). Asobo’s process will be different here but I can at least speak to software/gaming at this scale.
For Xbox crash bugs, we would completely ignore any crashes that had less than 10,000 instances (total). When you’ve got 10 million users playing for dozens of hours a week, 10,000 crashes is just not statistically significant.
Client reported bug backlogs were in the high hundreds for each developer.
So… how likely is reporting a bug on the forums going to get the bug fixed? Quite frankly it depends on the severity of the bug and how many people it impacts. They likely don’t have the staff to fix any more than the top 30% of bugs (even that’s optimistic) because in a good week, you might knock out 3-5 bugs, if that’s all you’re doing. That’s averaged - some weeks you fix one problem that resolves a dozen issues, some weeks you cannot for the life of you figure one out. Hundreds of bugs (with new ones always coming in) * 3-5 a week, you can do the math ![]()
And then it’s time for the next product build…