Paddle switch
-
I’m using CH Fighterstick & Pro Throttle.
Whats the recommended “button” for the paddle switch since the Fighterstick doesn’t have it?Cheers!
-
Leave it, you don’t need it on your stick and throttle.
But if you insist, I would suggest to be on the coolie hat of the throttle. -
I put it on the pinky switch, so that a short press activates the zoom function (so the pinky switch function on the real stick), and a held press activates the paddle switch. After several attemps with other buttons, that’s the most comfortable setting I came up with.
However the paddle is more than mildly useful only if you often fly with the TFR on, in my experience. -
I put it on the pinky switch, so that a short press activates the zoom function (so the pinky switch function on the real stick), and a held press activates the paddle switch. After several attemps with other buttons, that’s the most comfortable setting I came up with.
However the paddle is more than mildly useful only if you often fly with the TFR on, in my experience.Great idea, because I believe from the manuals the real paddle switch is also located near the pinky.
Just one more question - How do you program the long and short presses?
Cheers!
-
Here’s what I wrote in the CMS file :
// bouton 4 du manche
// appui moins de 0,3 seconde : pinky switch
// maintien plus de 0,3 seconde : AP paddle
timer(period,D3,6)=JS1.B4;
sequence
wait(D3 and not JS1.B4);
CMS.B4=true;
delay(1);
CMS.B4=false;
endsequence
sequence
wait(not D3 and JS1.B4);
CMS.B1=true;
endsequence
sequence
wait(not JS1.B4);
CMS.B1=false;
endsequenceKnowing that, in my set up, CMS.B1 activates the virtual DX button for the paddle switch, and CMS.B4 activates the virtual DX button for the pinky switch (which purely acts as a pinky switch only, since I don’t use shift functions on my HOTAS).
-
Here’s what I wrote in the CMS file :
// bouton 4 du manche
// appui moins de 0,3 seconde : pinky switch
// maintien plus de 0,3 seconde : AP paddle
timer(period,D3,6)=JS1.B4;
sequence
wait(D3 and not JS1.B4);
CMS.B4=true;
delay(1);
CMS.B4=false;
endsequence
sequence
wait(not D3 and JS1.B4);
CMS.B1=true;
endsequence
sequence
wait(not JS1.B4);
CMS.B1=false;
endsequenceKnowing that, in my set up, CMS.B1 activates the virtual DX button for the paddle switch, and CMS.B4 activates the virtual DX button for the pinky switch (which purely acts as a pinky switch only, since I don’t use shift functions on my HOTAS).
Thanks, but I’m no expert in this CH programming thingy.
Which CMS file exactly do you edit, or is it possible to do it through the CH Manager & how?Cheers!
-
To make it short, there are 3 main ways to program a HOTAS button :
– In the CH Control Manager (CHCM), click on the button you want to program on the picture of the throttle or the stick, uncheck all boxes in the window on the right and then select which keybord keys you want the HOTAS button to activate. Fast and easy.
– The 2nd method is quite close : just check the “DX mode” box in the HOTAS button window, and then choose which DX button you want the HOTAS button to activate. A little less easy than the 1st method, because you have to know what’s written in the Falcon 4.0 .key file, but it’s better than the 1st as it allows simultaneous presses with no trouble.
– The 3d is to leave the HOTAS button window blank, and add the “CMS controls” in the list of devices in the CHCM. When it’s done, you get a new tab called “CMS Controls”. That virtual device and the CM Editor enable you to program complex actions instead of the simple “press and release” actions of the two more simple methods.
What you program in the CM Editor is saved in a .CMS file, in addition to the usual .MAP file. Notice that the .CMS file can be opened and modified with Notepad, but using the CM Editor in the CHCM is more convenient as it comes with an error-checking routine.
As far as I can tell, the CM Editor is easier to use than Thrusmaster’s Target. The language used is logical and consistent, but you don’t have to understand it all anwyay, no biggie. Once the basic logic behind the CMS controls tab and the CM Editor is understood, you can simply pick the sequences that fit what you want on CH forums, or here, just like the one I gave you in my previous post.The CHCM manual is comprehensive and not badly written. If you want to use complex functions, reading it will be very useful. Feel absolutely free to ask questions if you have any as you read it.
EDIT : The three methods can be used on different HOTAS buttons if you wish, depending on what you need.
-
Thanks for the info wildcat!
But I can’t seem to find a way to program the same button to do the long press short press function thingy.
I’m hoping to program the following on my Fighterstick:
Trigger (guns) - short press to shoot guns, long press to shoot laser (for LGB)
Pinky - short press as per normal, long press for paddleCheers!
-
I gave you what you have to use to get the short press/long press behaviour for the pinky switch here : https://www.benchmarksims.org/forum/showthread.php?33066-Paddle-switch&p=465125&viewfull=1#post465125
If you tell me why you couldn’t implement it, I might help you.As for the trigger, what you describe is possible, but it means you won’t be able to have the cannon fire for longer than the duration of the short press. Is that what you want to program ?
-
Here’s what I wrote in the CMS file :
// bouton 4 du manche
// appui moins de 0,3 seconde : pinky switch
// maintien plus de 0,3 seconde : AP paddle
timer(period,D3,6)=JS1.B4;
sequence
wait(D3 and not JS1.B4);
CMS.B4=true;
delay(1);
CMS.B4=false;
endsequence
sequence
wait(not D3 and JS1.B4);
CMS.B1=true;
endsequence
sequence
wait(not JS1.B4);
CMS.B1=false;
endsequenceI’m not sure which file I should edit to include the above.
I opened the .cms file which I use for BMS and it’s this:Is this the file I should edit, and if yes, do I delete all the existing text and paste yours?
Cheers!
-
It is a very late answer, apologies… :?
However, if it’s not too late :
All lines beginning with // are commentary. They don’t do anything. So you can write whatever you want after //.
All that you want to use must be written between “script” and “endscript”. So you merely have to copy the suggested text between “script” and “endscript”.
Then :- Make sure that the stick button number 4 has no assignation at all (the button 4 menu must be blank)
- Select the CMS Controls tab, assign whatever key or dx function activates the AP paddle to the B1 button, and assign whatever key or dx function activates the pinky switch to the B4 button
- Save what you did
- Don’t forget to use the “download” button to make the HOTAS use the new settings you’ve just modified.
And, above all : read the manual. It’s a good manual, and it’s a lot easier to understand that explanation if you have the basics already covered.
-
Sorry I had to revisit this thread (which was started by me)
I still can’t quite understand what ewildcat mentioned.
Is there a “for dummies” (like me) step by step hold my hand walk me through process someone can help pls.
First off I don’t even know which CMS file to amend…Basically I’d like to:
1. Program my pinky switch to work as normal pink switch function on press and release, but work as AP paddle when pinky switch is HELD.
2. Program my trigger to work as second detent when pressed and released, but work as first detent when trigger is HELD.Thank you in advance for your patience & help!
-
Sorry I had to revisit this thread (which was started by me)
I still can’t quite understand what ewildcat mentioned.
Is there a “for dummies” (like me) step by step hold my hand walk me through process someone can help pls.
First off I don’t even know which CMS file to amend…Basically I’d like to:
1. Program my pinky switch to work as normal pink switch function on press and release, but work as AP paddle when pinky switch is HELD.
2. Program my trigger to work as second detent when pressed and released, but work as first detent when trigger is HELD.Thank you in advance for your patience & help!
Do you want that on your stick or on your throttle? I’ll see if I can figure it out from ewildcat’s posts and if so post a video.
-
Do you want that on your stick or on your throttle? I’ll see if I can figure it out from ewildcat’s posts and if so post a video.
Definitely on the stick
1. Program my pinky switch to work as normal pink switch function on press and release, but work as AP paddle when pinky switch is HELD.
2. Program my trigger to work as second detent when pressed and released, but work as first detent when trigger is HELD.
-
The hard thing about dealing with the CH stick is that it has three internal mode settings ( for A/A, A/G, NAV "layers) and the red switch on the side toggles those modes - so ALL of your button assignment can change after you actuate it. Depending on what you want to do may effectively need to program the stick three times/ways - once for each mode/layer. This can make doing shift functions a real PITA. The “mode” you are in corresponds to each of the red/yellow/green LEDs on the stick base.
Dunno if you can control or override this with the CH Stick Manager software or not (I’ve never fooled with it), but you may want to investigate along those lines.
-
Kenguan: I got it to work. Rendering the video now. Should be about an hour for it to render and upload to my website. So check back soon.
Stevie: Well IIRC by default you don’t use the layers and you can just ignore that mode stuff and use what would be the missile step button in the F-16 for whatever you please? (I happen to use it for 1st Detent but it would make a great missile step button too lol). But what would be the advantage of having an a/a, a/g, nav layer go-round? For myself, I think I’d want to have TMS, DMS, CMS, Trim, Guns, and Pickle always available whatever mode/submode I am in.
For additional callbacks I have the pinky on the stick set to “shift” the functions (only while held). I have to have that positive engagement to be out of my standard F-16 configuration. That seems better to me to get more HOTAS callbacks out of CH than chasing that mode light around.
-
Kenguan:
You can watch the .mp4 screencapture on how to do it by clicking HERE.
-
-
Stevie: Well IIRC by default you don’t use the layers and you can just ignore that mode stuff and use what would be the missile step button in the F-16 for whatever you please? (I happen to use it for 1st Detent but it would make a great missile step button too lol). But what would be the advantage of having an a/a, a/g, nav layer go-round? For myself, I think I’d want to have TMS, DMS, CMS, Trim, Guns, and Pickle always available whatever mode/submode I am in.
For additional callbacks I have the pinky on the stick set to “shift” the functions (only while held). I have to have that positive engagement to be out of my standard F-16 configuration. That seems better to me to get more HOTAS callbacks out of CH than chasing that mode light around.
Yes…I’ve tried this and that’s how I found out about the effect - it’s not very well documented. From what I’ve observed if I do key assignments with the green LED lit and then press the step button and the yellow LED lights I am not likely to get my assigned function without also making the assignments with the yellow LED lit. What I was thinking was that maybe you could null this behavior with CH, but I don’t really know…never tried it.
I’ve solved the problem by buying a HOTAS Warthog…on the WH I use CMDS->dwn as my shift key, since it’s not used for anything in the F-16.
-
Kenguan:
You can watch the .mp4 screencapture on how to do it by clicking HERE.
Thank you thank you thank you!!!
A picture says a thousand words, but your video says a million!It worked like a charm!
ewildcat was right on the codes, but you were right on in describing where to put the codes in your video.From that I also managed to program my trigger to function as what I wanted:
- short press shoots the gun
- long press fires the laser from the TGP manually.
Only downside (which I can live with) is that in an air to air, to shoot my guns I can only use short press (short burst of the guns). If I hold the trigger long, nothing happens because then it is commanding a “laser firing”. But I can live with that - you are supposed to use short bursts of the gun anyway.
Thank you again ewildcat & -Vandal-