Autopilot keeps disengaging NAV mode (VOR-to-VOR navigation)
-
Maybe this post is important. SU6 solve this issue perhaps.
https://forums.flightsimulator.com/t/vor-range-often-incorrect/406277/85
@SebAvi That might very well be related. Let's hope so. Thanks for the heads up.
-
Doesn't seem related at all, but maybe they will fix something in the code by mistake when adding/fixing those longer range VOR stations
In general I'm not sure if Asobo is even aware (and how it was described to them). There was a longer discussion on this topic in the Aircraft section of the official forums. But the only report I have seen was a user trying to report it and the answer from the mod was that this doesn't qualify as a report in this form. Not sure if the user re-tried in another form.
-
What I don't know is if developers have a feedback channel with Asobo where they can report the issue. After all they are the ones who get the feedback from their users / customers (questioning their product, not me btw
). Maybe Nick can comment on this. -
Found the report I was writing about.
Commendable effort on the side of the user, but I think he gave up in the end
https://forums.flightsimulator.com/t/bug-multiple-planes-change-from-nav-to-rol-hdg-mode-when-tracking-vor/762974/10
BTW. It not happening for me in the F28 and Bae146 might be suggesting that it's about the standard AP units. Both planes are larger and have the AP functions spread over the cockpit, with probably some custom coding involved to make it happen - and not just a standard AP panel.- decided to withdraw the conclusion as I just realized the 114 also has a custom AP panel and it also happened with the StarshipEither way, have some examples from YT (link should point to the specific moment):
https://youtu.be/1a-g3UMooCs?t=4393
On glideslope for some time now, clear view of the runway, APR randomly moves back to ROLL (the popped breaker is not about this, it's an icing sensor and was known).
Here a similar situation:
https://youtu.be/300F3IcCAqM?t=3593The same, but with only a localizer.
Normally it happens with VORs, was just easier to remember and find those two.
-
Found the report I was writing about.
Commendable effort on the side of the user, but I think he gave up in the end
https://forums.flightsimulator.com/t/bug-multiple-planes-change-from-nav-to-rol-hdg-mode-when-tracking-vor/762974/10
BTW. It not happening for me in the F28 and Bae146 might be suggesting that it's about the standard AP units. Both planes are larger and have the AP functions spread over the cockpit, with probably some custom coding involved to make it happen - and not just a standard AP panel.- decided to withdraw the conclusion as I just realized the 114 also has a custom AP panel and it also happened with the StarshipEither way, have some examples from YT (link should point to the specific moment):
https://youtu.be/1a-g3UMooCs?t=4393
On glideslope for some time now, clear view of the runway, APR randomly moves back to ROLL (the popped breaker is not about this, it's an icing sensor and was known).
Here a similar situation:
https://youtu.be/300F3IcCAqM?t=3593The same, but with only a localizer.
Normally it happens with VORs, was just easier to remember and find those two.
-
Yep, that was my original post in the MSFS forums about this issue, and yes I've just lived with this for some months.
I am also getting this behavior in the Commander.I have a workaround I've set up in multiple planes with some Spad.Next trickery, where I can activate/deactivate monitoring for when Nav mode is lost. When that happens, it quickly turns it back on again. It works pretty well.
Ironically, it seemed that if I didn't have SPad.next running, this problem didn't happen in the first place. It makes me think that Spad simply listening or polling certain variables might be causing this, but it would take some deep debugging to troubleshoot this.
Feel free to add observations to that thread for visibility to Asobo. I'm doing a VOR tour of Alaska in the Commander (before it gets too cold/icy for this plane), so maybe I'll experiment a bit this weekend.
-
Yep, that was my original post in the MSFS forums about this issue, and yes I've just lived with this for some months.
I am also getting this behavior in the Commander.I have a workaround I've set up in multiple planes with some Spad.Next trickery, where I can activate/deactivate monitoring for when Nav mode is lost. When that happens, it quickly turns it back on again. It works pretty well.
Ironically, it seemed that if I didn't have SPad.next running, this problem didn't happen in the first place. It makes me think that Spad simply listening or polling certain variables might be causing this, but it would take some deep debugging to troubleshoot this.
Feel free to add observations to that thread for visibility to Asobo. I'm doing a VOR tour of Alaska in the Commander (before it gets too cold/icy for this plane), so maybe I'll experiment a bit this weekend.
@SteveKane Thanks for the tip I must try your SPAD.neXt trick.
BTW, in my attempt to isolate the cause, I tested several scenarios that I described in my earlier post (see above). In the first scenario SPAD.neXt was not running, so I think this is not related. -
@SteveKane Thanks for the tip I must try your SPAD.neXt trick.
BTW, in my attempt to isolate the cause, I tested several scenarios that I described in my earlier post (see above). In the first scenario SPAD.neXt was not running, so I think this is not related.@HansDeVlieger said in Autopilot keeps disengaging NAV mode (VOR-to-VOR navigation):
@SteveKane Thanks for the tip I must try your SPAD.neXt trick.
BTW, in my attempt to isolate the cause, I tested several scenarios that I described in my earlier post (see above). In the first scenario SPAD.neXt was not running, so I think this is not related.Can confirm, never had SPAD installed and I don't have it now
I'm wondering if it's really a very small subset of users experiencing it or if the rest just thinks this is intended behavior and accepts it.
-
@HansDeVlieger said in Autopilot keeps disengaging NAV mode (VOR-to-VOR navigation):
@SteveKane Thanks for the tip I must try your SPAD.neXt trick.
BTW, in my attempt to isolate the cause, I tested several scenarios that I described in my earlier post (see above). In the first scenario SPAD.neXt was not running, so I think this is not related.Can confirm, never had SPAD installed and I don't have it now
I'm wondering if it's really a very small subset of users experiencing it or if the rest just thinks this is intended behavior and accepts it.
@Tadeus72 I'll devote my final weekend flight tonight to test a flight without SPAD and see what happens. IIRC, even running SPAD early in the flight and killing it still had the disconnect behavior, so I'll start the sim afresh with no Spad running. (gonna be weird to "mouse" everything, lol).
Stay tuned!