No mention of an AP fix in the next patch - Unacceptable

[Scottoest 1,561]

6 minutes ago, Dominique_K said:

I agree that the voting system reeks of PR and encourage spamming. We saw that with a poll on this Avsim forum some months ago when the VR army mobilizedits troops to go to the front 😁.  But again, there is no good way to please everybody, at least we know that they have some of the items listed in mind.

From looking at the feedback list, it doesn't really seem like the votes are a be-all-end-all decider for what they prioritize.  The stuff that is "WIP" is all over the place in terms of votes, and some highly upvoted stuff is not started.

The devs aren't dense, and I'm sure they understand the limitations of a voting system for bugs.

[Dominique_K 10,152]

54 minutes ago, Scottoest said:

From looking at the feedback list, it doesn't really seem like the votes are a be-all-end-all decider for what they prioritize. 

 This is what the alpha testing has clearly shown. They take the feedback of users as they deem fit, not to say with a large pinch of salt. 

The Asobo folks are not dense but the Microwoft PR should consider toning down the hype to more reasonable leVel  (that includes Neuman). They are in my opinion a major source of the backlash we hear from frustrated users. But you know the story of the frog and the scorpio...

 

[JRBarrett 3,121]

5 hours ago, Concorde79 said:

The bouncing autopilot needs to be a #1 priority in the fix list ! Not at patch 5 or 9.

It may not be an easy fix because it does not affect all users. I have had zero issues with the autopilot in the TBM since the patch came out. It operates no differently after patch 3 than it did in patch 2. I have tried to deliberately provoke the “dolphin dance” by climbing at various airspeeds in both IAS and VS modes to capture altitudes at both low and high levels, and it works correctly every time - captures smoothly and holds selected altitude with no vertical oscillations.

I am in no way suggesting that the bug is not real - there are far too many reports to dismiss it. But, whether it occurs or not obviously depends on something unique to the configuration of the end-users’ MSFS installations that are seeing the problem. It could be related to graphics settings, or specific external controllers being used, or the Windows version in use, or whether certain MS Windows updates have been applied or not.

For any users experiencing the problem, a report to Zendesk is essential, with as much information as possible as to what steps led up to the issue. Running DXDiag and attaching the results to a Zendesk report might also be helpful, as that will give information as to what specific hardware is in use on the computer, which drivers are installed, OS version and update status etc.

”Universal bugs” that affect every single end user, and can be reliably duplicated by the developers, are easy to fix by and large. The missing sensitivity settings in the controller UI in patch 2 is in that category. The CTD caused by opening the VFR map is evidently in that category too, (especially since Asobo knew about it even before the patch came out). It has not affected me, but only because I don’t use the VFR map, and I have no wish to provoke a CTD by deliberately opening the map in flight “just to see what will happen”. Since that is now listed as “fixed” for the next patch, I assume Asobo found exactly what was causing it.

Mods can also have an effect. I was a participant in a recent thread where several users were reporting that the altitude capture function was working incorrectly - altitude was not capturing at the indicated altitude on the altimeter based on current barometric pressure, but at the indicated altitude corresponding to a pressure of 29.92. A lot of assumptions were made that this was a bug caused by the latest patch, but it turned out that it is caused by a bug in the latest version of the Working Title G-1000 mod, which came out right about the same time as the patch.

Edited October 10, 2020 by JRBarrett

[HiFlyer 9,371]

3 hours ago, Dominique_K said:

I agree that the voting system reeks of PR and encourage spamming. We saw that with a poll on this Avsim forum some months ago when the VR army mobilizedits troops to go to the front 😁.  But again, there is no good way to please everybody, at least we know that they have some of the items listed in mind.

Yet this very thread is essentially mobilizing troops to go to the front, and suddenly everything is fine....

And when everybody gathered to push for track IR,  suddenly mobilizing troops was also A-OK.

And encouraging people to vote for their favorite Sims in the navigraph survey? Fine.

These different standards are seen and noted, here and in other places.

 

[Dillon 2,198]

51 minutes ago, JRBarrett said:

It may not be an easy fix because it does not affect all users. I have had zero issues with the autopilot in the TBM since the patch came out. It operates no differently after patch 3 than it did in patch 2. I have tried to deliberately provoke the “dolphin dance” by climbing at various airspeeds in both IAS and VS modes to capture altitudes at both low and high levels, and it works correctly every time - captures smoothly and holds selected altitude with no vertical oscillations.

I am in no way suggesting that the bug is not real - there are far too many reports to dismiss it. But, whether it occurs or not obviously depends on something unique to the configuration of the end-users’ MSFS installations that are seeing the problem. It could be related to graphics settings, or specific external controllers being used, or the Windows version in use, or whether certain MS Windows updates have been applied or not.

For any users experiencing the problem, a report to Zendesk is essential, with as much information as possible as to what steps led up to the issue. Running DXDiag and attaching the results to a Zendesk report might also be helpful, as that will give information as to what specific hardware is in use on the computer, which drivers are installed, OS version and update status etc.

Jim take a break from the TBM and try taking the Longitude up to 40,000ft. You’ll see the problem.  It’s universal to all users.  Asobo made a change to the sim’s FDE (reported as an update in the last patch) and now an adjustment needs to be made to some models.  Bottom line is some of us paid for the Premium aircraft and that decision has been a nightmare.  I’m sure many of us could solve this but Asobo won’t let us have access to the aircraft.  Furthermore we shouldn’t be solving issues with the core sim we should be focused on third party content, that’s Asobo’s job.

I’ll say this if Asobo doesn’t fix what was working prior to 1.9 in the next patch I’m going to corporate about this in Seattle.  My wife works for Microsoft and we know more than a few people there that can get eyes on this.  You can’t charge extra for the Deluxe version and continue to sideline customers.  Either give us the ability to fix it or fix it yourself. Get QA on board to test before killing everyone’s sim, allow us the ability like Windows to choose when we want to apply a patch and/or roll back a patch. We understand growing pains but this is ridicules.  

Edited October 10, 2020 by Dillon

[LarryD 132]

18 minutes ago, Dillon said:

I’ll say this if Asobo doesn’t fix what was working prior to 1.9 in the next patch I’m going to corporate about this in Seattle.  My wife works for Microsoft and we know more than a few people there to get eyes on this.  

Dillon, I know these issues are an irritation, but do you have any idea how announcing to the world that YOU ARE GOING TO CORPORATE to resolve these issues actually sounds?

And what, you think that the billion dollar company is going to say in the board meeting, "Dillon has a problem with our flight simulator, so we need to change course.  Cancel vacations and priorities and get this fixed"

Having said that, when you go, can you please tell them that I cut my lawn the other day, but it still looks uncut when I fly over in the simulator.  That is unacceptable!

[Dominique_K 10,152]

55 minutes ago, HiFlyer said:

Yet this very thread is essentially mobilizing troops to go to the front, and suddenly everything is fine....

And when everybody gathered to push for track IR,  suddenly mobilizing troops was also A-OK.

And encouraging people to vote for their favorite Sims in the navigraph survey? Fine.

These different standards are seen and noted, here and in other places.

 

🤣

Come on man, you will get your VR before the end of the year, smile ! Also note that I spoke of a VR army, where I could have said battalion if not platoon 😈 😋 !

Edited October 10, 2020 by Dominique_K

[leprechaunlive 1,861]

37 minutes ago, Dillon said:

Jim take a break from the TBM and try taking the Longitude up to 40,000ft. You’ll see the problem.  It’s universal to all users.  Asobo made a change to the sim’s FDE (reported as an update in the last patch) and now an adjustment needs to be made to some models.  Bottom line is some of us paid for the Premium aircraft and that decision has been a nightmare.  I’m sure many of us could solve this but Asobo won’t let us have access to the aircraft.  Furthermore we shouldn’t be solving issues with the core sim we should be focused on third party content, that’s Asobo’s job.

I’ll say this if Asobo doesn’t fix what was working prior to 1.9 in the next patch I’m going to corporate about this in Seattle.  My wife works for Microsoft and we know more than a few people there that can get eyes on this.  You can’t charge extra for the Deluxe version and continue to sideline customers.  Either give us the ability to fix it or fix it yourself. Get QA on board to test before killing everyone’s sim, allow us the ability like Windows to choose when we want to apply a patch and/or roll back a patch. We understand growing pains but this is ridicules.  

Geez, instead of that tell your wife to give you a massage, you'r overstressed my friend.

[FrankR409 514]

4 minutes ago, LarryD said:

Dillon, I know these issues are an irritation, but do you have any idea how announcing to the world that YOU ARE GOING TO CORPORATE to resolve these issues actually sounds?

And what, you think that the billion dollar company is going to say in the board meeting, "Dillon has a problem with our flight simulator, so we need to change course.  Cancel vacations and priorities and get this fixed"

Having said that, when you go, can you please tell them that I cut my lawn the other day, but it still looks uncut when I fly over in the simulator.  That is unacceptable!

The patition and the petition are already locked by MS, so this is a moot point.  It is already in the planned work load.  
 

As a MS shareholder, I will voice my opinion at The annual shareholders meeting on December 2, 2020.

[Adrian123 1,015]

Just now, FrankR409 said:

As a MS shareholder, I will voice my opinion at The annual shareholders meeting on December 2, 2020

Wow, they'll have a Company crisis with stocks plummeting. 🙂

[Dillon 2,198]

3 minutes ago, LarryD said:

Dillon, I know these issues are an irritation, but do you have any idea how announcing to the world that YOU ARE GOING TO CORPORATE to resolve these issues actually sounds?

And what, you think that the billion dollar company is going to say in the board meeting, "Dillon has a problem with our flight simulator, so we need to change course.  Cancel vacations and priorities and get this fixed"

Having said that, when you go, can you please tell them that I cut my lawn the other day, but it still looks uncut when I fly over in the simulator.  That is unacceptable!

Totally understand but there is a quality control department that handles software issues and Microsoft’s relations with their partners.  I’ve met a few of them and they’ll put bugs in certain people’s ear to look at how this product is doing, check forums, problem reports from users, and resolution turn around times.  Microsoft isn’t giving Asobo a blank check here as this could be another FLIGHT which is something we all don’t want.  Supporting this effort goes beyond using the sim we can’t be a door mate either.  These kinds of issues turn people away and with that the customer volume hence no reason to keep FS scenery servers. We have to hold Asobo to the fire because this would be a disaster down the road when the likes of PMDG and other advanced add-ones get developed and someone at Asobo changes something to break the thing that makes our add-ons work with Asobo telling us they’ll get to it down the road maybe a few months.  That’s unacceptable and it’s best we deal with this now... 

I’ll tell them about your lawn, it’s most likely a Bing issue...

[fppilot 4,391]

12 hours ago, bean_sprout said:

@Dillon - get over yourself.    As I said before pushing and nagging isn't going to solve things any quicker.  Let the team address this and back off.  If you were part of the development process I wouldn't be saying this but you are out of line IMO.

Regards

bs

And perhaps, just perhaps, you might come down off your high beanstalk..  Others are not getting personal.  Please follow suit.

[JRBarrett 3,121]

40 minutes ago, Dillon said:

Jim take a break from the TBM and try taking the Longitude up to 40,000ft. You’ll see the problem.  It’s universal to all users.

I’ve never flown the Longitude either pre or post patch, and if the problem was specific only to that model, I would suspect that it is an error in the flight dynamics of that one aircraft.

I specified the TBM, because many reports of the “dolphin dance” are by users of that specific aircraft, who never had the problem prior to the patch, but now do.

Something obviously changed in the patch to cause this issue but it does not affect all users. I can’t duplicate this bug on the TBM and I have tried very hard to deliberately provoke it - for others, it happens on every flight.

The Longitude, from what I have read, has always had a very poor flight model, and very poor system functionality. The TBM, by contrast has been noted as being one of the more stable and reliable aircraft in the current MSFS fleet. I have certainly found that to be the case. If an aircraft that has consistently performed well in the past suddenly manifests a bug after a new patch for some users, then those having the problem need to submit a report to Zendesk, with as much detail as possible, and focusing on an aircraft that worked well previously.

[LarryD 132]

16 minutes ago, Dillon said:

Microsoft isn’t giving Asobo a blank check here ....

More seriously this time.

Isn't Jorg Neuman a Microsoft bigwig and already running the entire show for Microsoft as far as the simulator?  He and Seb from Asobo are giving regular live updates and taking questions.  So no, they are not giving Asobo a blank check here and they are involved in all the decision making.  Is that not correct?  Don't you think that they have regular meetings discussing about how to proceed and this is what they came up with?

We all know everyone has different priorities to be fixed out here in userland.  For now, we just have to be patient.

Edited October 10, 2020 by LarryD

[Manny 1,293]

14 hours ago, bean_sprout said:

Garmin is going to be doing the Garmin code so give them time to get ramped up.  

Push all you want but it won't speed up the process.

 

Regards

bs

Any links to this news please?

thx

Edited to add: I see others were excited like I was and later realized this is not true. I too watched the interview and heard that either. Sigh!

Manny

Edited October 10, 2020 by Manny