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.

A few questions on GIT for XP

Hi Steve, 

Fist off congrats on your release for XPX

A few questions:

1)  Do I need to install this to the Goflight directory as I have my XPX install and another drive and want to keep everything associated with X-plane there. 

2) Is there any way to have it open the text files with a different text editor like Notepad ++ ( way easier to detect mistakes with that :) )

3) Are the settings and everything separate from the FSX/P3D version (IE no chance for one sim  to mess up the others files)
Steve McNitt

Comments

  • Hi Slayer,

    1) No, its no longer necessary.

    2) Yes, just make Notepad++ your default editor for text files.

    3) The BespokeEvents.xml and BespokeVariables.xml are shared. The other settings are stored in SettingsXPlane.xml. I'll work on separating it all out in the next release.

    I have just added a Quick Start Guide for GIT (XPlane) Under Support\User Guides which will help you.

    Best wishes

    Steve 

  • Great I love Notepad++, I'll have to set that as my Windows default text editor(duh)

    The quick start was the first thing I looked for and found it :)

    I am running into an issue when using the detective , whenever I click start monitoring everything crashes XPX and GIT locks up. I removed dataref editor per the instructions so it is no longer on my XPX install. Any ideas? 

    Working on a profile for the new IXEG 737 and they provided a full list of datarefs and custom commands, was just trying to figure out which data ref I needed to use in my bespoke event so wanted to use the monitor to see what was sent when i flipped the switch in the VC.
    Steve McNitt
  • Test with a standard X-Plane aircraft and see if it still occurs. If not, try filtering out all the standard DataRefs, perhaps its over-loaded. If still no good, add "/log" in the shortcut so it produces a log file and send it me. Also what version of X-Plane are you using 9/10 32 or 64bit.

    Thx

    Steve

  • edited April 2016

    Also, not sure if you had the old Beta version installed. Check the wpl files in the plugin for GIT are recent and not the old ones from last year.

    Remove any wpl file that its GIT Plugin, they should only be in the sub directories 32 and 64.

    Thx

    Steve

  • XP version 10.45 x64. 

    It's working with the default B58, the 32 and 64 bit plugins are today's date. 

    I also have a feeling it may be overloaded with the payware. I'll try filtering it down to areas of interest and see if that helps. 

    Thanks for the help
    Steve McNitt
  • Could be, I have no idea how many additional DataRefs the IXEG adds. If its 1000's it may be a problem. There could also be a fault with one of the IXEG DataRefs that is triggering an exception. Exclude all the IXEG DataRefs and see if it works and then unhide chunks of them until it breaks, it will pinpoint the problem.

    Keep me posted, although I'm off to bed now, I'll pick the issue up in the morning.

    Best wishes

    Steve

  • edited April 2016
    IXEG is using a platform called Gizmo and as far as I can tell this is where the crash is coming in from my logs. I've made a post on their forums. 

    It seems standard datarefs are ok but once I start using their custom datarefs that use the gizmo manipulators after a couple of cycles of a switch etc it throws a crash.

    I'll repost something here from Sandy Barbour ( a longtime expert XP guy) from a couple of years ago that I think is appropriate and probably is where the problem lies.

    "This has nothing to do with X-Plane directly as it does not load plugins, it is more to do with what happens when an error occurs in a plugin.

    Plugins are loaded by the plugin manager (XPLM) and the plugin manager alone.

     

    What usually happens is this and it applies to all plugins.

    The plugin is loaded and the plugin's code runs.

    If at any time the plugin does something that causes an exception and the plugin is not set up to handle the exception then X-Plane will crash.

    This is because the plugin manager and all plugins are mapped into X-Plane's process and address space so if a plugin misbehaves X-Plane generally crashes.

     " 

    I'm going to temporarily set the IXEG aside  right now to try some other Boeings with your program. Flight factor 757, 777 and the SSG Boeing 747 should match up nicely with the MCP and EFIS although they don't include documentation of their datarefs like IXEG do.

    PS I'm in communication with another user that is using different hardware and means to access their datarefs and he also gets crashes with Gizmo so it appears to be a problem with the IXEG product.
    Steve McNitt
  • Hi Steve,

    Yes it does sound like an IXEG problem if other users are having crashes using their DataRefs with different hardware and software.

    I have tested GIT for XPlane with every default aircraft and 3 payware aircraft with no problems.

    Let me know if you get any updates from IXEG.

    Best wishes

    Steve

  • I have one more question if you don't mind. 

    The disconnect switch is referred to as a button, not a big deal but what is the light data associated with that?  Shouldn't it be greyed out or is that for some other function I'm not aware of? It's the same on the FSX version I've just always left it alone.
    Steve McNitt
  • edited April 2016

    It's for switch syncing. The Light Data variable is read to determine what to do in the VC when GIT first starts. Its the same for the SECM, it has no lights but the logic is used to determine how to set the VC up when starting so the GoFlight hardware is in sync with the VC.

    Best wishes

    Steve

  • Is there a way to blank a display? 

    I'm making a profile for the FlightFactor 777 ( 777 has no course displays so I would like to blank them )  they always load up with a value that it initially reads even though I have a blank box for the Light display data I thought to set it to a dummy value of zero but then the zero would still show?
    Steve McNitt
  • No there isn't. I would have to build that feature into GIT. It's a good idea so I'll add it to the Development Plan.

    Best wishes

    Steve

  • +1 to the blank display capability. The vertical display and the IAS display should remain off all the time when VNAV/LNAV are engaged. That would be very cool if possible.
  • Hi Steve

    Try the attached GIT plugin replacement and see if the crashes stop with the IXEG. Upzip it and place into your X-Plane Directory\Resources\plugins and overwrite what is already there.

    Thx

    Steve

Sign In or Register to comment.