Auto Pilot
-
Shadow, may I ask what the purpose of doing everything in DX?
Means everything is in one place. You have just the one text file to alter joystick assignments, rather than hunting through several configuration files or GUIs.
It also means things are easier to set up, as Shad mentioned - you dont need to program your joystick software to interpret hold commands correctly - DX does that automatically.
-
I think I found what I needed in the Pitbuild.key
SimRightAPUp -1 0 0XFFFFFFFF 0 0 0 1 “MISC: PITCH Switch - ALT HOLD”
SimRightAPMid -1 0 0XFFFFFFFF 0 0 0 1 “MISC: PITCH Switch - A/P OFF”
SimRightAPDown -1 0 0XFFFFFFFF 0 0 0 1 “MISC: PITCH Switch - ATT HOLD”Is “Custom 3D Cockpit View” of any use today ??
OK all is right with the world, that was exactly what I needed to include in my key file.
Pity the Hog only has a push button for the left AP toggle but its workable.
-
Thanks guys,
Kinda makes sense. One question though:
when you say program in falcon, by that you mean in the controller setup window AND the keyfile? I am just trying to understand since I’m using Dunc_DX profile and a lot of the assignments are empty in the setup window. So I’m assuming he added those in the keyfile manually.Sorry if this off topic.
-
Thanks guys,
Kinda makes sense. One question though:
when you say program in falcon, by that you mean in the controller setup window AND the keyfile? I am just trying to understand since I’m using Dunc_DX profile and a lot of the assignments are empty in the setup window. So I’m assuming he added those in the keyfile manually.Sorry if this off topic.
Controller setup window IS the keyfile. If its not in the setup UI, its not in the keyfile.
-
Controller setup window IS the keyfile. If its not in the setup UI, its not in the keyfile.
In that case “not assigned” in the UI has to be manually edited in the keyfile?
-
Controller setup window IS the keyfile. If its not in the setup UI, its not in the keyfile.
Not true. There are 561 lines in my keyfile, but only 437 show in the “setup UI”
Here the -2 makes these invisible in the UI
OTWSetObjDetail -1 0 0X2 2 0X2D 2 -2 “Set Object Density”
OTWSetObjDetail -1 0 0X3 2 0X2D 2 -2 “Set Object Density”
OTWSetObjDetail -1 0 0X4 2 0X2D 2 -2 “Set Object Density”
OTWSetObjDetail -1 0 0X5 2 0X2D 2 -2 “Set Object Density”
OTWSetObjDetail -1 0 0X6 2 0X2D 2 -2 “Set Object Density” -
In that case “not assigned” in the UI has to be manually edited in the keyfile?
mouse click on “not assigned” it goes blue then pres a key. But are the already in use by DX?
I have callbacks directly assigned to the stick with out a keyboard input.
-
Thanks guys,
Kinda makes sense. One question though:
when you say program in falcon, by that you mean in the controller setup window AND the keyfile? I am just trying to understand since I’m using Dunc_DX profile and a lot of the assignments are empty in the setup window. So I’m assuming he added those in the keyfile manually.Sorry if this off topic.
Get Me This
If their DX directly to the stick they don’t need a keyboard assignment. “No Key Assigned”
-
Shadow thank you. I think I get it now.
Will go through the keyfile to see how these DX assignments are done. -
Get your self a copy of “Notepad ++” and use that to view your .key file.
Be carefull not change anything yet. NP++ has an Undo function but.
Cheers