FSUIPC and GoFlight Modules w/Windows 11

[Carob]

Hello.

I've come here for questions regarding the subject listed.  I am working with my father after him getting a new computer that is running Windows 11.  He is coming from Windows 7.  He has several GoFlight modules and after much research have failed to get them working in both FS9 and FSX.

My understanding is that the 2 main solutions for this issue is either using FSUIPC or the GoFlight Interface Tool from Pollypot.  However, the Pollypot tool, according to them, does not work for FS9.  I guess that leaves me with FSUIPC.  That is of course FSUIPC still works for this purpose on Windows 11.  Perhaps that's the first question someone can answer for me.

Assuming the first is true, the second is a bit more involved.  From what I've read, it seems to require a masters degree in programming to be able to accomplish getting all of this to work.  I was hoping someone would be willing to walk me through, possibly even doing a remote session with me, to help out as I've started to read about this a few times and am lost almost from the beginning.

If anyone can answer the first question, that would be a start.  Again, assuming the answer to that is yes, I'd greatly appreciate some assistance with the second.

Any and all help would be GREATLY appreciated.

Gary

[John Dowson]

FSUIPC3 is compatible with the FS9.1 update (which was made available on October 9th 2004) but not FS9. FSUIPC3 is now available for free - see https://fsuipc.com/. But be aware that FSUIPC3 is no longer supported. For Go Flight modules, you need to use the FSUIPC 32-bit GoFlight drivers, available from the same location - just copy the dll to your FSUIPC3 installation folder. Note that I have never used FSUIPC3 (before my time!) but I believe the GF driver should also work with this version.

For FSX, you will need a registered copy of FSUIPC4, and also the 32-bit GF driver.

There is certainly no issue running FSX/FSUIPC4 on Windows 11. If FS9.1 also runs on windows 11, then so should FSUIPC3 (as it is an embedded dll) and the GF drivers.

John

P.S. GF devices are also supported by FSUIPC's lua interface. Lua scripts will be needed to support any GF devices that have displays. See the User Contributions section of this forum for some lua scripts for GF devices.

Edited September 2 by John Dowson
PS added

[Carob]

Hello, John.

Thank you for the information posted.

Yes, I am referring to 9.1.  No issues there.

However, I'm confused by the rest of what you wrote.  To make the conversation easier at this point, if we just stick to talking about FS2004, I'm not sure where I need to go next.  The GF driver on your site is actually older than the one currently installed with the GF software.  Maybe that's important, maybe it's not.  But, if I take either and drop it in the FSUIPC install folder, there is still more that needs to be done, correct?  I'm assuming this is where the document comes in for the GFDisplay 1.30 software that I don't understand.  If so, I guess that's what I was hoping for help from someone on.  I can't make heads or tails of what's supposed to be done there.  (Hence my statement about a masters degree.  🙂 )

I also don't have any idea what you are referring to for lua.  You say the GF devices that have displays on them (a couple of those are involved) require this.  But I don't know what that is or what is required for it.

After weeks of trying to get things to work, and failing, my brain hurts and am hoping someone might be wiling to have an actual conversation about all of this to help me figure out what I need and what I don't.  And once I have that info, I'll need to know how to go about attempting to configure things to see if it actually solves the problem or not.

[John Dowson]

16 hours ago, Carob said:

Yes, I am referring to 9.1.  No issues there.

No issues? You said: "after much research have failed to get them working in both FS9 and FSX"?

16 hours ago, Carob said:

To make the conversation easier at this point, if we just stick to talking about FS2004,

Ok, but this is thew first time you have mentioned FS2004. As far as FSUIPC is concerned, FS2004 is the same as FS9 - you need FSUIPC3.

16 hours ago, Carob said:

The GF driver on your site is actually older than the one currently installed with the GF software. 

Sorry, but this is not possible. The current/latest 32-bit GF driver is (file) version 2.2.2.1 (or product version 2.22, a bit confusing..) from January 2013 - what version are you using?
And if using the FSUIPC GF driver (GFDev.dll), you do not need any other GF drivers or software - remove these.

16 hours ago, Carob said:

But, if I take either and drop it in the FSUIPC install folder, there is still more that needs to be done, correct? 

Of course! Once the GF driver is installed, this will make your GF buttons/switches visible to FSUIPC, where you then need to assign your buttons/switches, as you would with any other device/controller.

16 hours ago, Carob said:

I'm assuming this is where the document comes in for the GFDisplay 1.30 software that I don't understand. 

The GFDisplay driver is another additional program that uses FSUIPC and the GoFlight driver (GFDev.dll) and is used for driving displays,

16 hours ago, Carob said:

If so, I guess that's what I was hoping for help from someone on.  I can't make heads or tails of what's supposed to be done there.  (Hence my statement about a masters degree. 

Start with just FSUPC3 and the 32-bit GoFlight driver (GFDev.dll) and try and assign some buttons/switches. Once you have that working, then add in the GFDisplay program and read the manual to use this.

16 hours ago, Carob said:

I also don't have any idea what you are referring to for lua. 

Lua is a programming/scripting language. FSUIPC has a lua interface and additional lua libraries that allow you to write lua scripts that interface with the FS and FSUIPC, and allows further access to GF devices via is gf library. Please see the documentation provided by FSUIPC3.

16 hours ago, Carob said:

After weeks of trying to get things to work, and failing, my brain hurts and am hoping someone might be wiling to have an actual conversation about all of this to help me figure out what I need and what I don't.  And once I have that info, I'll need to know how to go about attempting to configure things to see if it actually solves the problem or not.

I don't understand why you are having so much difficulty...
First, install FSUIPC3 and the 32-bit GFDriver and take a look at the documentation that comes with FSUIPC3. Read the Installation and Registration guide, which will tell you how to install and register,  then the User guide, and also take a look at the Advanced User guide and the Lua Plug-Ins document. This should give you an overview of the functionality available  and the knowledge to program/assign your GF buttons/switches/rotaries.
Once you have that working, then look into adding GFDisplay to control your displays.

And please note that:
    - FSUIPC3 is provided free-of-charge but is unsupported. This is very old now, I have never used it and have no access to the source
    - I do not have any GF display devices and have never used the GFDisplay program so cannot really help with this
    - I don't have and have never used FS9 or FS2004

What GF devices do you actually have? You can also try searching these forums for advice and possibly lua scripts for specific devices.

But I really don't understand why you/anyone would want to continue using FS9 or FS2004. You should consider updating to either MSFS2020 or P3D (v5 or v6), or at least FSX (but this is also very old now!).

[Carob]

No issues in terms of the the sim itself running in Win 11.  I have that going.

 

I am aware FS9 and 2004 are the same thing.  Thought we were on the same page there.  Sorry about that.

 

The GFDev.dll file is currently in the GF software folder as that's where it puts it.  The GF software itself works fine.  It can be used to program the units without issues.  The problem is FS9 does not see them and they just sit there mocking the person wanting to use them.  🙂

 

Some of the GF modules being used do have displays.

 

I've read the manual for GFDisplay.  I don't understand it.  Again, masters degree in programming required.

 

I don't understand either.  I am certainly not the only one who has run into this.  There are tons of topics across multiple sources with people having these issues.  The GF modules were not designed to run on modern operating systems nobody has re-written the code for them to work.  With FS9 at least.  There is software from a company in England that half-way took over the stuff, but the software they have does not work with FS9.  Only FSX and above.

 

FSUIPC is already installed, but not registered.  Has been for many years.  You said the version for FS9 does not require payment for registration anymore?  How do I go about getting a key to enter?

 

Long story about sticking with FS9.  I am also certainly not the only one in that regard either.  My hope was to find one of those people who are also (somehow) successfully using it along with GF modules who would be willing to help.  Because I, and from what I've found MANY others, are having one hell of a time.  That aside, I was also hoping for help from the people who run this forum (who I thought you were one but perhaps I'm mistaken) for assistance with the FSUIPC side of the house and how to program the GF devices.  As stated, I have read all of the required info and still haven't a clue on how to proceed.  Especially since some of the modules have displays and some are just the push buttons or switches.  Going back and forth via e-mail (post) is not going to help me here.  Obviously.  Was hoping someone would be willing to to join a remote session possibly to assist.  I understand that might be pushing it, but it's kind of my only hope now.

[John Dowson]

10 hours ago, Carob said:

The GFDev.dll file is currently in the GF software folder as that's where it puts it.  The GF software itself works fine.  It can be used to program the units without issues.  The problem is FS9 does not see them and they just sit there mocking the person wanting to use them.  🙂

Sorry, but it seems that you have either not read my previous comments or have not understood them. I have no idea why you would want to put the GFDev.dll in the GF software folder - it goes in the FSUIPC installation folder (i.e. in the modules folder under your FS installation.

And you have to choose between using FSUIPC doe your GF devices or the tools provided by GF. If using FSUIPC, you should NOT use any GF drivers - uninstall them and let windows install default drivers, And do not use/run any GF tools - you only need FSUIPC3 and the FSUIPC GF driver.

10 hours ago, Carob said:

Some of the GF modules being used do have displays.

I've read the manual for GFDisplay.  I don't understand it.  Again, masters degree in programming required.

Again, please see my previous comments. There is no point in even looking at GFDisplay until you have FSUIPC working with your GF devices. And you need to understand how to use FSUIPC3 before toy can start with GFDisplay. Gave toy read the documentation for FSUIPC3, as advised?

10 hours ago, Carob said:

FSUIPC is already installed, but not registered.  Has been for many years.  You said the version for FS9 does not require payment for registration anymore?  How do I go about getting a key to enter?

Well, if its not registered then nothing is going to work, Details of the FSUIPC3 key are available on the fsuipc website (https://fsuipc.com/).

10 hours ago, Carob said:

That aside, I was also hoping for help from the people who run this forum (who I thought you were one but perhaps I'm mistaken) for assistance with the FSUIPC side of the house and how to program the GF devices. 

I do NOT run the forum (that is SimMarket). I support FSUIPC, versions 4, 5 and 6, As I said, FSUIPC3 is unsupported, but I can help you where I can...

10 hours ago, Carob said:

As stated, I have read all of the required info and still haven't a clue on how to proceed. 

But you haven't! You seem to have not even read my previous comments, let alone any of the required documentation, i.e. the documention that comes with FSUIPC3, NOT the GFDisplay documentation. And as I have already said, you proceed by installing AND registering FSUIPC3 (which you haven't done..), then you install the GFDev,dll in the correct place (which you haven't done), and then you test and program/assign your buttons/switches/rotaries. Only once that is done and you understand the basics if using GF devices with FSUIPC, then start looking at GFDisplay and/or lua scripts to control the displays.

10 hours ago, Carob said:

Was hoping someone would be willing to to join a remote session possibly to assist.  I understand that might be pushing it, but it's kind of my only hope now.

That is certainly not going to happen and is not necessary. Just read my comments and follow my advice, You seem to be ignoring almost everything I am saying, which is why you are having so many issues. Read my comments and follow my advice - if you can't do that, I cannot help you.

John

[John Dowson]

I have just taken a look at the GFDisplay documentation, and in the first pages, under Installation and Configuration, it says:

Quote

You will need version 3.465 of FSUIPC, or later, and preferably 6.465 of WideFS, or later. It will work on clients with earlier versions of WideFS, but not as well. You will need to be a fully registered user of FSUIPC to use GFdisplay on the same PC as FS—but then you must have full user registration to use the GF button programming in FSUIPC in the first place, and this present program merely complements that facility.

Did you not see this? i.e. nothing is going to work if you are using an unregistered/unlicensed version of FSUIPC3, which you seem to be doing for some reason, even though the license is freely available.

I repeat, READ THE DOCUMENTATION.

John

[Carob]

The GFDev.dll file is in the location mentioned because that is where the GF software puts it.  That is the software that has been used to program the hardware previously.  I have not yet done anything regarding FSUIPC and GoFlight.  That's why I came here.  To hopefully get more information and assistance with doing that.  I can't attempt to do anything until I know what to do with it and how it works.  That's just some of what I'm trying to find out.

 

---------------------------------

 

FSUIPC is not currently registered because it has never needed to be.  I do (now) see the key information on the site.  Missed that before.  Sorry.  However, I still need to understand what to do after that.

 

----------------------------

 

Correct, as mentioned, I have not yet done anything with FSUIPC and GF because I need to understand how it works first.  Once I know that, I can proceed.

 

----------------------

 

I am actually reading everything you are saying.  The issue is that I need to walk before I can run.  Programming these GF modules using FSUIPC appears to be not at all like using a GUI to do that and requires some programming knowledge.  Of which I, nor the person who is actually using this system, actually have.

 

---------------------------

 

While it might be great to get direct assistance from yourself, that wasn't a necessity.  My initial post was a generic one for anyone who was using the same products to possibly help because I was stuck.  I think the frustration you have is because perhaps you don't understand what I'm trying to accomplish before actually jumping in to start installing things and pushing buttons as it were.  Perhaps I'm just not seeing it, but I don't see anything in the FSUIPC documentation about how to actually configure the GF devices.  Once of course the product is registered, the .dll is where FSUIPC needs it to be, etc.

[John Dowson]

12 hours ago, Carob said:

The GFDev.dll file is in the location mentioned because that is where the GF software puts it.

As I have said, you have to choose between the GF software and FSUIPC. If you want to use FSUIPC to control your GF device, then follow the instructions for FSUIPC.

12 hours ago, Carob said:

FSUIPC is not currently registered because it has never needed to be.  I do (now) see the key information on the site.  Missed that before.  Sorry.  However, I still need to understand what to do after that.

I have told you what to do several times now, and  there is plenty of documentation which you seem to be ignoring.

12 hours ago, Carob said:

Correct, as mentioned, I have not yet done anything with FSUIPC and GF because I need to understand how it works first.  Once I know that, I can proceed.

Again, then read my posts and the provided documentation and try things.

12 hours ago, Carob said:

I am actually reading everything you are saying.  The issue is that I need to walk before I can run.  Programming these GF modules using FSUIPC appears to be not at all like using a GUI to do that and requires some programming knowledge. 

If you think this then you have not read the documentation correctly and have not tried to assign anything to your GF devices yet. Why don't you try this? Once FSUIPC is registered, you will have visibility of the buttons/switches assignment panel, which is the UI you used to  assign your buttons/switches, and is described in the user manual. No programming is required, although some advanced features may require manual editing of the FSUIPC ini file, which is also described in the user manual).

12 hours ago, Carob said:

Perhaps I'm just not seeing it, but I don't see anything in the FSUIPC documentation about how to actually configure the GF devices. 

Because there is nothing specific or special about a GF device - it is just another controller. You assign the buttons/switches/rotaries as you would with any other controller. The FSUIPC GF driver (GFDev.dll) just makes the GF device visible to FSUIPC, where it is then treated like any other controller. There is no distinction between any other standard USB controller and a GF device, except that the additional driver is needed for GF devices.

I don't understand why you keep posting the same questions, which I have answered many times, and don't just go ahead and try things...at least register your FSUIPC3,  install the GF driver and go to the button assignments panel and try and assign to your GF devices. Please do not post again until you have at least tried that. Once you have some hands-on experience, things will hopefully make more sense....

[Ray Proudfoot]

@Carob, do yourself and your father a favour and ditch FS9 / FS2004. Buy P3Dv5 (not 6) for around 50GBP.

I have several GoFlight units - MCP Pro, EFIS, T8, P8 , GF166 and a LGT. All nearly 20 years old and working perfectly with Windows 11.

Firstly, they must be connected to USB2 ports. USB3 are meant to be backward compatible but it can be unreliable. Modern motherboards don’t have USB2 ports but they do have USB2 headers.

I bought this from Amazon. Xiatiaosann 2 Pack 2 Port USB 2.0 Rear Panel Expansion Bracket.

It connects to USB2 Header on my mobo. Then I bought a powered USB2 hub (backward compatible USB3) should be okay. Plug your GoFlight units into the hub that’s plugged into one of the ports on the expansion bracket.

All my units work perfectly. And the scenery is transformed in P3Dv5. Get an Academic Licence. That’s fine. I hope you read this and haven’t given up.

I also use the Pollypot software which has a bit of a learning curve but is very good.