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.
Again and again "Registration Failed! 202 Exceeded Install Count"
I urgently need your help!
The facts: In 2016 I bought the GIT for FSX (version 3_6_5_1) Inv. # 603 and then mistakenly a second time in 2020 (version 4_5_1_2) Inv. # 2863 . Both versions were doing fine until last week. Then GIT was unable to connect to the simulator any longer (only the middle light was green, the left and the right one stayed red). Therefore I uninstalled GIT and thereafter downloaded the version 4_5_1_2 from my Pollypot account - no problems so far.
But after starting the program I was asked to complete the registration process by entering the (endless long) User Key available in my account. And so I did via paste and copy. But registration failed. GIT did not start. I got the message instead "Registration Failed! 202 Exceeded Install Count". Then I tried to start the older version 3_6_5_1 with its different User Key. In vain the very same way. As a German I have no idea, what "Registration Failed! 202 Exceeded Install Count" means. If this means "No Downloads anymore ..." it would be hard to understand: My account says 17 downloads left (new version) resp. 22 downloads left (older version). And every unsuccessful try costs me 1 more download option.
So dear sellers, please show me the way out of this mess. You can contact me via nighthawk2805@aol.com .
The facts: In 2016 I bought the GIT for FSX (version 3_6_5_1) Inv. # 603 and then mistakenly a second time in 2020 (version 4_5_1_2) Inv. # 2863 . Both versions were doing fine until last week. Then GIT was unable to connect to the simulator any longer (only the middle light was green, the left and the right one stayed red). Therefore I uninstalled GIT and thereafter downloaded the version 4_5_1_2 from my Pollypot account - no problems so far.
But after starting the program I was asked to complete the registration process by entering the (endless long) User Key available in my account. And so I did via paste and copy. But registration failed. GIT did not start. I got the message instead "Registration Failed! 202 Exceeded Install Count". Then I tried to start the older version 3_6_5_1 with its different User Key. In vain the very same way. As a German I have no idea, what "Registration Failed! 202 Exceeded Install Count" means. If this means "No Downloads anymore ..." it would be hard to understand: My account says 17 downloads left (new version) resp. 22 downloads left (older version). And every unsuccessful try costs me 1 more download option.
So dear sellers, please show me the way out of this mess. You can contact me via nighthawk2805@aol.com .
Comments
The yellow light will be down to the flightsimio WASM module not being in the Community folder. There are plenty of posts on the matter here in the forum.
Best wishes
Steve
I could start GIT normally now.
But I ended up at the very same point, that forced me to uninstall GIT a few days ago: I have eleven GoFlight hardware units installed and these all are running properly. But GIT is not recognizing any of these units as it did before the problems started. I assume, that this is probably not caused by the GIT, but by my computer's settings.
If someone has an idea, please let me know.
May be the FAQ will give a hint.
Regards
Claus
uninstalled and reinstalled GIT - and put its files inside the GoFlight folder (as recommended).
And GIT went to work again...