I agree with your expectation. It does seem realistic.
Maybe Asobo and Microsoft need to code review every contracted add-on before general release to ensure expectation is met.
I’m not sure Microsoft/Asobo/Developer is happy with you reverse engineering copyrighted code but congratulations are your achievement creating a mod.
Yes there are expectations on developers selling products but everyone including professionals create mistakes. That is why bugs in software happen. You said this developer did code right so they became busy with writing all the code and rushed or copied key bits and didn’t correct the errors. Careless code style, bad habits.
It is precisely this that is why the DC-3 (released two years ago), the 307 and, now, the just released C-47 all have the exact same Sperry Autopilot bug.
I won’t go into the nerdy details, but one of the dev’s mistakes is not converting the aircraft’s directional turning degrees into an integer. The code is written to look for a degree value of zero to shut off the turning function and resume level flight.
It is all too easy to get the Sperry into a turn that causes this bug to trigger due to decimal degree values being read and, as such, the Sperry will just fly circles indefinitely.
I actually think AH’s Sperry implementation concept is pretty cool. They just needed to come back and fix the bug.
Two years have gone by and two copy and pastes of the same Sperry code have occurred and here we are. Three bugged Sperry APs.
It feels as though Microsoft has no QA process for these aircraft, leaving that to the devs themselves. It’s also hard to see that they really care about these ongoing issues due to how they haven’t been fixed after all this time.
As a consumer and as an avid aviation enthusiast for these amazing planes that the FF and LL series bring to us, the aforementioned is extremely disappointing.
Bugs happen and will happen. It’s what you do about them that makes the difference.
The bug reports have been written and commented upon here on this forum.
As others have stated in this thread and elsewhere direct contact with the developer has often been received with less than favorable outcomes.
None of these issues are hidden, most of them are mentioned and logged on this forum and other Internet spaces where MSFS is discussed.
Microsoft’s name is on these aircraft. It’s their sim, their Marketplace and their product. It is their responsibility to see to it the issues are addressed. Clearly, that doesn’t seem to be happening in some cases.
There is only so much we can do as it’s out of our hands — unless we take it upon ourselves to fix them out of frustration, which we shouldn’t have to do.
Much of the discord here in this very thread stems from all that I’ve tried to explain to you.
We are not all irrational, unreasonable torch and pitchfork folk here in the community.
Past history. This is not just unfounded. Just a realistic expectation of what most folks think they’ll end up being presented with. It’s up to the devs to listen or not.
Haha, I know you just wanted to nitpick on what I said because you could But if you look at the context in which my answer was written you would see that my response makes sense.
The FlyByWire A320Neo wasn’t relevant to the original point of my reply, but ofc you are right, it is an A320 product.
Many developers do have dyslexia or other disabilities and we shouldn’t hold that disability against the developer. The number 6 can look like a number 8.
If the developer is reading the topic right now, they will be under high pressure. Cut the developer slack over tiny issues.
The Boeing 307 released with an altimeter that read 5, 6, 7, 8 properly. It got one small update (the addon’s only update) and that’s when the altimeter was changed.
No, that’s ridiculous. Entirely speculative dyslexia doesn’t stop you from doing basic quality control before a release. If I had dyslexia I would make it an even higher priority to ensure that someone was double-checking any aspects of my work that could be affected by my condition, and if such an error did slip the cracks I would make it a priority to fix it. AH is not a one man show, but there are actual solo developers that manage to avoid the sloppy errors AH repeatedly makes.
Please provide a link to your source documenting that the AH developers have disabilities that preclude them from providing a work product of acceptable quality. This thread is about AH and their products, not generalized hypotheticals about imagined developers with disabilities.
As a side note, many people with disabilities consider it an insult when someone makes statements like yours, because you’re essentially saying that they are “not good at their job” and that lower quality work product should be expected. I have a dyslexic family member who prides herself on putting in the work to compensate for its effects to be as effective as anyone else in her job.
Their website indicates they have been at this since 2002. That is 22 years of experience developing aircraft for simulators.
“They” say if you do something for seven years, it makes you an expert. AH has three times that time invested.
Why, exactly, am I supposed to cut a developer with 22 years experience some slack when all the aircraft they have released for this sim that I own are the only ones I own that are rife with obvious bugs that have not been fixed? Bugs that I’ve shown, via my 307 mod, could be easily fixed with a minimum of time investment from the very people who wrote the code.
How are we to get a change of behavior if we just keep giving our money to people who do subpar work and then cut them slack when they repeatedly do the same thing over and over?
Not only they don’t fix bugs but if someone in the community fixes the bugs for them for free they will not take that and update the product. It was given to them in a silver plate.
One thing is not to have time to fix bugs which is a serious problem and another is not willing to spend 10 minutes in taking a community contribution and make it official for all the product customers. That crosses the line from bad to evil.
For the mods: It would be really nice that once a product is released if a community mod is made fixing a lot of issues and is validated by a lot of users then MS / Asobo would be able to apply that to the product and release an update without needing to wait for the dev to respond or fix the issues. It could just appear in the marketplace as “B307 community improvement mod” for free or something like that.
Great idea - let’s find a way to help the Xbox users stuck with aircraft they paid for and AH won’t update. Understanding that the DC-3 is tied to the SU process but no reason we can’t do that with Nixon’s 307 mod and what I assume will be an upcoming C-47 mod.
You are expecting people to disclose their health issues online?
You are not willing to give people flexibility if they do have health issues?
I give people flexibility as no one is 100% healthy all the time and this could be because of health issues. Take pilots for example, it’s common knowledge pilots don’t disclose health issues to the FAA because they know it can cause them to lose money and their licence. That is why issues in the cockpit happen.
It’s not an insult to provide extra support to people with disabilities, no one with disabilities should be expected to put in extra overtime or work to show they are able as anyone else in their job for the same amount of money.
It was you who implied AH developers have disabilities preventing them from delivering a quality work product, not me. You should be able to back such assertions up with facts, otherwise you are just making things up from thin air, which does not contribute meaningfully to this thread and could even be interpreted as slander.
But if you look at the context in which my answer was written you would see that my response makes sense.