I've been plagued by BINDS files destroying themselves for quite a few iterations of ED now. Yes, Frontier could make the system a bit more robust but its NOT always down to them. Since my upgrade to Windows 10 Pro, and especially the Creators UPDATE 10.0.16299 I've noticed - and repeated the following behavior.
I'm currently using a reasonably powerful bespoke gaming PC. i7 chip; ROG Board; 32GbRAM; Solid State Hard Drive etc. etc.
My HOTAS of choice is CH Products Fighter Stick/Throttle/Pedals
I utilise CH Manager Software
About the time the main upgrade invaded my machine I noticed that "some" of the USB Drivers hadn't migrated properly - usual cop-out from MS of "ambiguous properties detected" with absolutely no solution offered/. ( I really don't want to rebuild my operating system at this time) What this translated to was that Windows rescanned the USB devices attached and did not always detect them in the same order - or so it seems.
The following is from two BINDS files and both reference the Pedals. The first one properly parsing the name and inserting it, the second "losing the plot" and inserting the HEX code - which incidentally is still ok if it always detects the attached devices at boot up or activation. This schizophrenia confuses the hell out of ED which since the windows driver layer is reporting that
a)it cannot find the named device in the BINDS file,
or
b)its now renamed or even missing, it happily trashes all of your control file.
<YawAxisRaw>
<Binding Device="CHProPedals" Key="Joy_ZAxis" />
<Inverted Value="1" />
<Deadzone Value="0.00000000" />
</YawAxisRaw>
<YawAxisRaw>
<Binding Device="068EC010" Key="Joy_RZAxis" />
<Inverted Value="1" />
<Deadzone Value="0.00000000" />
</YawAxisRaw>
For the clever clogs amongst you, who drop in their backup BINDS file, it will happily trash that also.
I find that I have to manually ensure that the 3 devices are connected and recognised by Windows BEFORE I fire up ED. In doing that I don't have a trashed BINDS file and can happily fly away.
A complete pain in the ar$e I know, but at least a work around for now until I come up with a better solution when I get more time.
I'm currently using a reasonably powerful bespoke gaming PC. i7 chip; ROG Board; 32GbRAM; Solid State Hard Drive etc. etc.
My HOTAS of choice is CH Products Fighter Stick/Throttle/Pedals
I utilise CH Manager Software
About the time the main upgrade invaded my machine I noticed that "some" of the USB Drivers hadn't migrated properly - usual cop-out from MS of "ambiguous properties detected" with absolutely no solution offered/. ( I really don't want to rebuild my operating system at this time) What this translated to was that Windows rescanned the USB devices attached and did not always detect them in the same order - or so it seems.
The following is from two BINDS files and both reference the Pedals. The first one properly parsing the name and inserting it, the second "losing the plot" and inserting the HEX code - which incidentally is still ok if it always detects the attached devices at boot up or activation. This schizophrenia confuses the hell out of ED which since the windows driver layer is reporting that
a)it cannot find the named device in the BINDS file,
or
b)its now renamed or even missing, it happily trashes all of your control file.
<YawAxisRaw>
<Binding Device="CHProPedals" Key="Joy_ZAxis" />
<Inverted Value="1" />
<Deadzone Value="0.00000000" />
</YawAxisRaw>
<YawAxisRaw>
<Binding Device="068EC010" Key="Joy_RZAxis" />
<Inverted Value="1" />
<Deadzone Value="0.00000000" />
</YawAxisRaw>
For the clever clogs amongst you, who drop in their backup BINDS file, it will happily trash that also.
I find that I have to manually ensure that the 3 devices are connected and recognised by Windows BEFORE I fire up ED. In doing that I don't have a trashed BINDS file and can happily fly away.
A complete pain in the ar$e I know, but at least a work around for now until I come up with a better solution when I get more time.
