AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() It really bugs me that I've had to deal with this Windows bug for over a year now. First off I tend to be a little OCD about this kind of stuff. Any suggestions or recommendations are most welcome. I have the latest chipset drivers installed for my motherboard. I've checked and installed the latest drivers for all devices. Thrustmaster HOTAS Warthog joystick and throttle Intel Core i7 4960X x79-Deluxe motherboard Here is a breakdown of my hardware configuration in case it helps: ect.)Īnyways I was just wondering if I'm the only guy experiencing this issue or if its more widespread. (I'm sure you all have read about the deleting of users documents, and the zip handling issues, and the Windows Media Player playback bar issue, and the Intel drivers issues ect. ![]() Especially with the train wreck that is the Windupdate. Windows 10 as a service has really worked well for Microsoft. However this is no good because Windows 10 is so aggressive about automatically updating itself to the latest version. ![]() Unplug all my devices after I'm done flying.Ģ. So far I have only found two solutions to this problem.ġ. If any one of these devices are plugged in no screensaver. I have a Thrustmaster HOTAS Warthog joystick and throttle, Saitek rudder pedals and I also occasionally use an Xbox 360 game pad for PC. I just never starts after the allotted time period. As soon as I plug them back in, no more screensaver. If I unplug my joystick, rudder pedals, and gamepad the screensaver starts no problem. However I still cannot get the screensaver to start. ![]() ![]() This last weekend I nuked my entire computer and upgraded to Windand installed Prepar3D v4.4 and all my addons. This issue first started with Windows 10 1803. I was wondering if anyone else out there has experienced an issue with Windor greater where if they have any type of joystick or game pad plugged into their computer the screensaver will not start. ![]()
0 Comments
Read More
Leave a Reply. |