Hello all,

I am having a pretty frustrating problem right now. I’ve tried a number of fixes, including updated drivers, a different HUB, and even purchasing the power adapter for the Saitek.

 

But, about 30 minutes into a flight, usually about the time I start my descent, the controller disconnects from the computer, just enough to make FSX stop recognizing it.

Any suggestions would be great. Here are a few more details:

Windows8 Pro

FSX with all available SP’s and updates

Latest drivers on all components

PMDG and FSX Basic aircraft (Mostly PMDG)

Saitek does come back, but only to Windows, not available to FSX without restarting FSX.

If anyone suggests using FSUIPC, I’d love to if: I could figure it out, and it doesn’t cause issues.

I am not running anything off of C, and I am using compatibility mode (Win 7 and XP)

 

Best,

Brad

There is a long thread in the Win8 forum on this. Don't think there is any proven answer.

 

scott s.

.

I have read that thread, but I believe this to be a software issue, or potentially a driver issue. I don't think that this is a hardware issue (as that has been ruled out). Perhaps FSUIPC would fix it, as in using it to take the Saitek inputs for FSX... Or, perhaps there are software debugging tools that folks are aware of that can help... I am not 100% sold on Windows8 being the issue, unless there was an update that broke things, as may be the case with this issue popping up recently for all other involved.

The problem is that Windows 8 installs default (windows certified) drivers. And when you install the drivers from the Manufacturer it will not install them as they are not certified. You must uninstall the default Windows drivers and then install the drivers from your vendor manually. This is all outlined on the Mad Catz web site.

 

I've done this 2 months ago and have not had a disconnect since. Prior to that I was getting disconnects every 15 minutes.

 

Regards

jja

Are you using any USB 3.0 connections? If so, move everything to do with Saitek to USB v2.0 connections.

 

Ray

The problem is that Windows 8 installs default (windows certified) drivers. And when you install the drivers from the Manufacturer it will not install them as they are not certified. You must uninstall the default Windows drivers and then install the drivers from your vendor manually. This is all outlined on the Mad Catz web site.

 

I've done this 2 months ago and have not had a disconnect since. Prior to that I was getting disconnects every 15 minutes.

 

Regards

jja

 

jja

I have earched the Mad Catz web site but cannot find any reference to it. Any chance of link, I want to find out how to uninstall the defaut Windows drivers. Many thanks.

 

John

I want to find out how to uninstall the defaut Windows drivers

 

Open up the Device Manager - http://pcsupport.about.com/od/windows-8/a/device-manager-windows-8.htm. Go to the Saitek Controller (probably located under the Human Interface Devices) and double-click to open. Select uninstall. Device drivers will be uninstalled. Here's a link to the Mad Catz knowledgebase for FSX and Saitek controllers.

 

http://support.madcatz.com/Knowledgebase/List/Index/52/fsx

 

Best regards,

jim

Jim,I tried your suggestion, and flew around for a while... So far, it seems to be working! But, it did look like I had already had the correct drivers installed. What I did in addition to your suggestion was remove all HID devices that were disabled in device manager. For those reading this, you should keep in mind that doing this could break other things, and you may need to reinstall devices that were not attached at the time of the deletion of all disabled devices. Regardless, it looks good from here. I will try it on the VATSIM network and report back!Best Regards,Brad

Have you unticked the power management options so that it doesn't send usb slot to sleep?

Glad my suggestion worked. If you remove a device through the device manager, don't worry as Windows will install it again if the hardware is found on your system. If you have any with question marks and unknown, those are the ones you need to find out what the hardware is that's not working.

 

Best regards,

Jim

Since this topic has pretty much run it's course here in the FSX forum, I'm moving it to the controller/joystick forum in the Hardware Section where I believe it belongs and can be useful to those who are interested in this type of hardware.

 

Best regards,

Jim

 

This is an automatic message.

 

This topic has been moved from "MS FSX Forum" to "Hardware Controllers & Drivers". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
  
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
  
• The images might not have been "illustrative" or "explanatory" in nature.
  
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.
  

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

Hey Jim, Well, I had the disconnect issue again, but, I believe I know why! I believe it is a conflict with SquawkBox! I "Flew" for hours this weekend, a plane flying a never ending flight plan, and it didn't disconnect... BUT, within a little bit of time of flying on the VATSIM network, the Saitek controllers disconnected. I'll try an alternate VATSIM client next, and report the results. I'd be curious if the others having this issue are also using an online flying client.

Well, I've run some more tests, and it looks like it is potentially a SquawkBox issue! The clue was the fact that many of us Win8 folks had started seeing a SB*.dll errors at FSX startup... Well, what ever was kicking that off, must have been further agrivated. I uninstalled SB, and switched to FSInn as my VATSIM client. I just flew from DLH to MSP and had 0 disconnect issues... there are other twichy things, but I only installed and did a basic configuration of FSInn... I'll report back after my next flight. Thanks again for all of your help!

I've been flying along without issues, but on a recent flight, it happened again.  Anyone else noticing this?  It seems to happen about halfway through an arrival.