Autopilot keeps disengaging NAV mode (VOR-to-VOR navigation)
-
Today I did two more flights in this wonderful little air-plane (the normally aspirated variant). I am having such a good time in it, it brings me the illusion of flying a real plane (of course I'm just an arm chair pilot).
But … I ran into something strange on both flights: I like navigating old school VOR-to-VOR so I was cruising towards a VOR station, autopilot on [alt] and [nav] and all went well. On both flights the autopilot [nav] keeps disengaging after a short time (varying from 30 seconds to just over 6 minutes during this flight) without any apparent reason. I can engage it again until it disengages by itself after a short while again.
I couldn't find a pattern, it seems to happen randomly.What I did (also see attached screen print):
cruising at 12500 and 7500 feet respectively
MX-170B NAV1 tuned into various VOR stations, in this case MEN 115.30 MHz in France and well in range (stable signal)
MD41-328 LOC SRC switch set to NAV1/GPS
TKM MC60 set to OBS mode and set to the appropriate radial (107° in this example)
S-TEC System 60-2 Autopilot engaged in [alt] and [nav]This behaviour doesn't seem normal to me, but – since I'm not a pilot and just learning to “fly” this air-plane – it is very well possible that I am overlooking something here.
Is anyone on the forum having a explanation for this?
Thanks very much for your help.
-
Today I did two more flights in this wonderful little air-plane (the normally aspirated variant). I am having such a good time in it, it brings me the illusion of flying a real plane (of course I'm just an arm chair pilot).
But … I ran into something strange on both flights: I like navigating old school VOR-to-VOR so I was cruising towards a VOR station, autopilot on [alt] and [nav] and all went well. On both flights the autopilot [nav] keeps disengaging after a short time (varying from 30 seconds to just over 6 minutes during this flight) without any apparent reason. I can engage it again until it disengages by itself after a short while again.
I couldn't find a pattern, it seems to happen randomly.What I did (also see attached screen print):
cruising at 12500 and 7500 feet respectively
MX-170B NAV1 tuned into various VOR stations, in this case MEN 115.30 MHz in France and well in range (stable signal)
MD41-328 LOC SRC switch set to NAV1/GPS
TKM MC60 set to OBS mode and set to the appropriate radial (107° in this example)
S-TEC System 60-2 Autopilot engaged in [alt] and [nav]This behaviour doesn't seem normal to me, but – since I'm not a pilot and just learning to “fly” this air-plane – it is very well possible that I am overlooking something here.
Is anyone on the forum having a explanation for this?
Thanks very much for your help.
@HansDeVlieger I know this is an issue people have posted with other planes. If it makes you feel any better, NAV mode has proven to be not so reliable to me IRL so I never use it personally, especially with VOR navigation due to signal sensitivity... I believe the issue occurs due to a temporary signal loss for some reason, tho I cannot see how black square aircraft would have any issues that default planes wouldn't...
My best recommendation is use hdg hold and make small course adjustments every once and a while to stay on course. Just like you would do IRL...
-
Today I did two more flights in this wonderful little air-plane (the normally aspirated variant). I am having such a good time in it, it brings me the illusion of flying a real plane (of course I'm just an arm chair pilot).
But … I ran into something strange on both flights: I like navigating old school VOR-to-VOR so I was cruising towards a VOR station, autopilot on [alt] and [nav] and all went well. On both flights the autopilot [nav] keeps disengaging after a short time (varying from 30 seconds to just over 6 minutes during this flight) without any apparent reason. I can engage it again until it disengages by itself after a short while again.
I couldn't find a pattern, it seems to happen randomly.What I did (also see attached screen print):
cruising at 12500 and 7500 feet respectively
MX-170B NAV1 tuned into various VOR stations, in this case MEN 115.30 MHz in France and well in range (stable signal)
MD41-328 LOC SRC switch set to NAV1/GPS
TKM MC60 set to OBS mode and set to the appropriate radial (107° in this example)
S-TEC System 60-2 Autopilot engaged in [alt] and [nav]This behaviour doesn't seem normal to me, but – since I'm not a pilot and just learning to “fly” this air-plane – it is very well possible that I am overlooking something here.
Is anyone on the forum having a explanation for this?
Thanks very much for your help.
@HansDeVlieger So far, the only plausible explanation I have seen for this is that some third party applications like FSUIPC are polling the variables and somehow causing it to disconnect. I do not believe there is any setting in my aircraft that could, or should, be causing this. I have seen posts on the official forum about this with other developer's aircraft too, but none of them have gained traction with Asobo. Unfortunately, I have never experienced this myself, so I'm not sure what troubleshooting I can do, or what that tells us about the problem.
-
I am experiencing this issue as well. NAV gets disabled without me noticing so many times I discover it after a few minutes. I do not use FSUIPC, but I do use SPAD.next which polls the nav variable in order to light up the NAV button of my Logitech flight panel.
-
@HansDeVlieger I know this is an issue people have posted with other planes. If it makes you feel any better, NAV mode has proven to be not so reliable to me IRL so I never use it personally, especially with VOR navigation due to signal sensitivity... I believe the issue occurs due to a temporary signal loss for some reason, tho I cannot see how black square aircraft would have any issues that default planes wouldn't...
My best recommendation is use hdg hold and make small course adjustments every once and a while to stay on course. Just like you would do IRL...
@SadBucket
Thanks for your real life insight. I guess the signal quality in general depends also on the place on the planet that your flying in (geographically for example). I know and experience this feature in Black Square's aircraft that mimic signal degradation which adds greatly to the immersion. It's this attention to detail that make me appreciate Black Square aircraft so much. So yes, I do use hdg hold already when it comes to switching between VOR stations that are not that dense in comparison to the earlier days. And of course when crossing a station to pick up a outbound radial later on. I guess that I'm going to follow your suggestion when the problem persists. I pretend that it's all about realism
-
@HansDeVlieger So far, the only plausible explanation I have seen for this is that some third party applications like FSUIPC are polling the variables and somehow causing it to disconnect. I do not believe there is any setting in my aircraft that could, or should, be causing this. I have seen posts on the official forum about this with other developer's aircraft too, but none of them have gained traction with Asobo. Unfortunately, I have never experienced this myself, so I'm not sure what troubleshooting I can do, or what that tells us about the problem.
@Black-Square
Thanks again for taking the time to take a look at my issue.
I'm afraid I don't know an awful lot about the magic behind the interacting between add-on airplanes and the simulator, but I understand what you're saying. I don't use FSUICP but use SPAD.neXt instead to manage my hardware. In this case I use the Honeycomb Bravo's autopilot feature.I must say this is the first time I run into this. I have a fair collection of Black Square aircraft and I don't recall I saw any disconnection issue before. I am not sure about the Dukes and Starship but I did quite a lot of hours in the TBM 850 and the Bonanzas.
What I will do is empty my Community folder except for the Commander 114 and do a test flight without SPAD.neXt or any other program running besides MSFS2024. Then I'll do a flight with my "normal" setup in one of the Bonanzas to see whether it occurs or not. After that, I'll report back. -
I am experiencing this issue as well. NAV gets disabled without me noticing so many times I discover it after a few minutes. I do not use FSUIPC, but I do use SPAD.next which polls the nav variable in order to light up the NAV button of my Logitech flight panel.
@Voxen
Do you experience the issue only in this aircraft or also in others? -
@Black-Square
Thanks again for taking the time to take a look at my issue.
I'm afraid I don't know an awful lot about the magic behind the interacting between add-on airplanes and the simulator, but I understand what you're saying. I don't use FSUICP but use SPAD.neXt instead to manage my hardware. In this case I use the Honeycomb Bravo's autopilot feature.I must say this is the first time I run into this. I have a fair collection of Black Square aircraft and I don't recall I saw any disconnection issue before. I am not sure about the Dukes and Starship but I did quite a lot of hours in the TBM 850 and the Bonanzas.
What I will do is empty my Community folder except for the Commander 114 and do a test flight without SPAD.neXt or any other program running besides MSFS2024. Then I'll do a flight with my "normal" setup in one of the Bonanzas to see whether it occurs or not. After that, I'll report back.@HansDeVlieger said in Autopilot keeps disengaging NAV mode (VOR-to-VOR navigation):
What I will do is empty my Community folder except for the Commander 114 and do a test flight without SPAD.neXt or any other program running besides MSFS2024. Then I'll do a flight with my "normal" setup in one of the Bonanzas to see whether it occurs or not. After that, I'll report back.
This will be greatly appreciated! Unfortunately, I think this is going to be a deep simulator level issue, but I've found that unless we can really pinpoint the issue, bug reports are likely to be sidelined. I will really appreciate even one more data point!
-
@Voxen
Do you experience the issue only in this aircraft or also in others?@HansDeVlieger said in Autopilot keeps disengaging NAV mode (VOR-to-VOR navigation):
@Voxen
Do you experience the issue only in this aircraft or also in others?I don't recall having seen this issue before, but lately I flew only the A2A Comanche that does not have a NAV button.
