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.

Instability problems between FSUIPC and GF Interface or PMDG ?

2

Comments

  • I cannot be certain that the GoFlight drivers are not in use when you use default aircraft. I need you to follow the steps I outlined and confirm you have dashes on the displays and then move on to the second step.

    Thx
    Steve
  • On the other hand Is it normal when I open GFIT on the MCPPRO index that the device box always returns to disabled when I configured it enabled and save?
    ok I will do that
  • It is isn't disabled, the status updates when you select a device. When it first starts, no device is selected so everything is greyed out.
  • with baron aircraft Nothing happens, all the displays are off
  • If the GoFlight Databridge is running and GIT isn't and you have set the MCP PRO to "compatiable add-on" in GFConfig, you will see dashes on the MCP PRO when FSX has started. If you aren't double check you have configured GFConfig correctly (particularly take note of the Flight Sim Version tabs).

    Thx
    Steve
  • no dash on MCP
  • I checked the installed version fsx
  • I think I will stop for tonight I'm starting to saturate, say which files could be useful to the understanding of this problem, I would send them to you.
    Good evening Steve
  • Morning Steve,
    If I summarize the situation:

    GFconfig on Addon
    TQ6, GF166, GF46 and MCP are identified, the latter only has its buttons illuminated.

    I open FSX, the buttons are no longer lit but there is a dash on each display.

    I charge the 737 PMDG on an airport, all the displays go out.

    I run GFIT from the VC, the displays flash zero and then turn off.
  • Some news, I cleaned my registry, restarted GFconfig, FS and GFIT, there is better since now the buttons and switches are active only the displays remain off... How can Ido for and now how to make them work?
  • I think reinstall .NET Framework and remove and reinstall the NGX.
  • Yes, I just installed version 4.6.01590 this morning .... Is there a preferential order of installation? Net frame first?
  • Here I have everything uninstall and reinstall and the displays are still not working !!!
  • Is the MCP PRO displaying nothing or zeroes?
  • Also you need .NET Framework 4.6.1+. The version you have reinstalled is to old.
  • Morning Steve,
    As I wrote to you yesterday morning:


    If I summarize the situation:

    GFconfig on Addon
    TQ6, GF166, GF46 and MCP are identified, the latter only has its buttons illuminated.

    I open FSX, the buttons are no longer lit but there is a dash on each display.

    I charge the 737 PMDG on an airport, all the displays go out. (nothing displays)

    I run GFIT from the VC, the displays flash zero and then turn off.


    On the other hand, the frame work version installed is the 4.61.
  • If you turn the rotaries on the MCP PRO does the NGX get updated e.g. the altitude knob does change the altitude.

    In Documents\Flight Simulator X Files, edit the Simconnect.ini file so it looks like:

    [SimConnect]
    level=Verbose
    console=Yes
    file=C:\SimConnect%01u.Log
    file_max_index=9

    Start GIT and FSX, load up the NGX and get to the VC. Then quit FSX. A log file will be created in C:\ (or many log files). Copy these and attach to this thread please.

    Thx
    Steve
  • Sorry Steve but I do not find a simconnect.ini in the folder you specify, nor elsewhere else,

    Only a simconnect.xml in the main folder C:\Users\Utilisateur\AppData\Roaming\Microsoft\FSX
  • Just create the file in notepad and add the lines.

    Thx
    Steve
  • ok Steve
    I created the Simconnect.ini file with notepad and inserted it into Documents \ Flight Simulator X Files.
    I started FSX, PMDG in VC and GFIT.
    Closed the whole but the file ini not changed and I do not see other files that have been created on C or on D elsewhere or is located FSX
  • When FSX started you should have seen a black cmd window open with information being updated in it. If you did and a file called Simconnect0.log was not created in C:\ try running FSX as Administrator.

    If you didn't see the black cmd window you have misspelt the filename or put the file in the wrong place.

    Thx
    Steve
  • I will try again, confim me that the right way for the file isC:\Users\Utilisateur\Documents\Flight Simulator X Files or C:\Users\Utilisateur\Documents\Fichiers Flight Simulator X
  • The first one!
  • the second folder is the right way, I send you attached the file
  • edited July 2017
    That hasn't shown anything wrong. We need to get your sim back to basics:

    1) Copy GFDev.dll from C:\Program Files (x86)\GoFlight and put it somewhere safe.
    2) Uninstall the GoFlight Drivers (keep GIT installed!).
    3) Copy back GFDev.dll to C:\Program Files (x86)\GoFlight.
    4) Rename C:\Users\Utilisateur\AppData\Roaming\Microsoft\FSX\EXE.XML to EXE.XML.OFF
    4) Edit C:\Users\Utilisateur\AppData\Roaming\Microsoft\FSX\dll.xml and for each main entry disable it unless its the GoFlight Interface Module or PMDG related. Each entry can be disabled by changing the Disabled tag from False to True
    5) Rename Documents\GoFlight Interface Tool to Documents\GIT OLD
    6) Start FSX and Set your default flight to be the Trike. Quit FSX.
    7) Start FSX and confirm the Trike has loaded as the default aircraft. If not, do it again.
    8) Start the default flight as the Trike and confirm the MCP PRO displays remain blank.
    9) Start GIT and confirm the MCP PRO still has blank displays.
    10) On the GIT MCP PRO tab, select Device 0 and then click Default FS and then Enable the device. Turn the altitude knob and confirm the altitude value is changing.
    11) Do not go back to the FSX main screen but use the top menu to click Aircraft, Select Aircraft and choose the NGX. The MCP PRO should have operational displays.

    Let me know at what point you have different results as described above.
    Thx
    Steve
  • At point 9 after the start of FGIT as the default flight loaded the PMDG, the MCP is already functional with the active displays
  • edited July 2017
    You can't have the default flight set as the NGX as it causes problems as discussed in the FAQ link I sent to you days OK. This will be the cause of your issues! See bold entry below:

    My MCP PRO or MCP Advanced is not updating its display (just showing zeroes)

    There are 5 potential causes.

    1) You are not running the latest versions of the NGX or 777. The NGX needs to be installed with SP1D.

    2) The PMDG NGX and 77X will stop sending messages via their SDK and thus into this driver if

    - the aircraft is flown and then you return to the FSX main menu and re-fly it again;

    - switch between different models;

    - your default flight is set to use the NGX or 777 and then you change to another NGX/777 aircraft or model;

    It will manifest itself as the displays on the MCP PRO not updating, although you can use buttons and switches on the MCP PRO and the NGX/77X will respond. You will also notice no activity on the PMDG status LED on the Status Tab.

    PMDG have acknowledged this as an issue with FSX/Simconnect and is why they always recommend to restart FSX after each flight with the NGX/77X.

    3) It may also be due to the PMDG SDK not being enabled. The enabling of the SDK is automatic if you have "FSX Enabled" and/or "Prepar3D Enabled" (whichever is appropriate) ticked on the Settings tab. You can check or set this option manually by using notepad to open the follow file(s):

    For the NGX: \PMDG\PMDG 737 NGX\737NGX_Options.ini

    For the 777: \PMDG\PMDG 777X\777X_Options.ini

    and ensure the following exists:

    [SDK]
    EnableDataBroadcast=1 (if this is set to 0 change it to 1)

    4) On some systems the Flight Simulator software and the GoFlight Interface Tool need to be run as Administrator. Right click on the program concerned (e.g. FSX.exe and afterwards GoFlight Interface Tool.exe). Select the compatibility tab and tick run this program as administrator.

    5) You do not have the latest .NET Framework installed.
  • Sorry Steve I read it but misinterpreted....English is not my mother tongue and a few days I had a lot to understand

    Otherwise if I load another device in the fault flight and to continue point 9, no display will turn on and I do not have access to the MCPPRO window on GFIT, it remains grayed out

    What can I do now? downloaded again drivers ?
  • I thought you had said the displays were working: "At point 9 after the start of FGIT as the default flight loaded the PMDG, the MCP is already functional with the active displays"
  • Also what was on the displays zeros or values?
Sign In or Register to comment.