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.

X Plane 12

Hi, do we need to do anything special to use the tool to work in XPlane 12? at the min if I copy from xplane 11 it crashes
«1

Comments

  • What crashes, GIT or XPlane? If XPlane, paste the GITlog.txt file from your XPlane 12 directory.

    Best wishes
    Steve
  • hallo
    GIT crashed x plane12 Mcp pro any help?
    thxxx
  • log file
    Violation by GoFlight Interface Plugin (xplanesdk.examples.DataRefEditor - G:\X-Plane 12/Resources/plugins/GIT Plugin/64/win.xpl)
  • I am also experiencing crashes (of XP12) when launching GIT... (have latest version). My hardware is
    EFIS x 2
    MCP PRO
    DIO

    Thanks!
    Happy to provide logs if necessary
  • Sir, a useable updated GIT File for XPLANE 12 would be gratefully appreciated. My understanding is it only requires some minor alterations. Kind regards John Reynolds (Moragon)
  • log file
    Violation by GoFlight Interface Plugin (xplanesdk.examples.DataRefEditor - G:\X-Plane 12/Resources/plugins/GIT Plugin/64/win.xpl)

    Make sure the DataRefEditor plugin is not running.

    Best wishes
    Steve
  • Aloha Steve,

    Not running dataref editor, plugin installed and app not started boots and runs until GIT app is run and then crashed, and kicks xplane12. If Git App is running and XP12 is run it never passes loading plugins, same violation error.

    Log.txt
    threading violation calling XPCreateWidget (C:\jenkins\xplanesdk\Src\XPLM\Src\XPWidgets.cpp:113)
    Violation by GoFlight Interface Plugin (xplanesdk.examples.DataRefEditor - E:\X-Plane 12\Resources\plugins\GIT Plugin\64\win.xpl)

    Git Log:
    13-09-2022 11-43-09: GIT Plugin Starting ...
    13-09-2022 11-43-09: Message Pipe Running!
    13-09-2022 11-43-09: Client Connect ...
    13-09-2022 11-43-09: GIT Plugin Started!
    13-09-2022 11-46-29: Client Connected!
    13-09-2022 11-46-29: Connecting ...
    13-09-2022 11-46-30: Cleanup Running ...
    13-09-2022 11-46-30: Cleanup Write Data Refs ...
    13-09-2022 11-46-30: Write Data Refs Cleaned!
    13-09-2022 11-46-30: Cleanup Detective Vars ...
    13-09-2022 11-46-30: Detective Vars Cleaned!
    13-09-2022 11-46-30: Cleanup Commands ...
    13-09-2022 11-46-30: Commands Cleaned!
    13-09-2022 11-46-30: Cleanup Complete!
    13-09-2022 11-46-30: Cleanup Ended!

    Mahalo,
    Gary

  • Steve,
    Also getting CTD. Don't have dataref editor installed or running.

    Threading violation calling XPCreateWidget (C:\jenkins\xplanesdk\Src\XPLM\Src\XPWidgets.cpp:113)
    Violation by GoFlight Interface Plugin (xplanesdk.examples.DataRefEditor - E:\_X-Plane 12\Resources\plugins\GIT Plugin\64\win.xpl)

    14-09-2022 16-53-12: GIT Plugin Starting ...
    14-09-2022 16-53-12: Message Pipe Running!
    14-09-2022 16-53-12: Client Connect ...
    14-09-2022 16-53-12: GIT Plugin Started!
    14-09-2022 17-11-30: Client Connected!
    14-09-2022 17-11-30: Connecting ...
    14-09-2022 17-11-31: Cleanup Running ...
    14-09-2022 17-11-31: Cleanup Write Data Refs ...
    14-09-2022 17-11-31: Write Data Refs Cleaned!
    14-09-2022 17-11-31: Cleanup Detective Vars ...
    14-09-2022 17-11-31: Detective Vars Cleaned!
    14-09-2022 17-11-31: Cleanup Commands ...
    14-09-2022 17-11-31: Commands Cleaned!
    14-09-2022 17-11-31: Cleanup Complete!
    14-09-2022 17-11-31: Cleanup Ended!

    Thanks!
    Rodney
  • Same here.

    log.txt (xplane 12)
    XPR 6:31:36 PM plugin enableFound stats plugin: 4
    0:00:00.000 D/HID: HID Bridge Running
    0:00:00.859 I/TEX: Target scale moved to 16.000000
    Threading violation calling XPCreateWidget (C:\jenkins\xplanesdk\Src\XPLM\Src\XPWidgets.cpp:113)
    Violation by GoFlight Interface Plugin (xplanesdk.examples.DataRefEditor - C:\Games/X-Plane 12/Resources/plugins/GIT Plugin/64/win.xpl)

    GITlog.txt
    15-09-2022 18-31-35: GIT Plugin Starting ...
    15-09-2022 18-31-35: Message Pipe Running!
    15-09-2022 18-31-35: Client Connect ...
    15-09-2022 18-31-35: GIT Plugin Started!
    15-09-2022 18-31-35: Client Connected!
    15-09-2022 18-31-35: Connecting ...
    15-09-2022 18-31-36: Cleanup Running ...
    15-09-2022 18-31-36: Cleanup Write Data Refs ...
    15-09-2022 18-31-36: Write Data Refs Cleaned!
    15-09-2022 18-31-36: Cleanup Detective Vars ...
    15-09-2022 18-31-36: Detective Vars Cleaned!
    15-09-2022 18-31-36: Cleanup Commands ...
    15-09-2022 18-31-36: Commands Cleaned!
    15-09-2022 18-31-36: Cleanup Complete!
    15-09-2022 18-31-36: Cleanup Ended!
  • I can't even get this software to install for Xplane 12. Hopefully they come out with an update for it to work in Xp12. As it stands, I can't use the sim and the Zibo mod without the MCP...
  • Same issue here. XP12 CTD as soon as I launch GIT. Don't use Dataref Editor.
  • Error in log file shows Violation by GoFlight Interface Plugin (xplanesdk.examples.DataRefEditor - E:\X-Plane 12\Resources\plugins\GIT Plugin\64\win.xpl)

    But I don't have DataRefEditor. Never used it, nor is it currently installed (Don't even have it downloaded).
  • 18:59:23 GoFlight Connection Starting.....
    18:59:23 X-Plane Connection Starting.....
    18:59:24 GoFlight Connection Started
    18:59:29 GIP: Pipe Connect Failed!

    Steve. We all sure could use your help in getting this working for XP12. Thanks!
  • I have looked into this issue and the crash is being caused by creating a widget, which as far as I can find out are still supported in X-Plane 12.

    The actual call that is causing the exception is XPCreateWidget which should return null if it fails and not crash out.

    Looking at the release notes for X-Plane, the XPLM (X-Plane Plugin Manager) is listed under Incomplete or missing features. So I'm assuming XPLM is bugged and causing the crash because its XPLM_64.dll that is crashing.

    So at this point, the logical thing is to wait for the XPLM to be updated.

    Best wishes
    Steve
  • Thanks Steve. So maybe they will get that worked out in the next beta release.
  • Thank you for the update and clarification, Steve.

    I hope Austin and his team fixes the issue soon.
  • hello Steeves ,

    as you are creators of GIT can you send a message to Laminar for this problem , you will surely have more importance than us

    in advance, thank you

    Roland
  • XPWideClient has a similar issue (Threading violation calling XPSendMessageToWidget (C:\jenkins\xplanesdk\Src\XPLM\Src\XPWidgets.cpp:247)).

    But I read somewhere that this is not an issue with XPLM (X-Plane Plugin Manager), but that the error is caused because XP12 is now catching some illegal API calls.

    Because X-Plane 11 wasn't catching it making illegal API calls we supposed it worked fine. In reality, it was probably the cause of some random crashes.
    Now X-Plane 12 catches it doing something that it shouldn't - but it is just as broken in X-Plane 11

    As far as I read in the Known Bugs is Incomplete or missing New XPLM APIs in Alpha/Early Access.
  • dmeerpa said:

    XPWideClient has a similar issue (Threading violation calling XPSendMessageToWidget (C:\jenkins\xplanesdk\Src\XPLM\Src\XPWidgets.cpp:247)).

    But I read somewhere that this is not an issue with XPLM (X-Plane Plugin Manager), but that the error is caused because XP12 is now catching some illegal API calls.

    Because X-Plane 11 wasn't catching it making illegal API calls we supposed it worked fine. In reality, it was probably the cause of some random crashes.
    Now X-Plane 12 catches it doing something that it shouldn't - but it is just as broken in X-Plane 11

    As far as I read in the Known Bugs is Incomplete or missing New XPLM APIs in Alpha/Early Access.

    Thanks for the heads up on this. You are correct, it no longer allows the call to made from a non X-Plane thread. Creating the widget at x-plane start up worked fine. I will have to rework the plugin.

    Best wishes
    Steve
  • There is now an X-Plane 12 plugin available to download from your account.

    It is a work in progress as all X-Plane SDK calls need to be moved so they are executed in X-Plane threads/call backs. It still may crash until this work is completed.

    Let me know how you all get on.

    Best wishes
    Steve
  • admin_pps said:

    There is now an X-Plane 12 plugin available to download from your account.

    It is a work in progress as all X-Plane SDK calls need to be moved so they are executed in X-Plane threads/call backs. It still may crash until this work is completed.

    Let me know how you all get on.

    Best wishes
    Steve

    Thanks Steve,

    Just installed the xpl file.
    No crashes so far, and I did some quick test assigning a rotary and a display, which worked well.
    I don't know but it felt like the MCP PRO rotary was working way better then before, but I had just my EFIS and MCP PRO connected, with only a few things configured. Normally I have 13 other Goflight modules that are also connected, and I must say my new computer is also a lot more powerful.
    And both modules are currently connected to USB 3.2 Gen 2 ports instead of a 2.0 USB Hub...

    Tomorrow I will look to copy my config files for the ZIBO from my old computer.
  • Configured 7 modules so far. No real issues (just some datarefs that has changed since my last use I guess or difference between XP11 and 12).

    Only bug so far, I noticed when you close XP12, and the GoFlight Interface Tool X-Plane is still open, it will hang.
    You will need to close the app via the Task Manager. I was even not able to move the GoFlight Interface Tool X-Plane window.
  • dmeerpa said:

    Only bug so far, I noticed when you close XP12, and the GoFlight Interface Tool X-Plane is still open, it will hang.
    You will need to close the app via the Task Manager. I was even not able to move the GoFlight Interface Tool X-Plane window.

    It has been like that for me for a few years now. So I got used to closing GIT b4 I close X-Plane ;)

    But thanks for letting us know the plugin seems to be resolving the CTD and allow you to get your modules to work.

    That means I'll be testing it myself this evening after work, YAHOO!!

  • New version of GIT for X-Plane now out with all necessary code changes complete for supporting X-Plane 12.

    Best wishes
    Steve
  • edited October 2022
    admin_pps said:

    New version of GIT for X-Plane now out with all necessary code changes complete for supporting X-Plane 12.

    Best wishes
    Steve

    It's not working for me after upgrade...

    At startup of GIT it keeps scanning files.

    17:20:51 GoFlight Connection Starting.....
    17:20:51 X-Plane Connection Starting.....
    17:20:52 GoFlight Connection Started
    17:20:53 X-Plane Connection Started
    17:20:53 Aircraft Connection Starting.....
    17:20:53 X-Plane: Event Received: Aircraft Loaded/Flight Loaded
    17:21:24 WinSock: Connection Failed: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    17:21:24 LUA Processor: Connect Exception - Unable To Connect!
    17:21:24 Aircraft Connection Started
    17:21:24 Synchronising Switches & Selectors .....
    17:21:24 Synchronising Switches & Selectors: Waiting for X-Plane .....
    17:21:41 LvarNamesUpdated!
    17:21:41 Creating Bespoke Vars
    17:21:41 Bespoke Vars Created
    17:21:41 Importing Bespoke Variables
    17:21:41 Bespoke Vars Assigned, Importing Bespoke Events
    17:21:41 Bespoke Events Temp Imported
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef laminar/B738/EFIS_control/capt/map_mode_pos - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef laminar/B738/EFIS_control/capt/map_mode_pos - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef laminar/B738/EFIS_control/capt/map_mode_pos - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef laminar/B738/EFIS_control/capt/map_mode_pos - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef laminar/B738/EFIS_control/capt/map_mode_pos - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef laminar/B738/EFIS_control/capt/map_mode_pos - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef laminar/B738/EFIS_control/capt/map_mode_pos - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef laminar/B738/EFIS_control/capt/map_mode_pos - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef laminar/B738/EFIS_control/capt/map_mode_pos - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef laminar/B738/EFIS_control/capt/map_mode_pos - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef sim/cockpit2/autopilot/vvi_dial_fpm - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef sim/cockpit2/autopilot/vvi_dial_fpm - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef laminar/B738/autopilot/mcp_speed_dial_kts_mach - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef laminar/B738/autopilot/mcp_speed_dial_kts_mach - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef sim/cockpit2/autopilot/vvi_dial_fpm - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef sim/cockpit2/autopilot/vvi_dial_fpm - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef laminar/B738/autopilot/mcp_speed_dial_kts_mach - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef laminar/B738/autopilot/mcp_speed_dial_kts_mach - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef sim/cockpit2/autopilot/vvi_dial_fpm - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef sim/cockpit2/autopilot/vvi_dial_fpm - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef sim/cockpit2/autopilot/vvi_dial_fpm - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef sim/cockpit2/autopilot/vvi_dial_fpm - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef laminar/B738/autopilot/mcp_speed_dial_kts_mach - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef laminar/B738/autopilot/mcp_speed_dial_kts_mach - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef sim/cockpit2/autopilot/airspeed_dial_kts_mach - 20003
    17:21:41 GIP: Send Message - Unexpected Reply Messsage - 20003
    17:21:41 GIP: Unable to Monitor DataRef sim/cockpit2/autopilot/airspeed_dial_kts_mach - 20003
    17:21:41 Bespoke Events Imported
    17:21:41 Loading Aircraft Settings
    17:21:41 GetXMLConfigData
    17:21:41 GotXMLConfigData
    17:21:41 Loading Power
    17:21:41 Loading MCPPRO
    17:21:41 Loading MCP
    17:21:41 Loading EFIS
    17:21:41 Loading P8


    When removing 'SettingsXPlane.xml' it starts.
    When I import for example my "b738_4k_GFP8-0.xml" or"b738_4k_GFT8-0.xml" GIT is no longer responding.

    Content of my "b738_4k_GFP8-0.xml":



    I reinstalled 2.0.16.3 with the patch 'Plugin Work In Progress', but this one also no longer works, keep getting popup that there is a new version, but also window saying 'Object reference not set to an instance of an object.

    When clicking OK on the new update I get an Application Halted.

  • hello Steeves


    Git 3.0.0.0
    the process stops there and the git pluggin folder is not installed in XPlane 12 /resource/plugin

    w10 -

    thanks for your help

    Roland

    image
  • sorry

    with this message




    image
  • Application Halted is due to corrupt settings file. Delete C:\Users\\AppData\Local\PollyPot_Software.

    The 20003 errors, can be safely ignored; it's just a notification that the dataref has already been registered. I will need to change that error reporting.

    You cannot connect to Winsock/Lua because the IP address of your PC needs to be set in Lua Config.txt which sits in Documents\GoFlight Interface Tool.

    Best wishes
    Steve
  • edited October 2022

    hello Steeves


    Git 3.0.0.0
    the process stops there and the git pluggin folder is not installed in XPlane 12 /resource/plugin

    w10 -

    thanks for your help

    Roland

    Is the pop up window appearing behind your installer to prompt for the X-Plane 12 directory during setup?

    Best wishes
    Steve
  • admin_pps said:

    Application Halted is due to corrupt settings file. Delete C:\Users\\AppData\Local\PollyPot_Software.

    The 20003 errors, can be safely ignored; it's just a notification that the dataref has already been registered. I will need to change that error reporting.

    You cannot connect to Winsock/Lua because the IP address of your PC needs to be set in Lua Config.txt which sits in Documents\GoFlight Interface Tool.

    Best wishes
    Steve

    Delete C:\Users\\AppData\Local\PollyPot_Software.
    Uninstalled everything
    Renamed

    Winsock/Lua, never touched the IP, it was still localhost. Maybe related to the corrupt settings.

    C:\Users\\Documents\GoFlight Interface Tool

    Reinstalled 3.0.0
    Can import XML files, but it seems GIT 3.0.0 can not read any Datarefs.

    18:01:33 GIP: Send Message - Unexpected Reply Messsage - 20003
    18:01:33 GIP: Unable to Monitor DataRef laminar/B738/annunciator/master_caution_light - 20003

    My configured switches seems to work, but none of the leds or displays works.

    other error I have in my log
    18:01:34 XPlane: Event Received: Sim State 1
    18:01:34 GIP - Message Processor Exception: An item with the same key has already been added.
    18:01:34 Aircraft To GF46: Nullable object must have a value.
    18:01:37 Synchronising Switches & Selectors Complete
Sign In or Register to comment.