Pinky switch and Paddle switch programing suggestions
-
I use the Warthog’s CMS->dwn position as a shift key - that way the paddles stays in use to cancel Autopilot…and the pinky for…whatever it does. I’m mixing Hornets and Vipers just now…
-
I use the Warthog’s CMS->dwn position as a shift key - that way the paddles stays in use to cancel Autopilot…and the pinky for…whatever it does. I’m mixing Hornets and Vipers just now…
Yes, I am planning to do the same. Why didn’t use the CMS push down as a shift key?
-
One last question this is a rookie question. How do you create \ DX switch using Target? For example if I want to use the paddle as the DX shift (Short press FOV/long press DX Shift), or if I want to use the Pinky switch instead how would I do it? I was reading the Target manual about put two command for the same button.
Also is anyone use the CMS push down future? -
SetShiftButton(&Joystick, S4);
MapKeyIO(&Joystick, TG1, DX1, DX2); -
Yes, I am planning to do the same. Why didn’t use the CMS push down as a shift key?
If you have shift functions on your TMS/DMS/PICKLE or Trim it’s going the be hard to hold CMS (presumably with a thumb) AND engage those keys/hats with another finger.
-
I use CMS->dwn for a couple of reasons. First, it’s not a key that has a specific function in the F-16 so it’s out of the way of normal HOTAS functions. I want to keep my HOTAS assignments as close to reality as I can.
Second, you need to do some thinking in regard to the below in your setup - i.e.; assign functions in such a way that you can get/hold what you want. Some of my shift actions don’t require holding the shit key - some of them are double-clicks, like CMS->dwn swapping my Trim hat between POV and Trim function, or double-tapping the NWS/WPN switch to center my Trim.
I also programed some delay into my CMS switch because yes - it’s easy to hit it and waste Chaff and Flares. The the delay (just a few ms) makes for having to do a positive actuation of the switch.
-
…. I want to keep my HOTAS assignments as close to reality as I can. …
I agree. In which case the paddle would be the paddle and the pinky would be the pinky. In BMS the DX function for the pinky does what the pinky is supposed to do PLUS acts as a shift key. IOW, there is not necessarily a reason to assign any DX callback to the ‘extra’ key on the Warthog (CMS press) and still maintain full fidelity of the RL stick.
…. Some of my shift actions don’t require holding the shift key - some of them are double-clicks …
I think we’re talking about two different things. I’m referring to DX Shift functionality built into BMS, not using a program such as TARGET (or similar). In which case (the native BMS case), you do need to hold the shift key and you don’t have double-clicks for the functions you describe. That is, I had not considered what you’re describing as ‘shift’ functionality.
-
I think you’re right about that, to a point - in the generic sense we’re talking about “alternate actions” on/from a keyboard since all of the commands are sent as key assignments. My approach amounts to also selecting “caps lock” on the “shift” in how/which functions I’m selecting - I try to avoid using momentary invoked actions via a shift layer, but that’s just my own approach to HOTAS - like with my toggle from Trim to POV, positive arm, positive cancel.
So…I’m not too familiar with Foxy, but one could also do a lot of the things I’m doing using Foxy instead of TARGET if you’re using an intact Cougar unit. Or you can re-map/reassign keys by editing a keyfile. You can always use DX assignments for an un-shifted function and assign macros, shifts, etc. via keyfile and/or third party, or require a combination (paddle+pinky, forex) to command an alternate action, which again, is pretty much what I’ve done. In my setup paddle+pinky commands Eject; paddle = paddle, and pinky = pinky.
Once I have my cockpit built I’ll have an Eject handle, so I’ll stop using paddle+pinky to Eject…or maybe use it for something else. Once I have an OTW projection screen built I’ll also eliminate POV control from my hat and use it for Trim only.
-
I use the paddle as the DX shift (Short press FOV/long press DX Shift), and the pinky as the Paddle (AP Override/Trim reset in shift layer).
The best thing to do with the Warthog stick is set the unshifted DX layer as it is laid out for the actual F-16 (the pinky/paddle swap above as the exception).
It’s an exception (for me) because it’s easier to hold the paddle when using the shift function and holding the pinky/paddle at the same time is difficult. The other exception is the press down on the CMS switch, which I used for the screenshot button.
How do you program that function?
-
<snip>Once I have my cockpit built I’ll have an Eject handle, so I’ll stop using paddle+pinky to Eject…or maybe use it for something else.</snip>
I programed VoiceAttack to Eject on the Verbal Command eject eject LOL…. Had so much fun testing it a half dozen times in Instant Action over the mountains of N. Korea with the dingy attached.
-
How do you program that function?
The ‘Pinky HOTAS’ command is: SimHotasPinkyShift … that does the short press/long press functionality.
The paddle switch command is: SimAPOverride
Like any callback command, you can assign those to any DX button or switch. The basic command can be assigned in the Setup UI, but shift functions have to be done in the keyfile or in some other off-line tool.
-
I programed VoiceAttack to Eject on the Verbal Command eject eject LOL…. Had so much fun testing it a half dozen times in Instant Action over the mountains of N. Korea with the dingy attached.
Nice. Once I get there I intend to program all Wingman, ATC, etc. commands for voice action.
-
Nice. Once I get there I intend to program all Wingman, ATC, etc. commands for voice action.
Have a look Ito the Voice control sub forum. There are already some very good Voice Attack profiles around. Programming /setup one from scratch might take way more time than setting up a HOTAS
-
Have a look Ito the Voice control sub forum. There are already some very good Voice Attack profiles around. Programming /setup one from scratch might take way more time than setting up a HOTAS
Copy. Just looking over the dialog menus I can already tell that’s a LOT of script to read through!