Originally Posted by
Boosterdog
Once i ran the installed freePIE and ran the script manually, the 12qwas commands take effect as does the F1 but no Z key command. The instant ups and downs, lefts and rights assigned by the keys and hat dont really get on with me which is why i changed the transitions to back to the EDtracker inputs in the opentrack software (still keeping vjoy as the input device). For me, if the forward and upward movement of the camera could be assigned to a spare axis (twist stick or finger rocker on the throttle) that would be super but how and if that can be done i dont know. Im also not sure how changing the assignment of the OT axis then affects everything else.
The filtering to x,y,z axes that ClodPIE does is actually quite similar to what you can do in Opentrack natively, just by assigning (for example) yaw to the X axis & entering the appropriate map in Opentrack.
However, what you can do in FreePIE is quite a lot more sophisticated because you can tweak things programmatically. Biggest advantage is in looking back. With Opentrack you can set it to move left or right when you look back, helping see around the tail a bit. But ClodPIE looks left/right and additionally moves your head forward (which is impossible to do in Opentrack--you can do left/right OR forward/back but not both). Result is quite an improved view looking backwards.
If you don't like the keys, just edit to remove them. Like find these sections of ClodPIE11.py:
Code:
def ResetKey(): return keyboard.getKeyDown(Key.F1) #resets all modes (except ME109 mode); I set this to be the same as my Opentrack reset key
def LeantoKey(): return keyboard.getKeyDown(Key.A)
def PreventLeantoKey(): return keyboard.getKeyDown(Key.S)
def PreventLeantoToggleKey(): return keyboard.getPressed(Key.LeftShift)
def VibrateLeantoToggleKey(): return keyboard.getPressed(Key.Z)
def ME109ToggleKey(): return ( keyboard.getKeyDown(Key.LeftControl) and keyboard.getPressed(Key.D9)) #Ctrl-9 for 109 mode
...
def LeantoToggleKey(): return keyboard.getPressed(Key.CapsLock) or (joystickinput and joystickinput.getPressed(2))
def UpKey(): return keyboard.getKeyDown(Key.D1) or jipov >= 31500 or ( jipov <= 4500 and jipov >=0 )
def DownKey(): return keyboard.getKeyDown(Key.D2) or (jipov >= 13500 and jipov <= 22500)
def LeftKey(): return keyboard.getKeyDown(Key.Q) or (jipov >= 22500 and jipov <= 31500)
def RightKey(): return keyboard.getKeyDown(Key.W) or (jipov >= 4500 and jipov <= 13500)
Edit those two sections to look like this and save:
Code:
def ResetKey(): return keyboard.getKeyDown(Key.F1) #resets all modes (except ME109 mode); I set this to be the same as my Opentrack reset key
def LeantoKey(): return 0
def PreventLeantoKey(): return 0
def PreventLeantoToggleKey(): return 0
def VibrateLeantoToggleKey(): return 0
def ME109ToggleKey(): return ( keyboard.getKeyDown(Key.LeftControl) and keyboard.getPressed(Key.D9)) #Ctrl-9 for 109 mode
...
def LeantoToggleKey(): return (joystickinput and joystickinput.getPressed(2))
def UpKey(): return 0
def DownKey(): return 0
def LeftKey(): return 0
def RightKey(): return 0
That disables almost all of the keyboard shortcuts, leaving you with reset/re-center (F1), ctrl-9 to enter ME109 mode, and one joystick button to enter/exit lean-to-gunsight mode.
(You can change the number of the joystick button via joystickinput.getPressed(0), joystickinput.getPressed(1), or whatever you want. You could also change this to a keyboard key.)
I find the improved lean-to-gunsight, which you can enter & leave with the press of a button, the most helpful. I have used the "EDtracker lean-forward-to-gunsight" scheme for over a year now, but the button really does work better.
Bookmarks