Waiting patiently for a driver update I guess. You can make a temporary controls profile in your games and attempt to work around the fact you do not have multiple profiles and macros and such so you can at least use the damn thing. For example, trigger is button 1 in control panel, so games will now detect this as "button 1". I've found a temporary solution though! If you play your games while you have the control panel open, your games will detect the presses as their number. MFD text also seems to flicker? Very strange behaviour all around. The display of which button I'm pressing on the MFD is also buggy, sometimes it shows trigger all the time and only some buttons show and only sometimes. Unplugging it causes the mouse to be unresponsive and you get that stupid "boop boop" each time you click. Profile settings will not work, such as key bindings. Thx for your helpĮxact same issues here, running Win 10 pro. Please give me the exact saitek driver version SST software version that is working with you. Because i tried to disable integrity check using shift + restart button using power menu then selecting troubleshot and restart with integrity check disabled. So, they've updated their drivers only for us to use the one back from 2013!!!Ĭan you give us steps to disable integrity check and steps to install drivers. So I choose the other one which had a version/date: v7.0.27.13. The one not working had a version/date: v7.0.39.0. In there I show too possible drivers found by the OS to be for this hardware. After installing the latest drivers and software, which they where not working, I tried to manualy choose what driver windows should use for "Programmable Root Enumerator". That is the one responsible for translating button presses to keyboard entries. In the Device Manager under "Programming Support" there is an entry called "Programmable Root Enumerator". Don't they do quality checks before releasing their software? I cannot imaging that they tested the new drivers and didn't noticed that the OS was rejecting the new version. It seems that there might be something wrong with the drivers digital signature. From a reddit tread someone managed to get the new drivers installed by disabling windows integrity check. The last two driver versions Saitek/Mad Catz really messed things up. I know that the title of the thread is about windows 10, but the problem exists even on windows 8.1.
0 kommentar(er)
