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.

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.

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.

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

Holy crap, dude. I was only asking for a little help. Sorry I don't measure up to your predetermined IQ qualifications.

But one number is for using the Cntrl key, which I don't want to use, and another was for the actual key. With a comma between then. I found that line in a post someone else had done for helping in a similar situation. I don't understand it. Is the comma mandatory? Can just one number be used? Is the syntax different with just one number? I'm not a programmer so have no idea what it's supposed to look like.

I did. But can't figure out what the line needs to be to do what I want.

I had looked in that manual but still wasn't sure what to put. That's why I posted here.

The paid version is needed for that, correct? I don't have that. I was told this is for Cntl + X AdvDisplayHotKey=88,10 so I tried it and it worked. I just don't want to use Cntl + X. I have a button on the yoke to invoke the "`" key for the default ATC but am looking to use that button for the AdvDisplay window for use with RadarContact.

Hello. Can someone possibly tell me what the entry would be to put in the FSUIPC.ini file to use the "`" key (default ATC key in FS9) to show/hide the AdvDisplay window? Or, can someone tell me what the line would be to just configure Button 1 on the CH Yoke to do the same thing? I can't quite figure it out from the manuals, etc. Thanks!

Well it doesn't seem to be the drivers and I don't know what DirectSound is. I think all we're looking for here is a solution. Which nobody, in multiple forums, seems to know.

Are older version of FSUIPC available somewhere? I don't see them on Pete's site. I'd like to try a couple of older versions ofr FSX to see if something broke in that along the way somewhere.

Yep.

Hello. I wanted to jump in here and say that this same issue is happening with my father's new Jetline system he just got. When FsRaas is running it shows connected. When taxiing to a runway FsRaas says "Approaching" and that's all. Different airports, different runways, different aircraft... that's all that happens. No other sound is heard the entire time. If everything is quit and started again, the exact same thing happens. Only the very first word FsRaas is trying to play is heard and nothing more. FSUIPC 4.937 with FSX. Using FSUIPC 6.995 with FS9 and it works fine there. I too am searching for an answer to this but so far have come up empty.

This could be a little difficult to work on now. I was doing some work on my father's computer as I was visiting for the holidays. Unfortunately I am back home now (another state) but I will see if I can get this information and get back to you. It might be a little while (if at all) but I will see what I can do. Thanks for your help so far!