Windows. MS messed with something in the enumartion process that has rendered target unreliable. Problems with axis and double button presses is most likely related to target not hiding the physical devices from the system.
You can check if this happening by running the script, then going to Windows start menu and running joy.cpl. If both the physical devices and the virtual device are there, then you’re going to have problems. The only reliable way I can run the script correctly is to restart windows then run the target script editor, hit compile and then it run. If I run any other program before I run target the script will often hang, but still run, though it won’t hide the devices. Which results in a faulty profile.
I wish I could provide a more reliable method for running the script but there is something going on with target, that needs to be fixed tby thrustmaster.
So… crazy late reply. Sorry. Thanks Gastone. That seems to be my issue. Sucks. I’m way to lazy to try to build a new key map My BMS days are over unless/until TM fixes Target.