So it's not in alphabetical order, Sidewinder starts with an S, Logitech with an L. I connected my old sidewinder as well, which ended up on top in joy.cpl, and which is now the device used in Secret Ops.
When i copy the Control.exe from system32 (where it *is* located on my PC) it works, but i still end up in the joy.cpl window, selecting the virtual stick, chosing it as the default device for older games, and being frustrated because Secret Ops still only recognizes the joystick.ĮDIT: Ok, now i have an interesting situation. Which is understandable, since i don't have a Control.exe in C:\Windows. The Secret Ops Launcher is no help either, when i try to select the stick there it always gives me a "(Misc (2)) Cannot execute file: C:\Windows\Control.exe, 2" - error. In fact, i assigned every single axis of the virtual stick to my throttle to be sure too, it still recognizes only joystick movement.
Sorry, should have been clearer about that. That's what i meant when i said i set the Virtual Joystick as default controller. That is, "Logitech G940 Joystick" is higher in the joy.cpl list than "PPJoy Virtual Joystick 1" because of the alphabet. The only other explanations i'd have is that either the virtual stick doesn't "look" enough like a joystick for Standoff so it choses the next best thing, or it always uses the device higher on the list no matter its set priority. But i set the Virtual stick as default, so that's not it. Normally every game, even the older ones, would use the "default" controller. Now that's something i find really odd, there already were multiple game controllers back when Prophecy came out, so there has to be a way of telling the game which one to use. I tried switching controller IDs around with "JoyIDs", but Standoff still doesn't seem impressed. However, Standoff still acts as if only the stick is connected, apparently only using "Logitech G940 Joystick" instead of "PPJoy Virtual Joystick 1", even though i made it the default game controller. So in Freespace/Saga i can use all functions of my Hotas now, so for that alone: Thank you.
I was going to blame Windows Security Updates for disallowing PPJoy's intrusive method, but in your link i saw posts newer than a month that say it works, so i have no idea.ĮDIT: OK don't know what did it, but all the axes and buttons work now. I am in Testmode right now, have manually signed the drivers, Hotas is plugged in, PPJoy is running, but when i scan for axes or buttons, it doesn't recognize any.
Yes, had to do that in order to install PPJoy in the first place.