I have the exact same issue. It occurred with my X-52 and my X-55. I have tried using a powered USB hub both 2.0 and 3.0, disabling USB 3.0 in bios, clean install of OS and Saitek Drivers etc.. No matter what, when I unplug my HOTAS windows beeps constantly, mouse becomes laggy and unresponsive. It is only fixed by a restart. Now, I either leave the HOTAS plugged in always, or shut down to unplug it.
I've done a lot of research and this issue is fairly common when googling terms like "windows beeping mouse lag." As it turns out, I have yet to see a fix for it. The Saitek configuration program also crashes in Win10 for me and is not reliable at all.
Ultimately, I have yet to find anyone using a Saitek HOTAS with Win10 that does not experience this issue.
I am concerned about my head tracking (FaceTrackNoIR using PS3 Eye camera and IR rig) working afterwards. Anyone else using that setup with Win10?
Evening Trackhatters! I've been testing the PS3 eye camera drivers and opentrack with Windows 10 today, and I'm pleased to report everything works great!
Ok, if you, as me has upgraded to Win X and have an edTracker... chances are that it's working fine (as mine now) or not (as mine 1 hour ago).
If you log into ED and see your control scheme is not working, test this:
- Exit Elite Dangerous
- Unplug your EdTracker device (if you have EdTracker GUI It will crash now...)
- Plug your EdTracker device
- Relaunch Elite Dangerous
This happens because when ED starts it parses all bindings files, and those without a valid controller are not shown at Controls selection dropdown nor active.
On updating to Windows 10, EdTracker is recognized first as a COM device (not joystick), which is OK since it's arduino based and the EdTracker GUI connects through COM to it, but it's also a HID (Human Interface Device aka control device). However, somewhere in the update process it's not recognized as HID and only as COM. Plug/unPlug resets it's state (a reboot while plugged doesn't trigger the driver recognition)
If you happen to copy your custom.binds to your very own file and it's not shown on the controls list, this is likely the cause.
There's something about this free upgrade to Windows 10 that's bothering me, & it's this:
From what I can discover, the free upgrade applies only for the lifetime of the machine running the OS to be upgraded, NOT in perpetuity. This is fine if you bought a machine with a previous version of Windows pre-installed or are using an OEM version, but what if you have installed a retail version ?
Using myself as an example, I am currently running the retail version of Windows 7 Ultimate, which represents a not insignificant amount of money. My machine is 4 years old so it's fair to assume that at some not too distant point it will need to be replaced, or in a best case scenario, I will have to replace the mainboard & processor, making it a different machine so far as Microsoft are concerned.
I will not be able to install (or re-install. Whichever) free Windows 10 on the new machine, but I also assume (given Microsoft's Modus Operandi) that my license for Windows 7 Ultimate will have either been rescinded or transferred to the original free Win 10 upgrade, which also means I will not be able to legally install my copy of Win 7 Ult. In effect, MS will have turned my retail Win 7 Ult into an OEM Win 10 & there will be no way of going back.
I would urge anyone running a retail version of Windows to think very carefully about the implications before accepting the free upgrade.
There's something about this free upgrade to Windows 10 that's bothering me, & it's this:
From what I can discover, the free upgrade applies only for the lifetime of the machine running the OS to be upgraded, NOT in perpetuity. This is fine if you bought a machine with a previous version of Windows pre-installed or are using an OEM version, but what if you have installed a retail version ?
Using myself as an example, I am currently running the retail version of Windows 7 Ultimate, which represents a not insignificant amount of money. My machine is 4 years old so it's fair to assume that at some not too distant point it will need to be replaced, or in a best case scenario, I will have to replace the mainboard & processor, making it a different machine so far as Microsoft are concerned.
I will not be able to install (or re-install. Whichever) free Windows 10 on the new machine, but I also assume (given Microsoft's Modus Operandi) that my license for Windows 7 Ultimate will have either been rescinded or transferred to the original free Win 10 upgrade, which also means I will not be able to legally install my copy of Win 7 Ult. In effect, MS will have turned my retail Win 7 Ult into an OEM Win 10 & there will be no way of going back.
I would urge anyone running a retail version of Windows to think very carefully about the implications before accepting the free upgrade.
If you have a proper Win10 key, you can do a fresh clean installation, also on a new/different machine. They key can only be used on one machine at the time. If you are talking about an OEM key from your laptop, those are hardware bound. Those keys won't work on a different machine. Anything else is fine.
Even if you upgrade you will be able for a certain amount of time to downgrade again. How it works, no clue but this option does exist. Yes, I thing Win7 Ultimate will become Win10 Pro?
If you have a proper Win10 key, you can do a fresh clean installation, also on a new/different machine. They key can only be used on one machine at the time. If you are talking about an OEM key from your laptop, those are hardware bound. Those keys won't work on a different machine. Anything else is fine.
Even if you upgrade you will be able for a certain amount of time to downgrade again. How it works, no clue but this option does exist. Yes, I thing Win7 Ultimate will become Win10 Pro?
It works on Windows 10?
Yeah, I've read that too - seems pretty plain. However, I run an OEM Win7 Pro, so I'm aware that I may encounter problems if I have to rebuild. The last time I had to switch the OS to a rebuilt machine, I had to contact MS for new OEM product key - no problem then, but these days I wonder if MS will be so accommodating.... the free upgrade applies only for the lifetime of the machine running the OS to be upgraded, NOT in perpetuity.
I done a fresh Win10 pro install today and have the exact same problem, all is fine until the X52pro is removed. Noticed that the Saitek drivers are still unsigned which also caused a few issues, tried disabling driver signing and I'm still having the problem. There have always been issues with driver signing with Saitek and they still haven't fixed it after all this time. IIRC they say it's due to drivers in the package that they didn't write, therefore they do not take responsibility for them.
I tried the usual fixes but no joy, looks like we will have to wait for an updated driver from Saitek. I dread to think how long that will take!![]()
Yeah, I've read that too - seems pretty plain. However, I run an OEM Win7 Pro, so I'm aware that I may encounter problems if I have to rebuild. The last time I had to switch the OS to a rebuilt machine, I had to contact MS for new OEM product key - no problem then, but these days I wonder if MS will be so accommodating.
Overall, I think I'll wait and see - but I am inclined to stick with Win7 for the foreseeable future.
Overall, I think I'll wait and see - but I am inclined to stick with Win7 for the foreseeable future.
This is what I was trying to say but you did it in a much more concise way lol +rep