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.

Go-Flight MCP Pro stuck on 99000 ft

David_BeckettDavid_Beckett
in GoFlight Interface Tool - Technical Support
Go-Flight MCP Pro stuck on 99000 ft on certain aircraft since the new update 6 in MSFS, those planes are

DA62.
Cirrus SR22
Textron Aviation Beechcraft Baron G58
" " " Bonanza
" " Cessna 208B Grand Caravan
" " Cessna 172 Skyhawks (all of the variations)
Cub Crafter X cub

Anyone else using Go Flight MCP suffering this problem?

Comments

  • David_BeckettDavid_Beckett
    The new GIT update on Wednesday the 8th didn't improve it at all. None of the aircraft listed in the above post work properly using the Go-Flight MCP. Problem is not down to GIT but it is the new update 6 is the cause.

  • David_BeckettDavid_Beckett
    Apparently it is a change to the SDK whatever that means.
  • David_BeckettDavid_Beckett
    If it helps, most of if not nearly all the default aircraft suffer with the altitude frozen on 99000 feet and some of the heavy aircraft the Auto pilot won't turn on at all.
  • admin_ppsadmin_pps
    edited September 2021
    I have just tested the DA62 and it works fine for me. They don't seem to have changed anything. Try setting Default FS again, in case the config has been accidently changed.

    It also be worth checking your MCP is broken. I have a copy of GoFlights test program here: https://1drv.ms/u/s!AvmOqBMETlayh9ZQKy3urkyHuWeNEw?e=aLKfs1

    Best wishes
    Steve
  • David_BeckettDavid_Beckett
    I've now discovered three other people all suffering with the addon autopilot
  • David_BeckettDavid_Beckett
    What do you mean by "Default FS"?
  • admin_ppsadmin_pps
    On the MCP tab, click the FS Default button to configure it.

    To be clear, I'm using the latest version of MSFS with the latest GIT and GIT WASM module.

    I wonder if the MSFS update didn't install properly for you and messed things up.

    I also tested the DA62 with my forthcoming new software and it all worked OK as well.

    It has to be something gone wrong on your PC, or your MCP is playing up.

    Best wishes
    Steve
  • David_BeckettDavid_Beckett
    Nothing wrong with the MCP as it works on most payware aircraft.
  • David_BeckettDavid_Beckett
    I've download both GIT and WASM several times. No change :(
  • David_BeckettDavid_Beckett
    Is it worth deleting MSFA and reinstalling from new again?
  • SteveGreenspanSteveGreenspan
    Just from a another perspective, I have not seen this occur after update to MSFS with WU6, and the latest versions of GIT and the WASM module. The MCPPro and EFIS are both working for me on the FBW A320NX and on the default Cessna 172 (standard gauges) and Cessna 152. The baro (EFIS) and course and heading (MCPPro) knobs work and display correctly.
  • David_BeckettDavid_Beckett
    Yes nothing wrong with the heading it's just the altimeter is stuck or rather frozen on 99000 ft
  • David_BeckettDavid_Beckett
    Another three people three people with the same problem, I think that is six or seven people suffering the same as me. :(
  • admin_ppsadmin_pps
    Ok, just googled it and someone has supplied an answer. It depends upon the config of the aircraft which is why I didn't see it on my test. Change the altitude to use this variable instead: AUTOPILOT_ALTITUDE_LOCK_VAR:1

    Best wishes
    Steve
  • David_BeckettDavid_Beckett
    Will try it. Many thanks.
    David
  • David_BeckettDavid_Beckett
    Steve I can't find the CFG with Autopilot listed, can you tell me the path, I'm assuming I start at the "Official" folder.
  • admin_ppsadmin_pps
    No, on the MCP Tab in GIT.
  • David_BeckettDavid_Beckett
    Hi sorry for the delay since you last posted to me but my computer broke and has been away to be mended. To refresh your memory I had and still have the MCP showing 99000ft your answer was to edit in GIt MCP tab "AUTOPILOT_ALTITUDE_LOCK_VAR:1 " I can't find that line. I enclose a pic showing where I'm looking, is this the correct place to loook? . Lastly how do you actually edit in GIT?
    1.jpg 50.5K
  • David_BeckettDavid_Beckett
    Sorry uploaded wrong pic, here is the correct pic.
    2.jpg 58.8K
  • admin_ppsadmin_pps


    See the high-lighted fields in the attached image. Select Device 0, then an Input of DISPLAY ALTITUDE and then change the Light/Disp Data to the required variable AUTOPILOT_ALTITUDE_LOCK_VAR1

    Best wishes
    Steve
  • David_BeckettDavid_Beckett
    It didn't work Steve, tried it on several airplanes the MCP altitude lights go out and it then totally frozen i.e. none of the controls do anything. :(
  • David_BeckettDavid_Beckett
    Fixed the 99000 ft Steve, reintalled Windows and reinstalled the Sim. But I still have a problem when booting up GIT some times it might take five minutes for the control panel to open, but more often than not it never opens. Any ideas as to what could be wrong?
    David
  • David_BeckettDavid_Beckett
    Just got GIT to open and the panel screen for Altitude shows 0 as do all the other panel screens but now none of the actual control knobs work, as if frozen. :( Two steps forward one step back :(
    David
  • SteveGreenspanSteveGreenspan
    David,
    I may have missed it, but what plane are you configuring in the GIT screenshots?

    Steve G.
  • David_BeckettDavid_Beckett
    I can't remember what aircraft were loaded when I did the screen shots, but I've tried two asobo and two payware aircraft and the
    MPC although lit up and displaying 0 on each screen, but none of the knobs will operate anything like Heading, Altitude or Course etc etc. All stay on 0. But if I go into the cockpit and change anything like set altitude or Heading the display on the MCP does change accordingly, The MCP is simply not working using it's own knobs.
  • SteveGreenspanSteveGreenspan
    OK, thanks. I'm using the FBW A320 and the Aerosoft CRJ, and for the most part, the MCP functions well with displays and knobs. That's why I'm curious to know what aircraft you are using and whether you configured any bespoke events.

    Does turning the knobs change the setting values in the simulator, such as the heading, altitude or airspeed, even though the MCP displays stay at zero?

    Do you have any bespoke events programmed in Detective to change the settings, incrementing or decrementing?

  • David_BeckettDavid_Beckett
    I'm holding my breath Steve, at this very moment it is working perfectly, the only thing I done was to update windows and reinstall a new download of your GIT. So I'm a happy chappie. Many thanks for all the quick replies and suggestion to help fix my problems.
    Dave
Sign In or Register to comment.

© Vanilla Keystone Theme 2025