I have the previous version of the ICCS that has the extra GF-46 that I have programed for DME1 DME2 and ADF. Every so often when I enter FSX the display is blank. If I go into GF Config it lights up as I select the module but the only way to get it to work in FSX is to reboot my computer.I think that there may be a glitch in GFDev.dll (the bridge from GF Config to FSX) that somehow doesn't send the information needed to activate the GF-46. Rebooting seems to "reset" the bridge.Anyone else having an issue with one or more of their modules not showing up or have an idea as to why it's doing this?ThanksAlan

I have the previous version of the ICCS that has the extra GF-46 that I have programed for DME1 DME2 and ADF. Every so often when I enter FSX the display is blank. If I go into GF Config it lights up as I select the module but the only way to get it to work in FSX is to reboot my computer.I think that there may be a glitch in GFDev.dll (the bridge from GF Config to FSX) that somehow doesn't send the information needed to activate the GF-46. Rebooting seems to "reset" the bridge.Anyone else having an issue with one or more of their modules not showing up or have an idea as to why it's doing this?ThanksAlan

I've got a couple of GF-46's along with several of their other modules. The only problem I ever have is with the GFDev software not properly unloading when the sim crashes. Provided the flight ends as expected, all the modules start up properly the next time I load the sim, regardless of restart. What OS are you running?

I've got a couple of GF-46's along with several of their other modules. The only problem I ever have is with the GFDev software not properly unloading when the sim crashes. Provided the flight ends as expected, all the modules start up properly the next time I load the sim, regardless of restart. What OS are you running?

BillI'm running WIN7 64. I am aware of the issue with the GFDev not closing so make sure it closes after FSX.Alan

Just kill the data bridge process in Task Manager after an FSX CTD. No need to reboot your PC.Cheers,- jahman.

Just kill the data bridge process in Task Manager after an FSX CTD. No need to reboot your PC.Cheers,- jahman.

Yep, that's what I do. You don't even have to go to the task manager, just left-click on the GFDev icon in the system tray and choose "exit". Of course, none of this solves the OP's problem.

Yep, that's what I do. You don't even have to go to the task manager, just left-click on the GFDev icon in the system tray and choose "exit". Of course, none of this solves the OP's problem.

Good point, thanks for the tip!Cheers,- jahman.

Just kill the data bridge process in Task Manager after an FSX CTD. No need to reboot your PC.Cheers,- jahman.

I think you missed my point. I don't have a CTD -- after a successful flight I shut down FSX, GFdev closes okay but the next time I fire up FSX the one GF-48 is blank. The other GF-48 that is the XPDR is fine. If I go into GF Config and highlight the particular GF-48 it lights up just fine however the only way to get it to work in FSX is to reboot. I somehow think that GFDev is not passing the information to FSX.

Yep, that's what I do. You don't even have to go to the task manager, just left-click on the GFDev icon in the system tray and choose "exit". Of course, none of this solves the OP's problem. spotlope

Exactly spotlope. Alan

No idea then what could cause your problem, but jusst in case make sure you're running the latest driver (v. 2.02, June 2011).Cheers,- jahman.

Just picked up on this topic because I have exactly the same problem as the OP. I've been running my GF46 (and a bunch of other GF modules) quite happily for years on an XP64 system. Just recently I bought a new W7 64 system and everything ran fine for about a week, and then I started seeing the problem as described. At that time the GF46 was connected via a hub, so I hooked it up direct to a native USB port, but the problem persists. I'm speculating it may be hardware, but this thread has me wondering. I will check I have the latest driver, and will ensure GFDev ends properly (that was something I wasn't aware of), but I think both of those are OK. I didn't have any CTDs (yet !)Was this problem eventually resolved ? And if so, how ?CheersDick B

I've have all the GoFlight modules including two GF-46's. I don't really have a solution for you except to tell you that the GF-46 module is WEIRD! Sometimes it plays nicely with my system and sometimes it's weird (no other word describes it). I run Win7 64-bit and FSX Accel. Sometimes the display is blank and sometimes it is not.I can tell you that connecting ALL your GoFlight modules to powered USB hubs is a hard requirement. You might get away with just plugging them in to a USB port on your computer but these modules WILL NOT work properly just plugged into a non-powered USB hub. I have seen every one of these modules work improperly when using non-powered hubs. The LED's might work but the functions will definetelyi be flakey.fb

Thanks for that fb ! Weird is definitely the word. The GF46 ran fine for years on my XP system, where it was indeed hooked up via a powered hub (where curiously the GF46 was generally OK, but other devices would occasionally 'disappear' occasionally !) I hooked it up the same way on the W7 system, but when this problem started I immediately suspected the hub and moved the module to a native USB port. After your comments above I will move it to a new Belkin powered hub I just installed and see if that makes any difference. The way it is at the moment, it seems to work only if I boot and then configure it via GFDev and then fly. But if I close FSX and start it again, the GF46 is out to lunch, and I have to go through the whole routine again. It also seems not to be keen on me cycling through the panels - after a short while it just gives up and displays a row of dashes.I did find out though that I am running on a back level GF software (1.93). The GF site, which is down for maintenance, says the latest is 2.03, but my AV software says the download link is dodgy, so I may have to give them a call.Don't you just love computers ?

Well, I plugged the GF46 in via the Belkin powered hub. It failed on the first flight, but seems to have worked since.I'd still like to update my GF software. I see elsewhere that some have had problems with the latest level (2.03). Is there anyone out there who could send me 2.01 or 2.02 ?

I hope I'm not speaking too soon, but I think I may have solved the problems with my GF46, thanks to some good advice from the folks at RC Simulations (thanks guys). I'm on new hardware and a new system (W7), and they pointed out to me that the USB ports may well be set to switch off automatically to save power. They were, so I changed them in Device Manager, and now my GF46 comes up with FSX every time and stays up. Simple when you know how !Curiously, the other GF modules I have didn't seem to suffer the same way.

Edited February 11, 201214 yr by DickB

Well, I did speak too soon ! It's not (just) the USB port power switching off (that's now fixed, and this problem happens even on the same powered hub as other devices which are fine). Somehow the GF46 just 'drops out' for some reason, and isn't even seen in GFConfig, let alone GFDevFSX. Unplugging/Replugging it gets it recognised again in GFConfig, and then if FSX is started pretty soon afterward, it gets recognised there and works properly. It never 'drops out' during a flight (so far !)It's very much as if it goes to sleep if no-one talks to it for a while and never wakes up until you kick it. This never used to be a problem, so I'm beginning to suspect hardware again.

Just catching this thread and have to chime in. I have the very same issue with a (Gray) GF46 I purchased a few months ago! Exactly as you have described. I've tried different USB ports, new powered hubs, all the W7 64Bit settings, etc. and still it sometimes will not function. I can unplug/plug the USB cable, then it will go, but who needs that? Meanwhile, my original (black) GF46 works fine, so...