Elite Dangerous and Windows 10 Discussion thread.

Fingers crossed things go smoothly when I upgrade (got a reservation yesterday... wonder how long I'll have to wait)

I am concerned about my head tracking (FaceTrackNoIR using PS3 Eye camera and IR rig) working afterwards. Anyone else using that setup with Win10?
 
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.

This is the same problem I have and I posted it a few pages earlier. I also found no solution. The weird things is that I used the Insider Program and the X52 worked just fine, the problems only started with the final W10 10240 release version. :(
 
Last edited:
I am concerned about my head tracking (FaceTrackNoIR using PS3 Eye camera and IR rig) working afterwards. Anyone else using that setup with Win10?

The Code Laboratories website makes no mention of Windows 10 for the CL Eye driver. Given that this is a paid-for driver it's a poor show.

EDIT: I use a Track Hat and I've just read this on their FB page:
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!
 
Last edited:
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.

Ya actually I n9tcied a reboot didn't fix it but unplugging and reconnecting did; However, and I doubt this will get fixed but it's not a huge deal, every time I boot up and go to play I now have to unplug and reconnect for it to show up in Opentrack lol.
 
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.

I honestly don't think it will be like that. Retail keys are supposed to have limited uses but they don't. I have used my keys though multiple components (motherboard and cpu) and your license from 7 is used to activate 10. I see no reason why you won't be able to do clean install on a new motherboard in the future. I guess we shall see but Microsoft are very...forgiving when it comes to keys on new machines. Correction : the 4th time I installed on a new motherboard it said the key could not be used again. I called them told them I was reinstalling and they fixer it...from a legal stand point maybe that was wrong but either way you probably don't have to worry much about it.
 
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 think Win7 Ultimate will become Win10 Pro?
 
Last edited:
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?

Now have final Windows 10.

after installing elite you must install directx 10 as 9 does not work.
 
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?

This is what I was trying to say but you did it in a much more concise way lol +rep
 
... the free upgrade applies only for the lifetime of the machine running the OS to be upgraded, NOT in perpetuity.
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.
 
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! :(

Also upgraded to Win10 today, and noticing the same issues, if not more; every now and then when (trying to) play ED, the lighting on my X52 will flicker off then back on , like it's just been unplugged/replugged. Not such an issue, until you realise it's now centred at whatever position you were holding it at when the lights went off. So when you _do_ centre it, it's now rolling/pitching in that direction. Of course, then unplugging it manually causes the whole thing to mess up, complete with the laggy mouse, can't click on anything, makes beeping noises, etc. Even the 'restart' option seems to cause a system hang - I can only restart with the reset button on the chassis...
 
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.

I had a client with an old copy of office 2003, they had used the key far too many times, called MS, they issued a new key, that was about a year and a half ago lol.
 
Firstly, agreed that Microsoft have in the past been much more accomodating regarding license transfers than their terms might suggest.

However, Windows 10's whole raison d'etre is to 'unify' everyone on the same version. MS' business model now centres around this idea.
Because of this, I'm dubious about how agreeable they will be about re-activating versions of Windows they'd rather didn't exist any more.

There's a whole massive debate around this issue, but this is not really the place for it.
 
Oh, for those looking to roll back from Win10 to their previous Windows, you can, provided: 1) you did an upgrade to win10, rather than a clean install, and 2) you do it within 30 days of the initial upgrade.
Click the Start button > Update & Security > Recovery > Go back to Windows <insert previous version>
 
Upgraded today (fresh install) and all software and drivers running fine so far.

Spec FYI: Asus P8P67 Deluxe, i7-2600k, Gigabyte 760 GTX, CH Throttle & Fighterstick, Saitek Rudders, G13.

So far I'm impressed. Elite even seems to be running more smoothly for me. I used to get slow down occasionally while skimming planets coming in to dock but so far it's been fine.
 
Back
Top Bottom