bjohnsonmn

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

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.

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

I should post a W8 Tips sheet... It took a while, but FSX is working great on Windows 8, with all kinds of extras running... One key: DO NOT install in the default directory. I have a second, SSD drive that I have it running from, which solved many of the issues. A few keys: Before installing anything, make sure the *.exe is "Unlocked" and running win7 compat and as admin. DO the uiautomation.dll fix (in the FSX root directory), and disable UAC if you know you are not going to do something that puts your system at risk. Good Luck!