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.
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.
P3D v4.5
Will the latest release of GIT 3.6.5.1 also handle P3D v4.5 , especially with PMDG 777-300 ?
Greetings,
Alex
Greetings,
Alex
Comments
Best wishes
Steve
Alex
As requirements I see: GoFlight Software Drivers (GF Config Setup 2.26.5 - available from our forum)
Will the actual drivers (2.28.0) work as well?
Alex
Best wishes
Steve
Greetings,
Alex
just purchased my newGIT for P3D and read:
2a) You should choose to install the software where you Goflight drivers have been installed (where GFConfig.exe and GFDev.dll reside...
So I will install it into: c:\programs(x86)\GoFlight ??? - this is the location where my GFConfig.exe and GFDev.dll reside
Thanks for your patience with me!
Alex
After operating the FF777 with lots of GF hardware and even 3DIO boards using bespoke events in XPlane11 quite some time in perfect way...
i´m getting kind of nervous about P3D 4.5 with PMDG777 and GIT now!
Un- and reinstalled GFConfig and GIT - GIT now shown in menu bar AddOns tab with (only) restart function available.
LUA non operational:
20:53:55 LUA Processor: Pipe Connect Exception - Could not connect to the server within the specified timeout period
20:54:01 LUA Processor: Pipe Connect Exception - Could not connect to the server within the specified timeout period
20:54:07 LUA Processor: Pipe Connect Exception - Could not connect to the server within the specified timeout period
20:54:07 LUA Processor: Connect Exception - Unable To Connect!
I think this is the time when I really need help, Steve!
Thanks so far,
Alex
Just deleted the "Launch addon FSUIPC5" and restarted the whole thing
There´s just one more thing: As I have 3 DIO boards working for my OHP - I just can´t remember which LED belongs to which output (shame on me)
Question: Is there any way to identify a single led? Clicking on any output gives no action
Best wishes
Steve
sure, but I don´t have any records from my Xplane installation, so I don´t know what e.g.
"lamps/47...on greater than 0.8"
displays on the OHP!
seems I might have to break my OHP and follow every cable fron a specific LED to its connector on the DIO,
readout via DataRef Tool doesn´t help a lot because when you move any switch on the ohp many "lamps/..." will change status!
I am really sorry to "disturb" you so much, but somehow I thought P3d would be a bit easier to configure in GIT than XPlane - which is absolutely not true!
BTW: Are there no bespoke events creatable in GIT 4 P3d like they are in GIT 4 XPL???
Another question is: how can I (successfully) run GIT and FSUIPC together in P3d? - GIT only works since I´ve erased the launch command lines for FSUIPC out of DLL.XML.
Thankful for your ideas,
Alex.
I wonder if GFConfig would light a specific bulb up for you. If not I will look at adding the functionality into GIT.
I wouldn't say GIT P3D is more difficult, just slightly different especially for PMDG aircraft. Make sure you have read this: https://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/19-operating/36-configuring-goflight-devices-additional-information-pmdg-ngx-77x-747x.html
The PMDG SDK's are built into GIT so all the SDK events and variables are available so Detective/Bespoke Events seemed pointless when running PMDG aircraft. They are available for other aircraft. You can write some Lua code if you want a switch to do multiple things or use CLUSTER events.
I'm not aware of there being a problem with GIT and FSUIPC. I have certainly had both running on my development system OK. Can you try again and let me know specific errors messages.
Best wishes
Steve
thanks for reply...
NO, GFConfig does definitely not light up any LED for identification of output, It lights ONE led up to identify the selected board, which seems a little funny when looking up to a complete OHP with lots of LEDs spread on almost 1 square meter, but nothing more. DIO isn´t even added in their help files, so:
WOW!!! If you could really add this functionality into GIT... at least I would spend you some extra coffee for that
I will read the suggested file.
I will keep you updated about GIT together with FSUIPC (delayed to when I´ve finished my OHP configuration).
Thanks so very much,
Alex
I have added an LED button to the DIO screen. I haven't been able to test it as my DIO is in storage and hard to get to at the moment. I will PM you a link to download.
Best wishes
Steve
I will surely test it a little later when I´m back at my SIM and inform you about it!!!
Thanks so far, I´m already collecting money for your coffees
Greetings,
Alex.
Just installed the new file.
-- No need to be activated via key - worked right away
--When I started GIT and P3d I received an error msg that there were more devices configured than connected. (strange, I didn´t change a thing with my hardware!)
--Checking the DIOs made me cry: GIT finds only Device0 with all configurations lost, Device1 and Device2 are lost, although visible in GFconfig!
--The added function works, the LEDs are lit up when clicking on a certain output.
--The LED button does the same thing as the IDENTIFY button - all LEDs of that board are lit up.
--Checked my XPL installation - everything works fine with DIOs on my other drive!!!
Hope for a simple soluition to get my other devices back?
Greetings,
Alex.
very glad to inform you that things worked out great!
Got all my GOFlight devives back and reassigned all 3 DIO boards with your latest file
Just one thing remaining that makes me a bit cry: When I load my 777-200LR in P3d in a cold and dark status - most - but not all - of the LEDs of DIO boards are lit!!!! (ON ones as well as OFF and FAULT ones)
Looking at the virtual OHP everything is off, and all of my OHP lights are assigned AND TESTED to fit the virtual OHP.
The only way is to start the plane into flight configuration, switch all the switches from off to on and back to off, shut down the plane again into cold and dark - then all the LEDs are off!
STRANGE, isn´t it? Do you have any idea?
Greetings,
Alex
Log says: 11:52:53 Synchronising Switches & Selectors Complete...
attached the log as txt and a pic:
you can see many FAULT lights (hyd, fuel, window heat,...) on which should be off in the actual state as seen in the pic`s lower area (virtual OHP)
Only the green ones are supposed to be on - meaning 2 groundpowers available.
Done 3 times, always the same - but all light-functions are totally ok during flight!!!
If you can solve this, then you are my king!
Greetings,
Alex.
Thx
Steve
e.g. Hydraulic Left Engine Pump switch: EVT_OH_HYD_ENG1
ON light (white,working ok) DATA_OH_HYD_SWITCH_PRIMARY_ENG_PUMP_LEFT
FAULT light (yellow, on in cold+dark) DATA_OH_HYD_LIGHT_PRIMARY_ENG_PUMP_FAULT_LEFT
They´re assigned in a way that the white light shows the switch-position (ON/OFF)
and the yellow light is on when the pump doesn´t work or is damaged
When Plane is powered up both lights act perfectly: white shows switch-position instantly
and yellow acts like in real life with the delay from the hydraulic system diagnostics!
Thanks for caring,
Alex
Thx
Steve
I forgot to write down that
action = ON to both LEDs
Value = 1 to both LEDs.
tried Action = ON GREATER THAN / Value 0.7 - to a fault led, made no difference, even with restart of SIM and GIT.
Pls. note my update: all Light functions are totally perfect during powered up plane (taxi, takeoff, inflight, landing). As soon as I shut down power all white ON lights switch off as they should, but the Yellow FAULTs stay powered up as they should not!
Thx
Alex
Best wishes
Steve
Happy Easter,
Alex
I have just raised a support ticket with the PMDG about this. The issue is that the PMDG SDK does not set the variables from 1 to 0 when the battery power is cut hence your lights stay on.
Best wishes
Steve
Alex