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 with msfs2020 and goflight drivers

One thing not clear to me. Does the git software need the goflight drivers when using only msfs2020?
Tagged:
«1

Comments

  • I am using and no Goflight drivers. as Steve says: It is a work in progress, but it does the trick for me.
  • Ok, I will try it without the drivers.
  • I include GFDev.dll from the drivers, so no need for them.

    Best wishes
    Steve
  • Thx, got them working. Great software!
    However, displays are not functional. I suppose this has something to do with Windows USB power management?
  • If you mean the GF166's you need to click one of the pre-configure buttons on the tab (NAV, COM or ADF). Also remember to enable the device, then quit GIT and restart it and it will work OK. The GF166's are very finicky, but as long as they were working before GIT, they will work fine.

    Best wishes
    Steve
  • Sorry if this is the wrong place for my question.
    Regarding MSFS2020.
    I am new to 2020 but not to simming. I have used GF's modules for many years with FSX, 2004 and P3Dv5.3.
    That said, I am completely befuddled with the GIT using the P8, T8, 166, 45, 46. Fine with MCP-Pro and LGT.
    I would think that there may be presets out there for these modules for 2020, ior more concise info.
    I have read the instructions many many times, but seem to not be able to figure out how to set up as in the other simulations like P3D, FSX, where I love the modules. (I am familiar with FSUIPC and have the 7, but would rather not have to use this)
    Suggestions or ?,
    Many thanks,
    Bill T.
    USA, California
  • You can automatically configure the GF166, 45 and 46. E.g. the GF166 has buttons on the GIT GF166 tab for COM, NAV, ADF. See this for additional info: https://www.pollypotsoftware.org.uk/vanillaforums/discussion/1436/fs2020-feature-status-and-usage/p1

    The P8 and T8 need to be configured as required. As an example for the P8, to assign parking brakes to a button. Select the button in GIT on the P8 tab, select the ON Event to PARKING_BRAKES and set the led to BRAKE_PARKING_INDICATOR with an action of ON and a value of 1.

    Best wishes
    Steve
  • Hi,
    Many thanks regarding the the 45, 46 and 166, (I just did not see those options in GIT)
    I have looked at the T8 and P8 in the forum and think that it might be a little more daunting to program a toggle or button to achieve a result for ON/OFF on a toggle or just ON on a button (needing another press to turn OFF on that button) as opposed doing another button to do just OFF.
    Thank you Admin/Steve,
    Bill T.
  • For buttons use either the ON or OFF Event and select an Event that toggles something on or off.

    For switches you can program the ON and OFF Events with distinctive Events (e.g. PARKING_BRAKES_OFF) or use an Event that toggles for both ON and OFF.

    Best wishes
    Steve
  • Hi, thanks.

    I have tried that to no avail; here is my GIT values for T8, number 1;
    SWITCH EVENT , on , LANDING LIGHTS, TOGGLE
    SWITCH ACTION, onoff ( no ON and OFF, I cannot see that on the pulldown list))
    LIGHT DATA, landing light, gear
    LIGHT ACTION, nothing , LIGHT VALUE, 1
    Nothing happens, I am confused regarding the "light data", 'light action" and "light value". I don't see or am aware of the meanings of these terms.
    Is there somewhere where they are more defined for me to check out? I just don't understand this "light" stuff. Sorry

    (Anybody else here any suggestions? Thanks)

    Thanks Steve
  • Event should be LANDING_LIGHTS_TOGGLE
    Switch Action should be NOTHING. Most Switch Actions are for use with PMDG aircraft.
    Light Data should be LIGHT STATES
    Light Action HAS_FLAG
    Light Value 4

    The various landing lights related variables are very unreliable and the only consistent way I have found is to use the above. The value 4 is used to detect the landing lights state.

    Best wishes
    Steve
  • Thanks ,
    From what I am experiencing with this is that it seems to me is that my expecting 2020 and GF modules is not the same as with P3Dv5 and GF modules. (not meaning to blame one or the other)
    In the past, I was able to use the GF modules with FS, FSX, and Steam with none of this needing this 'special handling.'
    I appreciate your help, thanks,
    Bill T.
  • Several times in the past when starting 2020 with the default Baron (which I have been using quite frequently,) I have noticed that some of the functions of the MCP Pro do not work. Today, the CRS1 worked, but not the HDG,ALT or V/S.
    So I turned off the PC and started again, everything works fine, any ideas as to the sometimes working and sometimes not?
    Thanks and cheers,
    Bill
  • Were you using a different aircraft before switching to the baron, or was it a fresh start?
  • Sorry to be so slow in answering. I have had no such events as of late, everything seems to be working great.
  • In thinking more about it, yes, I do recall that I was changing aircraft, but I think it is no longer anything to be concerned with.

    I really want to be able to see the T8 and P8 switches or buttons light up when activated.
    I am looking at FSUIPC as well as Pollypot for a simple way to get the indicator lights to show that the switch or button has been activated.
    I would try Lua with FSUIPC but don't know where to start to put any scripts to begin with.
    Yes, I realize that this is not the place for any FSUIPC questions
    So, I was thinking that there must be somewhere for somebody (me) with no coding experience to obtain the scripts needed for my purposes. And how to use them.
    Anybody, any help please.
    Many thanks, I appreciate all the knowledge that's in these forums.
  • Be careful mixing GIT with FSUIPC. If you configure the same controls in both, things will clash and cause problems.

    Best wishes
    Steve
  • Okay, regarding GIT, 2020 and GF MCP Pro, I notice that the V/S button does not work when using the default button.
    Any suggestions here?
    Thanks
  • Which aircraft?
  • Every aircraft that I have in 2020, though I mainly use the PC12.
    Again this is a desktop cockpit.
    Thanks.
  • I don't have the PC12. Can you load up Detective, enable event monitoring then press the VS button in the virtual cockpit and let me know what Event appears.

    Thx
    Steve
  • I have done that now, but no EVENTS showing anything like the V/S.
    Perhaps I am doing it wrong, I cannot see anything in the log or find out how to send the log to you.
    The issue is with all aircraft. I am using FSUIPC7 to get the T8 switches to work but they have no lights (not your problem, mine and FSUIPC)
    I use the Honeycomb Bravo throttle and the V/S button DOES work and shows active in GF MCP Pro and then the rate can be adjusted, it just does not work when pressing the V/S button on the GF MCP Pro.
    Cheers and thanks for your interest.
  • I have just noticed that when I press the V/S button on the GF MCP Pro that the LNAV light illuminates for a brief moment.
  • I have seen an MCP Pro send the wrong button due to twisted board inside. Check the button responds correctly using this GoFlight test program: https://1drv.ms/u/s!AvmOqBMETlayh9ZQUzSikUTgvmwIyw?e=DsyIEJ

    Best wishes
    Steve
  • There is the problem, the V/S button does NOT light when pressed.
    All lights do show when tested.
    Looks like there is an issue.
    What to do next?
    Thanks for your help
  • Its a hardware issue. I had a similar problem due to a twisted board on my MCP Pro. You can try tightening/loosing the screws at the back to see if it fixes any pressure on the board. You can also try repeatedly pressing the button in case its just dirty. It may be a dry solder joint (plenty of info on the internet about resolving that). I would of course direct you to GoFlight for a repair but they have vanished into thin air; but the next best thing if none of the above works is try to find someone who is good with electronics/pcb repair.

    Best wishes
    Steve
  • BillTee said:

    There is the problem, the V/S button does NOT light when pressed.
    All lights do show when tested.
    Looks like there is an issue.
    What to do next?
    Thanks for your help

    I think I misunderstood what you were saying. Did the test software show a problem?
  • yes, it did show the problem. The V/S indicator does NOT light when pressed. On the light test, ALL lights show.
    It does look as if there is a problem with the unit.
    Thanks
  • New Issue;
    Unplugged the PC, moved it, upon restarting MS2020, all GoFlight modules work as usual EXCEPT no lights on them (166,46), MCP Pro works as usual with all displays lighted.
    The 166 and 46s do NOT light up when identifing in GIT.
    What am I missing?
    Thanks
  • For clarification; when I say lights, I mean the lighted digital readout on those units, the 166 and 46 modules themselves. Again, they do work as they should changing frequencies and so forth.
    Thanks
Sign In or Register to comment.