BUG: Multiple planes change from NAV to ROL/HDG mode when tracking VOR

Description of the issue:

Executive summary: Many (all?) Black Square aircraft (Dukes, Caravan Pro, Baron/Bonanza Pro, Starship), the Milviz/Blackbird C310a, and perhaps other aircraft have an issue where when tracking a VOR, the autopilot spontaneously changes from NAV mode to ROL mode at intervals ranging from 30 seconds to several minutes. This occurs independently of the distance from the VOR, including within a few miles. I can hit NAV to get back on track, but it still reverts to ROL mode eventually. I believe I’ve also seen this when tracking an ILS. (Note that the Duke reverts to HDG mode, as it does not have a ROL mode.)

Other Factoids:
-This occurs whether using just old-school avionics, or the TDS GTNXi when in VLOC mode.
-GPS Mode is not affected, only VOR.
-KEY ITEM: Most interestingly, myself and others who have reported this in other posts all have either SPAD.Next, FSUIPC, or other third-party control mapping software running. If I don’t use SPAD in a flight and simply use my mouse to control the autopilot and everything else, this behavior does not occur. Furthermore, one user who reports this doesn’t have any control mappings whatsoever, and only uses FSUIPC to connect their Virtual Airline client to the sim.
-I originally thought it was specifically Black Square aircraft, but it’s also observed in the Blackbird C310. I might try some other planes like the C414 to further repro.

Template answers below, but the above pretty much explains it all.

I’ll tag affected users and reference various threads here an in the JustFlight BKSQ Forum in a child post.

FREQUENCY OF ISSUE

How often does this occur for you: Every flight with the repro steps below.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Prior to starting the flight, launch FSUIPC or SPAD.NExt (or maybe Axes and Ohs).
  2. Start flight in the BKSQ aircraft listed above or BB C310, and track any VOR in autopilot NAV mode. I’ve tested on a flight from PAKT to PAWG using the Level Island VOR (116.5), but have reproduced this in other US areas like SoCal.
  3. Keep flying, and watch for the autopilot to change from NAV to ROL (or HDG in the Duke).
  4. Reengage NAV, and it still will change back to ROL/HDG eventually.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:

[PC Only] Are you using Developer Mode or have you made any changes to it? NO

[PC, MSFS 2020 Only] Are you using DX11 or DX12? DX12

[PC Only] What GPU (Graphics Card) do you use?

[PC Only] What other relevant PC specs can you share?

MEDIA

Please add a screenshot or video of the issue occurring.
Will eventually create a YT video to demo.

Just flight forum threads:
NAV mode keeps changing to ROL with Non-GPS Avionics | Just Flight Community
Autopilot goes from VOR to ROLL when tracking VOR | Just Flight Community

Baron/Bonanza Thread (with multiple responses)

Separate thread:
NAV and Approach modes being randomly disconnected - User Support Hub / Aircraft & Systems - Microsoft Flight Simulator Forums

Tagging some interested folks:
@PhonedGorgon897
@kaha300d

Hi @SteveKane ,

Thank you for this report. We’ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.

If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.

If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.

All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.

I’ll add that the cause/responsibility is rather gray on this bug. It involves third-party aircraft from at least two different developers (Black Square and Blackbird), control mapping products from at least two devs (Spad and FSUIPC), and of course FS2024.

My goal before the end of the coming weekend is to see if I can repro this in an Asobo aircraft with just FSUIPC running, no control mappings.

If you can replicate the issue with 1st party aircraft but using FSUIPC, I would recommend to report it to the developers of this tool. If they identify an issue on FS2024 side, then they need to report it to Asobo through the dedicated SDK support forums.
The Bug Reporting Hub is only to report issues with the base sim & 1st party contents, without using 3rd party addons/mods.

Just a datapoint for you:

Replicated your flight from PAKT-LVD-PAWG using Nav only in the BKSQ Bonanza Pro with Spad running the autopilot (I dont use FSUIPC). I picked up the VOR a couple of miles out from PAWG, switched NAV on and started following it out. The AP NAV switched off at c.20 NM out from PAWG, but the HSI and DME were still tracking the beacon.

Repeated the flight in the same session with default 172 (G1000) tracking the VOR only (no GPS used) and using Spad for AP controls. No problem with the AP NAV on that flight.

Just want to chime in that I’m also seeing this behavior while flying the Black Square Bonanza NAV/COMs only, however I’m not using nor have I installed any control mapping software. I have the Baron as well but haven’t flown it so I’ll give that a test when I have some time.

Very interesting! Thanks for the data point.