Autopilot keeps disengaging NAV mode (VOR-to-VOR navigation)
-
Interesting, as I've seen this behavior in I think all BKSQ aircraft, including the Commander.
I've got a couple of scenarios I want to try tonight:
-Try using the RNAV receiver with distance = 0.
-Start with SPAD, track VOR, wait for it to disconnect once, then kill SPAD and see what happens. (I think I've tried that before, and the disconnects continued, but that was months ago.) -
@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 Hans, I read your post and wondered if you have tried using ‘empty” hardware control profiles in MSFS to find the problem, not just an empty Community folder?
I had a related problem with the Honeycomb Bravo where commands pre-assigned to the default Honeycomb Bravo controller profile conflicted with a command that I was trying to assign in Axis and Ohs (similar keyboard software to Spad.next).
Once I created an empty hardware profile for the Honeycomb Bravo, my problems disappeared. After that I was able to add commands back in step by step. I only mention this as the Bravo fires commands constantly and the default Bravo profile contains commands for all of the autopilot controls and something there could potentially by causing your problem.
I could also be completely wrong but wanted to let you know my experience and how I solved it, in case it helps you too.
-
I tested as follows: used Spad, climbed to 11000 feet. It took a while, but finally got a disconnect. Turned off Spad, eventually got another. It seems at higher altitudes, there are much longer intervals between disconnects than my current flight at 6000 feet, have had six disconnects in about 12 minutes all with SPAD. I'm using SPAD to output a voice when it runs my auto-reset to NAV mode code. (In fact, as I type, it's now up to 11 instances.)
Anyone else note a correlation between cruise altitude and disconnect rates?
-
@HansDeVlieger Hans, I read your post and wondered if you have tried using ‘empty” hardware control profiles in MSFS to find the problem, not just an empty Community folder?
I had a related problem with the Honeycomb Bravo where commands pre-assigned to the default Honeycomb Bravo controller profile conflicted with a command that I was trying to assign in Axis and Ohs (similar keyboard software to Spad.next).
Once I created an empty hardware profile for the Honeycomb Bravo, my problems disappeared. After that I was able to add commands back in step by step. I only mention this as the Bravo fires commands constantly and the default Bravo profile contains commands for all of the autopilot controls and something there could potentially by causing your problem.
I could also be completely wrong but wanted to let you know my experience and how I solved it, in case it helps you too.
@toby23 Thanks for joining.
Yes, I empty any MSFS hardware profile for the Honeycomb Bravo with any new aircraft as I use SPAD.neXt (only exception: for some aircraft I use the standard axes bindings). Conflicting bindings are very often the root cause of strange behaviour of the sim, so I agree with you to look for those first. -
I tried using the RNAV receiver, tuned to a 0 distance so essentially VOR mode, never had any disconnects for an hour long flight.
@SteveKane That sounds very interesting. Not only as a work-around but it could also point into the direction of isolating the cause of this. I'll try to confirm this later today.
-
I tried using the RNAV receiver, tuned to a 0 distance so essentially VOR mode, never had any disconnects for an hour long flight.
@SteveKane said in Autopilot keeps disengaging NAV mode (VOR-to-VOR navigation):
I tried using the RNAV receiver, tuned to a 0 distance so essentially VOR mode, never had any disconnects for an hour long flight.
Yes, I can confirm that. With RNAV receiver I never had problems.
And for me, it does not seem to be altitude depend, but I didn't actually test that. -
@SteveKane That sounds very interesting. Not only as a work-around but it could also point into the direction of isolating the cause of this. I'll try to confirm this later today.
@HansDeVlieger said in Autopilot keeps disengaging NAV mode (VOR-to-VOR navigation):
@SteveKane That sounds very interesting. Not only as a work-around but it could also point into the direction of isolating the cause of this. I'll try to confirm this later today.
Yes, a good work-around, though not for aircraft that don't have RNAV. Like the PMDG DC-6.
-
@HansDeVlieger said in Autopilot keeps disengaging NAV mode (VOR-to-VOR navigation):
@SteveKane That sounds very interesting. Not only as a work-around but it could also point into the direction of isolating the cause of this. I'll try to confirm this later today.
Yes, a good work-around, though not for aircraft that don't have RNAV. Like the PMDG DC-6.
@George-Curious
@SteveKane
You're right of couse about this working only for RNAV equipped airplanes (including the KLN-90B I suppose).
Well, I did some more testing again today and I can confirm the issue occurs when navigating directly to a VOR station. As soon as you switch to RNAV the AP NAV mode doesn't disengage, no matter what radial/distance you set.
I also didn't notice any difference at various altitudes. -
Hi, just a thought. When an aircraft like the Commander 114 is performing VOR signal degradation is it only doing it when the in game setting is ON (as per attached) or is it just doing its own thing? So in other words does the in game setting interfere with the Commander's own logic at all?
