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.
GIT 3.3.0.1 not working with P3D v4
Hi Steve,
I just purchased a new monster computer for P3D v4 and my combat flight sims. GIT 3.3.0.1 is not working with the new set up. I have the GF MCP, LGT II and two GF EFIS units. I used a previous GIT version successfully with P3D 2.5 on my old machine with the previously mentioned hardware. I'm using the latest software versions for everything including the PMDG 737NGX. GF CONFIG seems to allow basic functions but GIT simply won't respond. Incidentally, I have the latest version of FSUIPC (registered) and TrackIR is also not running. I've installed the latest P3Dv4 SDK and run the Simconnect client as well. Nothing. Your help will be greatly appreciated!
I just purchased a new monster computer for P3D v4 and my combat flight sims. GIT 3.3.0.1 is not working with the new set up. I have the GF MCP, LGT II and two GF EFIS units. I used a previous GIT version successfully with P3D 2.5 on my old machine with the previously mentioned hardware. I'm using the latest software versions for everything including the PMDG 737NGX. GF CONFIG seems to allow basic functions but GIT simply won't respond. Incidentally, I have the latest version of FSUIPC (registered) and TrackIR is also not running. I've installed the latest P3Dv4 SDK and run the Simconnect client as well. Nothing. Your help will be greatly appreciated!
Comments
Thx
Steve
Off to lunch! Thanks.
A couple of other people have had issues with the NGX and P3Dv4 over the last couple of days. I know a Windows 10 update has caused problems for some flight simmers and maybe this has impacted GIT with the NGX. I will investigate and come back to you and the others.
The directory is correct for P3Dv4 as its a 64bit application.
Best wishes
Steve
Best wishes
Steve
There was mention in the post about FSUIPC. I AM running FSUIPC 5. The post mentioned it being compatible with certain settings. Is it even necessary? If so, what settings constitute compatibility?
Thanks,
Terry
Thx
Steve
Best wishes
Steve
Thanks Steve!
1. The latest GFConfig software won't retain the path to P3Dv4. It has to be entered every time.
2. Issues with the latest GIT are that no settings can be saved. Unlike my previous version, GIT requires the data bridge to be running in order for anything to work. On old machine, data bridge had to be running when GIT was started but shut down after it was started in order for LGT II to work.
3. All devices have to be enabled every time GIT is started. Settings can't seem to be saved on SETTINGS tab.
4. Detector button is grayed out on STATUS page. Hitting RESTART button causes SimConnect button to turn yellow and everything has to be restarted from scratch, P3D included.
Incidentally, I was also having trouble with my Saitek Radio Panel AND TrackIR not working. I installed older versions of the software for those units and they work fine now. Thoughts with regard to latest GIT?
Terry
2) GIT does not need the data bridge at all. It could be that the hardware is being driven by GoFlight Drivers because you haven't set everything to Compatible Add-On in GFConfig.
3) Change something on the Settings tab, quit GIT and see if it has been saved.
4) Detective will not enable for PMDG aircraft. Try the default baron and if it doesn't enable, the Goflight Interface Module.dll is not running - check its entry is in dll.xml.
Best wishes
Steve
I was unaware Detective would enable with PMDG. Makes sense. I'll check it with a Baron.
Thanks!
Best wishes
Steve
One step forward, one step back. GIT is working beautifully with NGX. However, that's only airplane anything GF is working with! I've tried running GFConfig only with the Baron, with and without the GIT, data bridge on and off. Nothing. I've shut everything down, restarted and cold-booted the computer. Again, nothing. GIT shows the generic Baron loaded. I've clicked on each hardware tab and enabled them. I've hit the RESTART button on the Status tab and get all green lights but to no avail. Detective CAN be selected. I don't understand how everything WAS working at 2am this morning and now it isn't. The biggest frustration is that I'm running a very expensive new computer that's only been up and running now for about 10 days and 90% of my time has been spent trying to get this GF stuff running. I'm on vacation and NOT having fun! It's time to focus on something else for a while.
Thanks,
Terry
I have been quite busy with my job as a 737 pilot lately and haven’t spent much time with the PMDG 737 or the latest version of GIT. I am between trips today, leaving in about an hour for another 3 day trip. I spent some time this afternoon uninstalling/reinstalling GF Config and the latest GIT version and, as has been the case for months, I’m having little success getting GIT to work. Since my last message, I have installed P3Dv4.1. It seems that I have new GF/GIT issues every time there’s some new update. My frustration level with this hardware/software is through the roof! I am just before unplugging it all and putting it up for sale. With regard to my GF/GIT/PMDG combo, I spend more time trying to get it all working than I do flying. My alarm just went off to start getting ready to go to work. I know this is a vague message but I hope you can understand my frustration. I have a lot of money tied up in this setup to have it not work AT ALL.
I will have 11 days off starting Friday. I will be mentoring a pilot on Friday who’s returning to work after 3 months of medical leave. I’ll be doing so WITHOUT the benefit of my GF hardware. With the stretch of time off coming up, I’d like to get this hardware/software working once and for all without the constant issues. If I can’t, I’ll sell it.
Your help will be greatly appreciated!
Sincerely,
Terry
The issue is due to LM. They appear to have broke SDK compatibility with the post hotfix versions of P3Dv4 which then broke GIT because it uses LM's previous 32Bit SDK's . Therefore I have released a 64Bit BETA version of GIT for P3Dv4 only that should fix your issues.
I feel your pain. P3Dv4 has been a PITA for me and many others and has cost me a small fortune in tracking down bugs, issues, support and redevelopment.
If your system is critical for you I would strongly suggest avoiding P3Dv4 and going back to P3Dv3 or FSX SE as I have decreasing levels of confidence in the reliability of P3Dv4 whilst LM settle down the product.
Best wishes
Steve
I certainly understand your frustration regarding LM. When P3Dv3 was released and LM announced that the new version would require a full-price purchase for all previous users, I decided that I wouldn’t buy another version until a 64-bit version came out. V4 was released and I bit the bullet. I’m very happy with v4 despite the fact that my GF hardware is little more than $1500 in useless junk now.
I use P3Dv4 for fun as much as I use it for personal training and mentoring. It’s highly unlikely that I’ll return to a previous version. VR will give me more incentive to sell most of my hardware anyway as it will be difficult to use wearing the VR goggles. In the meantime, I’ll keep my eye out for updates to GIT.
Incidentally, I downloaded the latest 64-bit GIT. I flip one switch on the MCP (i.e. Capt FD Switch) and that switch will also move in PMDG. After that, nothing happens. I’ll work with it more once I start the stretch of upcoming days off.
Thanks again,
Terry
Ouch! I sure hope we can get this sorted out or I have the same "junk"
Thanks for resetting the install count for me the other day.
As always seems to be the case with the installation of any new GIT version, I seem to be right back to square 1 with hardware not working. DoOver2021;-) I have the MCP PRO, EFIS (2x) and LGT ll. I’ve uninstalled everything including the GF Config and reinstalled. GF Config recognizes all modules and all are set to Compatible Add-ons where appropriate. Using this with P3Dv4.5, Win 10. GIT seems to recognize only the LGT ll but not the other modules. All tabs are grayed out except STATUS, SETTINGS and LOG. SimConnect is yellow (not sure how to or if I need to reinstall it).
With training I mentioned previously approaching, I really need to get this hardware up and running……again! I only use this hardware and the PMDG 737 once a year for training prep. Not sure how or why I so often seem to have trouble with it when training time rolls around. As always, any help will be greatly appreciated.
Terry
Best wishes
Steve
I’m actually on a trip at the moment and will be home on Sunday night. I AM running the latest 64bit version of GIT (4.5.1.2 if I remember correctly) for P3D and the above-mentioned DLLs are present. So that I’m sure I’m not wasting time once home, how do I extract the log? Copy and paste?
Incidentally since my Nov 2 post above, I have tried unplugging and re-plugging in the USBs while P3D and GIT are running. The result is that my EFIS and LGT ll panel tabs become active and I’m able to ENABLE them but they don’t respond. The MCP PRO panel tab remains grayed out and unselectable. On the Status page, all GoFlight hardware appears to be connected.
It may be Monday before I can get that log posted. Thanks for your response!
Regards,
Terry
I'm home and on "staycation" for the next 10 days.
I do have the above-mentioned DLLs in my GoFlight directory. Still looking for how to post log (yeah, I'm that thick😉).
Thanks,
Terry
Best wishes
Steve
I was trying to do that with the mouse and couldn't make it happen. Log attached. Standing by.
Thanks,
Terry
Best wishes
Steve
There only appears to be one such entry in dll.xml. Picture attached. Incidentally, in that folder there are three files I’ve never noticed before: dll.xml.GIT0, dll.xml.GIT1, and dll.xml.GIT2. Assuming those should be there. I tried unplug/replugging in hardware this morning and for the first time got the MCPPRO tab to “un-gray”. I enabled device 0 in that tab but nothing responded. Also, only one EFIS panel “un-grayed” and also didn’t respond. The other EFIS panel and LGT ll did not. In both cases above, no switches or knobs worked. Oddly enough, the same excercise yesterday got everything working EXCEPT the MCPPRO. No consistency.
Eager to get this hardware working again so I can start training prep!
Thanks, Terry
Configure GFConfig P3D tab as necessary. Load up the beech baron and get to the VC. On your MCP PRO tab, click Default FS and then enable Device 0 on the same tab and see if the MCP works OK (you may need to move the rotaries to get the displays to refresh initially).
Best wishes
Steve
Surprisingly, everything is now working and it was a simple fix. I have two 10-port powered USB hubs. All my GF hardware is plugged into one and everything else is plugged into the other. I simply swapped the ports that the powered ports were plugged into. Strange but simple fix.
I do have a couple of lingering issues, one GIT-related and the other not exactly. First the “not exactly”. For some reason, every time I restart P3D, the sim attempts to auto-assign a number of actions to all my various hardware. I use FSUIPC almost exclusively to assign non-GF hardware buttons and axis so that I can assign on a per-airplane basis. These auto-assignments conflict with FSUIPC assignments and have to be manually removed, which is quite time consuming. I will try unplugging my combat-related hardware and see if that stops it. In the meantime, would you know of a more permanent way to stop the auto-assignments?
Second, in previous versions of GIT the trim rotary knobs on the LGT ll, namely the aileron and rudder trim knobs, had the capability of inputting a quick “bump” of the NGX trim with each click of the rotary. I can’t seem to find a setting that does that. One click of a rotary knob causes the NGX trim to be held and not released. Rotating one click back releases the NGX trim. The problem with that is that it’s very easy to click and hold in the other direction, creating havoc when practicing engine out procedures. Is there a way to get back to “one click, one bump”?
Sorry to be such a pain but I really do appreciate your help! You’re a godsend to those of us who own this aging hardware!
Thanks,
Terry