NBouc
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.
NBouc
Comments
-
Copy that. I'll leave it alone since it now works and later check my MSFS installation (even though MSFS has been installed there since august 2020) Have a nice weekend and thanks again.
-
TADAM !!! Everything is now working fine with GIT 4730. THANK YOU Steve ! Should the file Microsoft.FlightSimulator.SimConnect.dll have been installed when updating to GIT 4730 ?
-
That file was not in my Goflight folder, so I added it and GIT 4730 started. I'll start MSFS to see if my goflight modules are working ... standby.
-
Yes simConnect.dll is in Program Files\GoFlight and dated 29/11/2022 MSFS is up to date as yesterday (installed in F:\MS Flight Simulator)
-
If I do that, and after restarting GIT clean close it and copy back the LUA folder, as well as all the XML files in the Documents\GoFlight Interface Tool folder, this might work and bring back my configs ? UPDATE: I deleted Documents\GoFlight Interface Tool and got the same error when starting GIT clean.
-
Yes, I noticed that but I am familiar enough with Windows to have deleted C:\Users\MY USER NAME\AppData\Local\PollyPot_Software
-
Well ... it didn't work. After deleting C:\Users\\AppData\Local\PollyPot_Software, I have the same error message when starting GIT 4.7.3.0. Any other ideas ?
-
Thank you Steve for such a prompt update. I confirm that GIT 4.7.2.1 sees all my GF166 again. Well done !
-
Steve, I don't have the B738 yet, but GIT 4.7.2.0 only sees 1 of my GF166 (I have 3 of them) even though Windows 10 detects all 3. I re-installed GIT 4.7.1.0 and it sees all 3 GF166 again. I thought I would let you know in case others have the same problem. I am OK with GIT 4.7.1.0 for now, until I decide to buy the B738…
-
Here's the path: F:\WpSystem\S-1-5-21-2083512862-3558294711-2696691775-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\pmdg-aircraft-736\work My F drive is where I have the Community and Official folders installed. Worth noting that when I installed the B737-600, GIT 4.7 was already…
-
Hi Steve, GIT 4.7 is working fine for me in MSFS with the PMDG B736 (EFIS and MCP Pro). But I had to manually add [SDK] EnableDataBroadcast=1 in the 737_Options.ini file in the B736 Work folder. I have the MS Store version of MSFS installed on a dedicated drive.
-
I don't have the GF-LGT II but I noticed the same thing as you on my MCP-PRO and G166. GIT version 4.6.1.0
-
Steve, just in case it can help you troubleshooting the issue (wild guess here) ... I have the same error message when closing GIT and I noticed that the FlightSimIOLua.exe process is still running (was killed previously when closing GIT I believe). If it is not related, well no harm done ;-)
-
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…
-
Steve, thank you, thank you, thank you, thank you, thank you, thank you... Everything is now working fine with my EFIS and MCP Pro. Norm.
-
I too am waiting for GIT to support the NGXu for my GF MCP Pro and EFIS. In the meantime, to my great surprise, using the VC's MCP with the mouse is not as bad as I remembered ... but still not as natural as my MCP Pro.