4 minutes ago, March Hare said:

I recall they were looking for partners, which probably means helicopter manufacturers for licencing of helicopter types, names, etc. Don't recollect them saying they are outsourcing (the development of) them, but I could be wrong.

This was mentioned in the last Q&A, but I'm not sure about the details. Perhaps a native speaker can decipher those details.

Kind regards, Michael

Yes, they were talking about Helicopter manufactures.

6 minutes ago, Tuskin38 said:

Yes, they were talking about Helicopter manufactures.

Thanks. I presumed so.

On 10/29/2021 at 9:07 AM, Tuskin38 said:

They don’t ignore the testers.

It’s based off the amount of votes on the forum. This list isn’t Asobo’s internal priority list. It’s not the order they’re fixing stuff in. It’s just the top issues voted on by the community.

They will delay updates if the issues found during testing are too big. Unless there’s some hard deadline they can’t miss.

You speak so confidently on the internal workings at Asobo/MS.   I didn't realize you had become such a trusted spokesperson for MSFS 2020.  You should request a commercial member forum tag from Avsim or something indicating your level of involvement.  If not, you're simply speculating like the rest of us 
"ordinary" simmers.

10 hours ago, irocx said:

You speak so confidently on the internal workings at Asobo/MS.   I didn't realize you had become such a trusted spokesperson for MSFS 2020.  You should request a commercial member forum tag from Avsim or something indicating your level of involvement.  If not, you're simply speculating like the rest of us 
"ordinary" simmers.

They've explained it before during Q&As. It's not speculation.

Plus you know, observations? The bugs aren't fixed and the wishes aren't completed in the order they're listed.

Edited November 1, 20214 yr by Tuskin38

Approach flyback bug pushed to the end of Feb 2022 

18 months with this bug... 😡

9 minutes ago, MrFuzzy said:

Approach flyback bug pushed to the end of Feb 2022 

18 months with this bug... 😡

Is this is tied to what Working Title are doing with the navigation systems? Their system is in beta now then will be integrated into the sim properly, to replace the current default system, so I guess end of February is the time scale for the integration?

1 minute ago, March Hare said:

Is this is tied to what Working Title are doing with the navigation systems? Their system is in beta now then will be integrated into the sim properly, to replace the current default system, so I guess end of February is the time scale for the integration?

I guess so... it is now clear that Asobo is unable or unwilling to fix that bug.

They promised to fix it with SU6 but they didn't.

1 minute ago, MrFuzzy said:

I guess so... it is now clear that Asobo is unable or unwilling to fix that bug.

They promised to fix it with SU6 but they didn't.

It won't be a case of unwilling. If it's going to be fixed when WT's work is completed and integrated properly, there's no point expending time and resources fixing the default systems that are due to be replaced within a few months anyway. Obviously it doesn't help in the meantime, but it's logical.

6 hours ago, MrFuzzy said:

I guess so... it is now clear that Asobo is unable or unwilling to fix that bug.

Asobo initially attempted to fix this themselves with Sim Update 4 (the initial release noted in the Feedback Snapshot), but after being considered fixed, Working Title reported that it was still occurring in many cases, so they took over it.

They have made some small fixes beyond the NXi which is immune to the bug, but it is true that it will be completely eliminated when they upgrade all aircraft to their new navigation and autopilot systems. I guess the only way it could have been fixed sooner is if they had brought Working Title on-board earlier.