Search the Community
Showing results for tags 'windows 8'.
Found 3 results
If you've been tearing your hair out over Win 8.1 or 10 joystick and throttle disconnects in P3D, especially with Saitek products, this could be for you. I stumbled across a cure that, so far, has been absolutely, 100-percent effective. This works when disabling selective suspend in device manager does not. It works when changing power settings in Control Panel does not. It works when the problem presents itself in Windows 8.1 OR 10. Here goes. Search the registry for this string, EnhancedPowerManagementEnabled=1, where the device it refers to corresponds to a joystick, pedals, throttle quadrant and so on. Change it to read EnhancedPowerManagementEnabled=0 Reboot. Smile. Bear in mind, though, this needs to be redone every single frickin' time you upgrade Windows, as the Windows install stomps on those Registry keys. Sorry "resets them to the 'proper' values." Hope this settles it once and for all
Hey everyone, I believe I have solved the joystick woes with Windows 8 and Windows 8.1. I have done 2 days of stress testing FSX and P3D with multiple installs of the program and OS, and I haven't had a disconnect yet. Before I go further - I want to give my thanks to certain individuals who have helped me and inspired me to solve this joystick annoyance. 1) Word Not Allowed for having his awesome guides 2) AVSIM's staff/team for creating the amazing Hardware/Software Guide to FSX/P3D 3) Peter Dowson's FSUIPC utility (it got me through the periods when no joystick fix was avialable) 4) Orbx Team - Thank you Global and your Tips and Tricks Forum section 5) NickN's - FSX Computer System Guide 6) Ranak Jones of "Rogue's Guide to Acquisition: Principles of Final Frontier" for sending me a spare XFX 6970 for my system and pointing me to Windows 8 Registry to search for USB Device GUIDs potential errors 7) Microsoft MSDN for having Windows 8.1 Pro for testing/evaluation purposes only. 8) LM Prepar3d Developer Network Testing: 1) FullScreen FSX in Eyefinity Mode (5760x1200) for 3 hours+ 2) Windowed FSX in triple screen mode and 1920x1200 for 4 hours+ 3) Multiple active windows on top of FSX Windowed in background for 4 hours+ 4) Testing was done with USB 3.0 and USB 2.0 ports FSX testing was in Win 8.1 and 8, and P3D 1.4 was in Win 8. My System Cpu: i5-750 (intel 1156 cpu) overclocked to 4.1Ghz Memory: 8GB DDR3 Storage: 1xSamsung 830 SSD at Sata III (Main drive), Intel 80GB SSD at Sata II speeds, 1 TB hitachi mechanical HDD at sata II <- all connected to PCIEx4 Sata III controller) Motherboard: MSI Fuzion p55A - has native usb 2.0 and Renesas USB 3.0 controller Video: New XFX 6970 2GB with latest ATI drivers OS - Windows 8 Pro Clean install / Windows 8.1 Clean Install Joystick: Thurstmaster Hotas X Windows 8 Solution - (FSX / Prepar3d 1.4) 1) Make sure power management features are off or set to high 2) Most important setting is USB Selective Suspend Setting is Disabled (we all knew this) Honestly, that setting does not disable USB selective suspend in Windows 8 (this is for Windows 8 only), like it promises. The power management on USB devices is set to Selective Suspend Please see your HID Devices, USB Input Device and USB Root Hub Devices - They are STILL set to Suspend. You have to turn OFF the manual power savings one by one to all USB Devices/Compositive Devices and the all the USB Root Hubs (this is v.important). If it says "Allow the computer to turn off this device to save power" and is checked then please UNCHECK it For example like this This was discovered when I was searching for Joystick UID's in Windows 8 based on Ranak's suggestion. This is where stuff gets weird for both Windows 8 and Windows 8.1. I am no registry expert, but GUID's for my joystick is half correct and half backwards as compared to one listed in FSUIPC's ini file See Pic - Windows Registry And my Joystick GUID in FSUIPC So for some reason half of the GUID is backwards in Registry - I do not know if that is normal or not but that led me to search all the usb devices/ports in Device Manager. Here I found all the power saving features were somehow enabled when Windows Power Management is explicitly set to disable. Recap So for Windows 8 Pro ONLY - Uncheck Allow the computer to turn off this device to save power and make sure Windows Power management also has Selective Suspend set to Disabled. Prepar3d 1.4 - Please have JOYSTICKS=1 in [CONTROLS] in P3D.cfg (more on this later) Windows 8.1 Pro (RTM Version) - FSX TEST No joystick disconnects with 1 Setting change Only - Joystick works in Windows 8.1 Pro I am seeing that all devices still have the USB Power Management check in windows 8.1 but in FSX with PNW, and Bowerman addon, Carenado B200 - Joystick did not disconnect. The only crash I got was from latest FSUIPC 4.92. If in Windows 8.1 you have joystick disconnects, then just turn off all those power management features as listed in for Windows 8. Miscellaneous Info FSUIPC I have it installed but it Zero Joystick Configuration in all tests. I hope this helps everyone - as Windows 8.1 Pro definitely works fantastic with no joysticks issues so far. And Windows 8 works with all power management features individually turned off in all those sections listed. Have a great day, Skywolf
This problem has really been bothering me for a long time. I have tried basically everything in the book to solve it. When I switch tasks in flight, say to check vpilot or go to chrome, my controller resets and causes fsx not to read it anymore. I tried porting it through FSUIPC and the same problem occured. I've gone through device manager(making sure it doesn't cut off for power saving), and did the same thing in control panel. I have run fsx in compatability mode, still no luck. When I check fsuipc anything to do with the yoke disappears. I've updated the drivers on saitek, and the problem is still there. I'm pretty sure it has something to do with vas because whenever I go into a high end scenery area or I use a heavy payware aircraft it tends to happen more often. It's literally making it impossible to fly because I can't seem to go through a flight without this problem occuring. Sometimes I don't even need to do a task switch to get this to trigger, the yoke itself will just blip on and off and fsx will stop reading the yoke. This also happens with almost all my other joysticks as well. The only way I know about fixing it is by switching between fullscreen and windowed mode a ton of times, but that only works to a point. I am completely at a loss of what to do next. I've heard its a common problem with windows 8, but I still have no idea how to solve it.