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.

GIT PMDG 777X Beta Bug Reporting Thread

admin_ppsadmin_pps
edited October 2014 in GoFlight Interface Tool - Technical Support
Please report all bugs with the beta release of the Goflight Interface Tool in this thread.


Thanks
Steve
«1

Comments

  • SlayerSlayer
    edited November -1
    Thanks Steve amazing. The only "problem" which isn't really a problem at all is that with the EFIS you must set the minimums and baro rotaries in the simulation options of the aircraft to "rotary" instead of "realistic" otherwise it will not work because those are spring loaded switches not rotaries in the real thing.
    Steve McNitt
  • admin_ppsadmin_pps
    edited November -1
    Thanks for letting me know. I didn't change anything in the aircraft, its just set as defaults. I have 0 hrs in the 777 so you 777 experts need to feed back all the issues, bugs and quirks.

    Best wishes
    Steve
  • SlayerSlayer
    edited November -1
    The range selector setting checkbox on the EFIS seems to be reversed? If the box is unchecked it uses the 10-640 setting with it checked it skips some spots. 
    Steve McNitt
  • admin_ppsadmin_pps
    edited November -1
    If memory serves me right, you might have to quit and restart the interface when you change that setting.
  • AWE2502AWE2502
    edited November -1
    Steve,
    On the MCPpro every knob turn causes the numbers to increase or decrease by 5. So if my headings is 360 and I turn slowly the heading knob clockwise it goes to 005, next turn will be 010. Same with counter-clockwise, and same for all knob functions. Also rapid turn causes a multiple of 5, either direction.
    Also I can get the lights to work with the toggle T8, but I can not get any data on the light status to light up the LED. I have restarted GFIT every time I change a light setting, but still no LED function.
    Also, does the MCPpro work like the MD11, the displays do not show on the MCPpro but it will work on the 777 MCP? If that is correct, then nothing, if not, then the displays on the MCPpro only show 000 but work the MCP on the 777. However it works as listed above.

    Thank you for all your work on this..
    Terry
  • admin_ppsadmin_pps
    edited November -1

    Hi Terry,

    Is GFConfig configured so that the MCP PRO is set to compatible add-on? Can you also confirm you are using the beta and not an old version off the main product page.

    Thx

    Steve

  • AWE2502AWE2502
    edited November -1
    Yes to both, I downloaded the beta, should I have removed the old one, before I downloaded the beta?
    The beta seems to have merged with the last GFIT whan I downloaded it, should that not be?
    The first thing I did when I created a 777 profile in the GF software was to make sure the MCPpro was set to compatible add-on.

    Terry
     
  • admin_ppsadmin_pps
    edited September 2014
    In Slayers post above he notes that some dials can be configured in the fmc between realistic and rotary. I wonder if you have changed things from the default settings?

    You also need the very latest patch from PMDG as this fixed the SDK.

    Best wishes
    Steve
  • AWE2502AWE2502
    edited November -1
    I did change the dials from realistic to rotary with no change to the way the MCPpro reacts. The knobs still change the number by 5. I have not touched the 777 because I have been waiting for the GFIT to work with it..So everything is default except for the rotaries which I changed. The knobs on the EFIS work properly just not the ones on the MCPpro.

    Also any idea on how to get the leds to indicate the state of the landing lights and other lights. I tried the same as the MD11 and the 737 and nothing works the LEDS. The switch works T* toggle works the lights just not showing the light on status with the LED. I have tried all the combos in the light state and nothing.

    I will try the updated SDK that I have not downloaded yet.

    Terry
  • admin_ppsadmin_pps
    edited November -1
    Hi Terry,

    You must install the 777 service pack SP1b from PMDG.

    I set the LGT up with standard simconnect variables as the SDK does not provide gear status data as it did with the NGX. If that doesn't work, people will have to complain to PMDG to add support for it.

    Best wishes
    Steve
  • AWE2502AWE2502
    edited November -1
    Okay I will try that...I also noticed that when I installed the Beta, it erased all my saved GF variables. So my PMDG 737 and MD11 no longer had any thing that I saved such as taxi and landing lights, strobes and nav lights. All we gone. I did save copies before I down loaded so I was and to get them back. Is there a proper way to install the beta?
    I understand the gear position light will not work but does the landing light indicator and taxi and nav indicator work?

    Sorry for all the questions
    Terry
  • admin_ppsadmin_pps
    edited November -1
    If your saved configs got deleted, then you have found a bug. 

    Yes, the other lights should work. I'll double check tomorrow at my end - it could be something broke whilst tweaking the code.

    Best wishes
    Steve
  • AWE2502AWE2502
    edited November -1
    Yes all my set variables, the ones I made such as taxi lights and nav lights and other button and switches were gone.. Anything that had to do with the major hardware such as the EFIS and MCPpro and throttles all worked still. I hope that makes sense?
    I just copies the saved items back into the c:goflight/"anything" goflight interface module and the go flight Interface tool folder in the document section. That returned all my settings back. Should I roll the beta driver back to the original driver I had, which was the last goflight driver you had out?

    Terry
  • admin_ppsadmin_pps
    edited November -1
    If you keep losing your settings then yes wait for me to fix the bug.

    Best wishes
    Steve

  • admin_ppsadmin_pps
    edited November -1

    Hi Terry,

    I have managed to recreate the 5 increment problem. Its to do with control acceleration in the sim. The NGX handled it automatically, but the 777 doesn't. I'll get an updated version out in a couple of hrs.

    Best wishes

    Steve

  • admin_ppsadmin_pps
    edited November -1
    Hi Terry,

    I have just checked the taxi lights and the light works for me.

    I used DATA_OH_LTS_SWITCH_TAXI, ON, 1

    Best wishes
    Steve
  • admin_ppsadmin_pps
    edited November -1

    New version released:

    https://www.dropbox.com/s/8urlhmxmy0zj1in/Goflight%20Interface%20Tool%202-1-1-0.zip?dl=0

  • AWE2502AWE2502
    edited November -1
    That new BETA works...the MCPpro works as does the EFIS and I have programmed some light buttons...However, the program erased all my buttons I programmed for mt PMDG MD11 and 737NGX. Not sure if there a way just to import those buttons into the new BETA. I saved the old data so I can go back to using the buttons with the 737NGX, however when I do that it removes all the data for the 777. All data is gone buttons programmed and MCPpro and EFIS also do not function when trying to get the MD11 and 737 buttons back.

    Terry
  • admin_ppsadmin_pps
    edited November -1
    Hi Terry,

    I have yet to look into that particular bug. I'll get a new release out ASAP.

    Best wishes
    Steve

  • SlayerSlayer
    edited November -1
    Working fine with both my NGX and T7 but I only own the MCPPro and EFIS. Profiles seem to be intact.
    Steve McNitt
  • AWE2502AWE2502
    edited November -1
    My NGX and MD11, MCPpro and EFIS worked with the with the new BETA fine. The problem i have is that the toggle switches and buttons for the T8, P8, and RP48 lose what I have programmed them to do for both the NGX and MD11.
    Terry
  • admin_ppsadmin_pps
    edited November -1
    Hi Terry,

    I'm aware of this bug and will get a release out to fix it at the weekend.

    Best wishes
    Steve
  • AWE2502AWE2502
    edited November -1
    Sorry Steve, I was answering Slayer about my MCPpro and EFIS working...I knew you were working on a fix.

    Thanks for all you do..

    Terry
  • admin_ppsadmin_pps
    edited November -1
    New release that fixes bugs in the BETA. See change log after installing for details.


    Best wishes
    Steve
  • AWE2502AWE2502
    edited October 2014
    Steve,
    It works great, all my current PMDG settings stayed with the new beta...So far I have programmed a few lights and small items.
    Suggestion. Can you create the landing light as a group function like the switches for the APU and such. The landing lights require 3 different buttons and that eats a lot of switches I would like to keep some for other items.
    THANK YOU...
    I can not find the button to donate. Since you made 3 items to work with the PMDG I would like to donate again as a way to say thank you.. (disregard I found it..Thanks for the program I will let you know on items)

    Terry
  • stopnickistopnicki
    edited November -1
    Hello everybody and hi Steve:

    A few items on my end.

    1) If Slayer (or you) could help me to set the BAROM and MINM rotaries from "realistic" to "rotary" as Slayer indicated in his first post, as all of my setting options in the EFIS are grayed out and I have the same difficulties in changing settings in these two buttons as he had.

    2) Has anybody managed to program the auto-brake function. If yes, could you share?

    3) Regarding Terry's last message, in the B777, a click of the mouse's rotary, will turn on (or off) the three light switches simultaneously. I have the same lack of switches as Terry has :-)

    Notwithstanding that I have the "10 to 640" range box clicked in the EFIS setting, it only works down to "20"

    Notwithstanding all of the above, it is a pleasure to play with the modules and the B777. 
    Great job!!
    Roberto

  • admin_ppsadmin_pps
    edited November -1
    Hi Terry,

    Yes I can do that for you. I have also put in a ticket to PMDG for them to add the gear status variables so the LGT's LED's can be driven properly.

    Many thanks for the donation.

    Best wishes
    Steve
  • admin_ppsadmin_pps
    edited November -1
    Hi Roberto,

    I can't help you with issue number 1. I suggest you raise a ticket with PMDG.

    For issue number 2, the PMDG NGX manual included with GIT shows how to do it for the NGX - the same way should work for the 777.

    3rd issue - see my response to Terry.

    As for the EFIS, when you change the tick box, GIT needs to be exited and restarted for that function to work properly. If it still doesn't let me know.

    Best wishes
    Steve
  • GnacinoGnacino
    edited November -1

    Thanks Steve.  You obviously spend more time programming so we can spend more time flying than you.  Very much appreciated.

    Gnacino

  • admin_ppsadmin_pps
    edited November -1
    Hi Gnacino,

    Sadly I no longer get any time for flying. Once I get the Sid Star Tool out, I will be able to get back to some flying!

    Best wishes
    Steve
This discussion has been closed.

© Vanilla Keystone Theme 2025