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.

MSFS: Is it normal that I have to reconfigure GIT at every launch of the simulator

I don't know if it is supposed to be like that, but every time I start a new session of MSFS (with GIT 4.2.0.0 started), my Goflight modules are blank and dead. Pressing a button on the GF-166s or the MCP-PRO does not wake them up. GIT status is displaying all green.

I must reconfigure them in GIT every time.
MCP-PRO > Device 0 > enabled > FS Default
GF-166 > Device 0 > enabled > COM
GF-166 > Device 1 > enabled > NAV
GF-166 > Device 2 > enabled > NAV

Only then do they come alive. Shouldn't GIT remember my configurations ?

I understand that GIT for MSFS is still work in progress and I appreciate your efforts, I just wish that there is a way to avoid having to do this every time I start MSFS. Any suggestions ?
Tagged:

Comments

  • Oh brother. If this is that under developed, I'll wait before I try and figure out how to set my stuff up in this tool. I don't even know how to download the updated version. It would be nice if the tool updated itself.
  • NBouc,

    No it shouldn't be doing that and I'm not seeing that behaviour on my PC. Can you try renaming Documents\GoFlight Interface Tool so GIT starts with new config files and try re-configuring again and see if it sticks. Also make sure GIT is quitting as that is when the settings can saved.

    Best wishes
    Steve
  • GS FS2020 is available in your account downloads, along with all the other versions. See the last entry in this article for more info: https://www.pollypotsoftware.org.uk/support/need-assistance.html

    Best wishes
    Steve
  • Thank you Steve for your reply, you told me exactly what I needed to know. I followed your advice and also applied the guide lines provided in your “FS2020 Feature Status and Usage” post. It looks like my problem is now solved.

    I think that my initial mistake was to believe that once GIT was configured for a default aircraft, it should work for any other default aircraft.

    I want to express my gratitude to you for providing us with a version of GIT for FS2020 so quickly, and that works quite well I might say. Being able to use my Goflight modules in FS2020 makes my flights so much more enjoyable.

    Best wishes,
    Normand.
  • NBouc said:

    I don't know if it is supposed to be like that, but every time I start a new session of MSFS (with GIT 4.2.0.0 started), my Goflight modules are blank and dead. Pressing a button on the GF-166s or the MCP-PRO does not wake them up. GIT status is displaying all green.

    I must reconfigure them in GIT every time.
    MCP-PRO > Device 0 > enabled > FS Default
    GF-166 > Device 0 > enabled > COM
    GF-166 > Device 1 > enabled > NAV
    GF-166 > Device 2 > enabled > NAV

    Only then do they come alive. Shouldn't GIT remember my configurations ?

    I understand that GIT for MSFS is still work in progress and I appreciate your efforts, I just wish that there is a way to avoid having to do this every time I start MSFS. Any suggestions ?

    I have the same problem every time I start GIT and the SIM I need to reconfigure all of my 11 modules.
Sign In or Register to comment.