Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.

MCP Advanced, help requested for light data for Nav button - Xplane Default C172

I was able to get MCP advanced (not Pro) Nav button to work ( I think ) for the default Xplane 11 C172 (steam gauge) autopilot . However, I can't seem to get the Nav light on the MCP to work properly. Would anyone have suggested light data value settings?
Many thanks! - Bentley

Comments

  • Try sim/cockpit2/autopilot/nav_status with ON at a value of 1.

    Best wishes
    Steve
  • edited March 2020
    thanks Steve,
    so here's my issue - doesn't come on with Value of 1, but with some experimentation, does come on with a value of 2. The problem is, the Nav button actually cycles Nav and Nav GPSS modes. I have this part working and mimics the Nav button in the sim. However, with repeat Nav button presses, it will cycle the Nav light, even though the autopilot (in sim) remains in Nav mode- alternating Nav and Nav GPSS- hope that makes sense. There may not be an easy way to fix this, but thought I would put out there.

    Appreciate your help!
    Bentley
  • According to this https://developer.x-plane.com/datarefs/ there is also gpss_status, so you could create a bespoke event called Start that looks at the state of these two datarefs to determine if the light is on, then set a bespoke variable to either 1 or 0 and assign that to the NAV light.

    Start bespoke events run automatically when the plane loads, so the bespoke variable will always be up to date. Make sure you add a Sleep(500) in the bespoke event otherwise your CPU usage will go to 100%

    You can do the same thing in Lua if you prefer.

    Best wishes
    Steve
  • thank you for the suggestions.
    Bentley
Sign In or Register to comment.