May I ask, what’s the incentive to log a bug if there’s a reasonable chance that it gets closed out? I know you’re the messenger, I know that it’s not you doing the closing and that you are only communicating what’s in the bug tracker, but what’s going on? Some of those bugs that were closed had as many as 150 votes. One of my bugs that was closed had 85 votes.
8 Likes
maybe the incentive is that you dont
I’m with you. It’s going to be a process. But as long as there’s acknowledgement and some sort of communication of a roadmap, I’m going to hang in there.
I’m also with you about the need for a clearing house for bugs that’s easier to report, discuss, and receive updates. What I don’t like about the current method is that if it is reported as a bug, there can no longer be discussion, even if the bug has been fixed, or something changed (for better or worse). Most of all, it’s annoying and time-consuming when a reported bug really isn’t a bug at all, but a user’s misperception, or intentional but poor design of a feature, or some other config issue.
Either way, hang in there, bud. One piece at a time.
1 Like
The idea of the forum bug reporting is transparency. I’m in favor of it, so long as bugs actually get logged and fixed. Otherwise, it’s a waste of everybody’s time.
There can be discussion inside of a bug report, as long as it is in furtherance of that bug report. When discussion in a bug report gets to something like, “I can’t believe the devs are too insert adjective here to fix this bug,” that doesn’t belong in the bug report and moderators may take action accordingly.
If a bug has been marked as fixed and closed, anybody is within their rights to log a new bug report and reference the old bug report.
Hope that helps.
I get that. I want the transparency, too. But there really isn’t a lot of discussion allowed unless you also submit it in the bug report format which, frankly, is too tedious. Sometimes it’s not a bug - it’s just me telling them “that’s the way it’s supposed to work,” or “you have this set wrong,” or “this update changed it and now this.” Or I’m providing a lot of resources and detail as to what’s wrong with a bug someone else reported. Sometimes it’s unclear that we’re still talking about the same issue after changes occur - there’s mission creep involved.
Sometimes we just want to talk about it without the rigamarole, but we have to do so in a parallel thread and it just isn’t the best way to do that.
3 Likes
I understand your point presented here, but to my knowledge this is a configuration problem at the destination airport where this helipad is programmed to receive a C172. That’s why it accepts the slot.
Come watch twotonemurphy and relax <3 He is good at giving us positive energy about msfs2024. I am demoralized a lot since my surgery and release of msfs2024. I managed to test some and gave up… Watching Murphy until all bug, performance issues fixed. (not even talking about bandwidth issues)
I was crazy positive after seeing that amazing Cpu Core usage / gpu / resources usages at Tech Alpha test we experienced, but sadly it is not the same at release version now, it is like msfs2020 levels of cpu core usage back we are again. (some people says it is related to servers, some says it is about windows update, 24H2 23H2 vs) I also realised my posts about my findings at Tech alpha test all deleted, i was crazy happy with awesome cpu core usages and smoothness, (probably topic(s) deleted). I tested the same senario with same settings at grand canyon yesterday and it was not good at all, not even close, from avarage 68-70fps(sometimes 80) to 45-55fps, with way less cpu core usage. Gpu usages were still at max on both, identical. If i could find my previous posts about it, i was gonna open a bug report or user help topic but it is a waste of time now. I didn’t see anyone mentioning this on forums, not a single one. All those tests i did with msfs2020 latest updates, they were also a waste of time, no one cared! If they really cared all those bug reports awesome people like you created wont go in to trash bins and dissappear. Funny thing i still see same bugs from msfs2020 on 2024, it is making me so sad.
But luckily we have twotonemurphy (an awesome person from twitch), he is doing his best to save msfs2024, 10h a day. I am watching him and want to believe everything will be great in couple weeks… maybe months. I want to believe all these things related to servers and will be fixed, but i am tired.
edit: see it is crazy funny, Devs should see this also instead of bug reports Twitch
1 Like
This (the bugs) is what really worries me about MSFS2024. The server and bandwidth issues are temporary, rather sooner than later they will solve them by increasing the capacity, adding more servers, etc.
But it looks like the amount of glitches and bugs, both in the sim itself and in the aircraft, is huge. Perhaps not all of them show stoppers, but still irritants.
And I am even more worried when i remember the difficulties that asobo face with 2020 to push fixes. Some took months (or years) to be
corrected and came only with the bimonthly cycle of the sim updates (which also brought new bugs). I think there were very few hotfixes released.
The volume of work remaining, plus the usual lead times to do it, add up to a time frame of several years before the sim becomes enjoyable.
Fingers crossed that Asobo knew most of the bugs and a big patch is coming to tackle moat of them. Or that they are now able to released frequent, small patches to progressively kill all bugs.
2 Likes
The template is a hurdle that doesn’t encourage bug reporting.
Some of the bugs and issues are so glaringly transparent that you hope that they are listed somewhere and just didn’t make the go-live cut off.
5 Likes
You are well aware of the time it took to get the bugs out of 2020, some haven’t been or plan on being dealt with. This cosmetic sim of 2024 is massively bug ridden and will be that way for some time to come. Don’t look for immediate solutions, the money is pouring in.
1 Like
My god. I knew it was bad, but this has shocked me. What the heck is going on here?? What is wrong with this team! Its surreal where we find ourselves.
Total kick in the face to enthusiastic paying customers and volunteer staff.
This is a new low. Im stunned.
12 Likes
There are a lot of us doing that, pointing out the good and bad.
1 Like
Yeah, it’s soooo bad, I’m even on here posting, which is something I’ve seldom done. This is just a huge mistake on Asobo’s part. I think the money changers at Microsoft said, “Hey, this sim needs to make money, find a way”. It was pushed out the door half baked. You could tell by their faces in the video conference they could smell the disgrace.
3 Likes
Hard to understand how such glaringly obvious bugs like EFB not working in VR made it in the release. Or the beta team is radically incompetent, or they were aware and left the bugs in because they had to meet the release date. Hope that hotfixes will be much easier and frequent now that the sim is largely streamed.
2 Likes
A post by Jummivana indicates that the temple has been simplified. That happened after my last bug report so I’ve yet to try the new one 
2 Likes
Chances are the dev team knew it wasn’t ready for release and would have preferred to delay it, but weren’t allowed to do so by the higher ups.
4 Likes
Reporting anything will be utterly pointless at the minute, the only response will be " it’s YOUR internet connection "
I have just watched a flight by 320 simpilot, he lost all the cockpit sound, then external sound, loads of popping in, lag, blurry textures you name it, it definitely doesn’t create an incentive to purchase at the moment, that’s for sure.
I was thinking about purchasing for Xmas and I think a 5 week wait may be the way to go!
I would have thought Asobo could have created the Sim the way they have but with one exception, all the aircraft should be on your PC, so no waiting and looking at blurry textures and the like.
6 Likes
My thought is “Why bother reporting bugs?” MS and Asobo will only address what they want to address.
MS has a long history of ignoring end users and especially third party devs. They are why I quit developing add-ons years ago. They would promise certain things but then never deliver and then, after a release, go silent.
Also, many of the bugs I have seen so far NEVER should have passed even a cursory QC. So clearly, that was not a priority for either entity. (I mean, how does the classic Cessna 172 have no working lights?)
With the mappings to the keyboard and joysticks all nearly being wiped out, it sends a strong message that MS and Asobo will do what they want and to heck with the users.
My last version of MSFS was FSX, and now I remember why I left. Thank goodness I’m old school and purchased a retail version from Amazon, as it was easy to get a refund.
6 Likes
Exactly. That is what happens when you let bean counters and those who get big bonuses for making targets make the decisions.
2 Likes
I wrote a bug report to ZenDesk yesterday, and it was acknowledged - by email!