Pedals/Brakes help

[scout]

Can someone help me assign toe brakes to both my pedals in CM? I've looked at the available downloadable profiles but I guess I'm too thick.

My pedals are on device number 3.

If someone really wanted to be a pal, I could send you the profile I'm currently using and you could add the assignment for me :)

scout@army.com

[Spidey]

Depends on what game you are talking about...

IF you are talking about FS2002 / 2004, its very easy. Just leave them as Uaxis and Vaxis. Configure them inside the game for LEft Brake Axis and Right Brake Axis.

If you are talking about IL2, a little tricky here since IL2 only supports one Brake Axis whereas you have 2. So the easiest thing to do it is to use CMS to make your two brake axes into one axis.

IF ([JS3.A1 > JS3.A2]) then // LEFT OR RIGHT TOE BRAKES
CMS.A1 = JS3.A1;
ELSE
CMS.A1 = JS3.A2;
ENDIF

That assigns CMS Axis 1 to be whichever is greater of your two brakes. You can also average them together if you want.

CMS.A1 = (JS3.A1 + JS3.A2);

Then you assign JS3.A1 and JS3.A2 to NONE. CMS.A1 to either Uaxis or Vaxis. Then assign the brake axis in the game just like with FS2004.

Finally, you have games like Falcon4 where you need to hold down the k key

CMS.B1 = ([JS3.A1 > 128] or [JS3.A2 >128]); // WHEEL BRAKES

This activates CMS B1 button when either left brake or right brake is depressed more than 50% (128 value).

You assign JS3.A1 and JS3.A2 to NONE. Then CMS.B1 becomes "HOLD k" for holding down k key.

[scout]

Its finally working. Thank you.

[Richard]

Is there a chance of assigning brakes to the toe pedals without cms scripting.

[MichaelCHProd]

Absolutely but it depends on what the game itself supports. Which game are you looking at?

[Richard]

Right now I am just using the '3 mode' system for my game and not using CMS scripting for my setup. Could someone please tell me how to apply wheel brakes to my brake pedals for the game LOMAC.

It would be greatly appreciated.

[MichaelCHProd]

Ok, LOMAC does not have support for analog toe brakes, nor does it even support differential brakes. It only supports "wheel brakes" with the default key stroke of "w". Now if there has beeen some UBER patch released since last Monday this may be different but I don't think so.

As such you are going to need to program the "brakes" in the Control Manager. Scripting is the best way to accomplish this in my opinion. Are you sure you don't want to script this?

More pointedly are you sure you don't just want to copy a working script and use it to get your brakes?

[Dracon]

Just so's ya know......I have never done a thing with cms scripting. Nada! Spidey, I followed your instructions to the letter and it WORKS!!!

In hopes of making things even clearer. After you paste the above script in the Forgotten Battles cms. You MUST then set your Device # 3, Toe Brake axis to NONE for both left and right toe brakes.

Add the cms to you Forgotten Battles CM program if it's not there. Select cms axis #1 top left axis. Uncheck Center and set the cms #1 axis to CM Device 3 in the pull down menu next to DirectX Device. Then under Direct X Axis set it to U axis.

Now go into Hotas Control in-game under HOTAS and select brake. Step on Left toe brake. Apply and You Be Done!

Hope I didn't muck Spideys explanation up!

Dracon

Man this CH stuff is cool! A bit to learn but cool!

A special Thankyou to Spidey <Salute Sir>

[scout]

Yep, worked like a charm... again :P

[MichaelCHProd]

Outstanding B)

[Flak_Rambler]

Just bought IL-2 AEP and CH pro pedals USB and don&#39;t know how to make them work (rudder and brakes), I read all these instructions given, but quite honest, don&#39;t understand anything. I&#39;m not a tech person so I would like to be lead step by step.

[MichaelCHProd]

For the rudder it is pretty simple. I would suggest having a look at the CH Slide Show for it... http://www.chproducts.com/retail/setups.htm

The brakes are a different manner; depending on how much realism you want :)

IL-2 does not have "left" and "right brakes" just "brakes". Since your pedals are setup for "left" and "right" you have a couple of options....

1. You can choose one pedal to act as the brakes and pretend when you push both when you are really only getting analog braking from the one you assigned in IL-2.

2. You can assign a keystroke to either of the pedals (b is the default "brakes command) but then you only get brake activation from one pedal just like above but now it is not analog so the game either sees full brakes or no brakes.

3. You can get into scripting and get both pedals to input to one axis in the game so that either pedal will send "brake" to the game and the signal will be analog.


Which one would you like :)

[Flak_Rambler]

OK, went into the Control Mgr, assigned rudder and left and right break to the pedals (didn&#39;t know only one works), went to HOTAS and got the pedals working.

Now, you gave 3 options, and I choose #3, however, let me see if I undestood you: because IL-2 limitations, both pedals will "break" but won&#39;t get a left or right brake, and this can be done with the keyboard either.

Well, by doing # 3 will learn more about it, so let&#39;s start, what I need to read and what I need to do?

[Dracon]

Let&#39;s see if I can help here:

1. Open the CM and create a profile called forgotten battles. Adding all your CM devices. Assuming you have stick, throttle and pedals then: CM Device 1 will be the Joystick, CM Device 2 will be the throttle and CM Device 3 will be your pedals.

2. You will be asked if you want to add a CMS (Control Manager Script) say Yes!

3. Assuming you installed your CM to the default location. Open Widows Explorer that&#39;s your Hard Drives Tree. Find Program Files and expand it by clicking the (+). Now find CH Products and expand by clicking the (+). No you will see the folder Control Manger Folder. Again expand by clicking the (+). The folder called Maps is displayed. Open this folder and find a file called The name you gave your forgotten Battles Profile. Mine is Forgotten Battles.Map There will also be a like .cms file Mine is Forgotten Battles.cms. Open the .cms file with notepad. It will look like this:

// CMS Script File
//
// Game Title:
// Written By:
// Date:
//
script

endScript

4. Now from Spideys post above, copy the lines he refers to and insert it between: Script and endScript. So it looks like this:

// CMS Script File
//
// Game Title:
// Written By:
// Date:
//
script

IF ([JS3.A1 > JS3.A2]) then // LEFT OR RIGHT TOE BRAKES
CMS.A1 = JS3.A1;
ELSE
CMS.A1 = JS3.A2;
ENDIF

endScript

OR!!!! Copy and paste into Notepad what I have above.

5. Now save it by selecting "File" on the top of Notepad and click on "Save". Hey you&#39;re almost there! Close Windows Explorer, you&#39;re done with it.

6. Now launch the CM and open your forgotten Battles Profile. Select the CMS Controls Tab. It&#39;s the one on the left! The top (Larger box) is labled "Buttons". The bottom (Smaller box) is labeled Axes. The bottom (Smaller Box) Axes is the one we want!

7. Click on the upper left button called "A1". Put you cursor over it and it will display "A1".

8. Now, on the right side, Uncheck Center and set the cms #1 axis to CM Device 3 (Your Pedals) in the pull down menu next to DirectX Device. Then under Direct X Axis set it to U axis. Like this:

http://myweb.cableone.net/decon14/images&#...CMS%20sheet.jpg (http://myweb.cableone.net/decon14/images\CMS%20sheet.jpg)


9. Save the profile. It will prompt you to do so if you didn&#39;t.

10. Download the Forgotten battles Profile.

11. Launch Forgotten Battles/ AEP.

12. Now go into Hotas Control in-game under HOTAS and select brake. Step on Left toe brake. Click on Apply.

You are done!

NOTE******** The only other thing I have done in my profile is to make my CH Pro throttle work more friendly. When I push it all the way forward it&#39;s 100% meaning it doesn&#39;t go all the way to 110% wep. I then assigned a WEP button "in game" by setting a button on my Throttle to "Increase Engine Power". It&#39;s under the Engine section. Each time I press the button it increases power by 5%. Hehehe! I now have 2 stages of WEP or 105% and 110%. Cool?

Hey, If you don&#39;t want to mess around and you have the CH Fighterstick, CH pro throttle, and CH Pro Pedals I will gladly send you my profile! It will come as two files named Forgotten Battles.map and Forgotten Battles.cms. Simply put both of these in your C:\Program Files\CH Products\Control Manager\Maps folder. Now launch your CM and Open the Forgotten Battles Profile and download it. Execute Forgotten Battles and go into Hotas Control under HOTAS and select brake. Step on Left toe brake. Click on Apply. I hope this helps you.

My best!
Dracon

Need more? Keep asking!

[MichaelCHProd]

That&#39;s on the money Dracon :salute:

Only thing I do different is I use this script..

CMS.A1 = (JS1.A1/2 + JS1.A2/2);

It gives me input from both pedals and requires both pedals to be down to get full brakes.

[MichaelCHProd]

I am also toying with this script to get some differential analog toe brakes....


CMS.A1 = (JS1.A1/2 + JS1.A2/2);

CMS.A2 = (JS1.A3 + (JS1.A2/2) - (JS1.A1/2));[/b]


Pro Pedals are JS1 for this script and I have set CMS.A1 and CMS.A2 as Control Manager Device 2 X and Y respectively with CMD 2 X as the "Brakes" Axis in IL-2 and CMD 2 Y as the "Rudder" Axis in IL-2.

Tell me what you think.

[Sykstring]

I like the idea of using both brakes for full braking in IL2. If I give you my setup parameters, maybe you can help me set the script up? Here is how I have my pedals set.

Rudder [A3]
Direct X mode CHECKED
DX Device = CM Device 1
Centered Box = CHECKED
DX Axis = R Axis
Sensitivity = 100
Dead Zone = 0


Left Brake [A1]
Direct X mode = Checked
DX Device = None
DX Axis - None
Sensitivity = 100
Dead Zone = 0 {greyed out}


Right Brake [A2]
Direct X mode = Checked
DX Device = CM Device 1
DX Axis = V Axis
Sensitivity = 50
Dead Zone = 0 {greyed out}


Currently my all my equipment is combined. My rudders acting like rudders, my left brake pedal doing nothing, and my right brake pedal acting as my brake, set to 50% sensitivity to keep it from being all or none. It slows me down, but stopping completely takes time.

I appreciate the time and effort of all who have been helping me, and hope to return the favor when possible.

[MichaelCHProd]

Rudder [A3]
Direct X mode CHECKED
DX Device = CM Device 1
Centered Box = CHECKED
DX Axis = R Axis
Sensitivity = 100
Dead Zone = 0


Left Brake [A1]
Direct X mode = Checked
DX Device = CM Device 2
DX Axis - X Axis
Sensitivity = 100
Dead Zone = 0 {greyed out}


Right Brake [A2]
Direct X mode = Checked
DX Device = CM Device 2
DX Axis = Y Axis
Sensitivity = 100
Dead Zone = 0 {greyed out}[/b]

[Sykstring]

I set my rudders up to the above, and then tried these settings in IL2 control panel, but only got 1 brake pedal (the X pedal when X axis chosen in IL2 controls, and Y pedal when Y axis chosen) to work at a time, and it was a full brake applied, and applying both or either combination of pedals didn&#39;t make any difference.


1: Had HOTAS brake set to X axis, both with and without script.
2: Had HOTAS brake set to Y axis, both with and without script.

My standard brake button is B.

The script that I used was this: CMS.A1 = (JS1.A1/2 + JS1.A2/2); from post in here dated Aug 12 2004, 08:18 AM


The script downloaded successfully.

Am I missing something, or thinking it should do something that it shouldn&#39;t?
Thanks again. It&#39;s not that important, as I do somewhat like my original brake settings, just need to raise sensitivity a little more.

[Dracon]

Hmm.......Love this stuff!

Question though? Using this script:

IF ([JS3.A1 > JS3.A2]) then // LEFT OR RIGHT TOE BRAKES
CMS.A1 = JS3.A1;
ELSE
CMS.A1 = JS3.A2;
ENDIF

My brakes appear to work perfectly and historically. The only problem I have is not being able to add Deadband in the CM. I must be oh so careful not to drag a break on take off. Especially that dang P-40 :) The oddest thing???? I am not able to scale or add deadband to my rudder or brakes in-game. All I have is Pitch and Roll??

Questions:
1. Is there a way to add deadband in the CM? Mine is Greyed out.
2. Anyone have a clue as to why there is no scaling for Rudders and Brakes?
3. Which one of the other aforementioned scripts would be more historical?

Thanks for any reply,
Dracon

[Sykstring]

To Dracon,

I think that you need to go into the conf.ini file in IL2FB to change your sensitivity settings for your equipment. Here is what mine looks like.

[rts_joystick]
X=0 1 4 9 16 25 36 49 64 81 100 0
Y=0 1 4 9 16 25 36 49 64 81 100 0
Z=0 10 20 30 40 50 60 70 80 90 100
RZ=0 10 20 30 40 50 60 70 80 90 100 0
FF=0
U=0 10 20 30 40 50 60 70 80 90 100 0
V=0 10 20 30 40 50 60 70 80 90 100 0
1X=0 100 100 100 100 100 100 100 100 100 100 0
1Y=0 100 100 100 100 100 100 100 100 100 100 0
1Z=0 100 100 100 100 100 100 100 100 100 100 0
1RZ=0 100 100 100 100 100 100 100 100 100 100 0
1RX=0 100 100 100 100 100 100 100 100 100 100 0
1U=0 100 100 100 100 100 100 100 100 100 100 0
1V=0 100 100 100 100 100 100 100 100 100 100 0
1X1=0 100 100 100 100 100 100 100 100 100 100 0
1Y1=0 100 100 100 100 100 100 100 100 100 100 0
1RZ1=0 100 100 100 100 100 100 100 100 100 100 0
1U1=0 100 100 100 100 100 100 100 100 100 100 0
1V1=0 100 100 100 100 100 100 100 100 100 100 0
1Z1=0 100 100 100 100 100 100 100 100 100 100 0
1X2=0 100 100 100 100 100 100 100 100 100 100 0
1Y2=0 100 100 100 100 100 100 100 100 100 100 0
1Z2=0 100 100 100 100 100 100 100 100 100 100 0
1RY=0 100 100 100 100 100 100 100 100 100 100 0


Here you can change to your hearts content, just back it up before changing it.


Here is probably where I need to set my brake pedals for pressure sensitivity, ie brake pedal 1/2 way down = 1/2 brakes applied and such. Hope this helps.

[MichaelCHProd]

After you use the script and download the map you need to change the assignments in IL-2


Control Manager Device 2 - X axis = Brakes Axis in IL-2
Control Manager Device 2 - Y axis = Rudder Axis in IL-2.

[Bob Church]

>> 1. Is there a way to add deadband in the CM? Mine is Greyed out. <<

Sure. The value is greyed because the toe brake axes are non-centering and only centering axes get deadzone. Anyway, the trick is that you have to pass the value through a CMS variable so you can modifiy. Suppose that the actual toe-brake is js1.a1. It should normally produce 0 when it&#39;s released and 255 when it&#39;s full depressed. You can&#39;t modify those directly, but you can modify a CMS axis and then use that result. I&#39;ll assume the toe brake is js1.a1 and we&#39;re going to feed it to the sim on cms.a1. You need a script that looks something like this:

if( [js1.a1 < 10 ] ) then
cms.a1 = 0;
else
cms.a1 = js1.a1;
endIf

Which just says that, unless the pedal is down to at least 10, just treat it as 0. If it&#39;s past ten, then feed it whatever the actual toe brake is returning. Up in the GUI, you will have assigned that toe brake to a CM Device axis. You&#39;ll need to unassign the real brake from there and then assign cms.a1 instead, and Voila! Deazone! (Actually "Endzone").

There&#39;s a problem with the above though. The value going to the sim is 0 until it jumps to 10 and it can cause the action to be not too smooth. Depending on the application, that might or might not be something that&#39;s objectionable. It&#39;s easy enough to work around, though. Axis js1.a1 returns 0..255 (all axes do) and that is the same range we want to feed into cms.a1. The only wrinkle is we want a change on js1.a1 from 10 to 255 to result in a change on cms.a1 of 0 to 255. We need to do a little arithmetic:

if( [js1.a1 < 10 ] ) then
cms.a1 = 0;
else
cms.a1 = (255 * (js1.a1 - 10)) / 245;
endIf

The only change is in the second part where the value of js1.a1 is first corrected for the loss of 10 off the bottom end of the range, and then multiplied by 255/245 to stretch what&#39;s left out to cover 0..255. The difference is mainly that when the js1.a1 value exceeds 10, the cms.a1 value starts from 0 and goes to 255 rather than jumping to 10 and going to 255 as the first example did.

- Bob

The StickWorks
http://www.stickworks.com

[Flak_Rambler]

Thanks Dracon and Michael, will work on your instructions this week end and let you know how it goes..
Let me tell you that have no throttle control and my joystick is a Windows one, but will buy a CH Combat stick next week. Have to combine both in order to use the pedals with CFS1
Incidentally, how can I set the rudder sensitivity in order to have a full swing + slow reaction to my feet? If sensitivity is set to 100 get full swing and if set to 25 it hardly moves, however the reaction to my feet remain the same!

[Sykstring]

Michael, I assigned everything as you said in my IL2 controls, but my Y pedal Axis activates rudders and my R axis rudders don&#39;t work. The left pedal acts as the brake, but I can&#39;t figure out how you got "It gives me input from both pedals and requires both pedals to be down to get full brakes." My control manager is set up for rudder pedals like this as per your instructions. I could tell it wouldn&#39;t work because of the AXIS assignments in CM for the rudders. How do I keep my rudders acting like rudders and the Pedals like the brake pedals.


QUOTE
Rudder [A3]
Direct X mode CHECKED
DX Device = CM Device 1
Centered Box = CHECKED
DX Axis = R Axis
Sensitivity = 100
Dead Zone = 0


Left Brake [A1]
Direct X mode = Checked
DX Device = CM Device 2
DX Axis - X Axis
Sensitivity = 100
Dead Zone = 0 {greyed out}


Right Brake [A2]
Direct X mode = Checked
DX Device = CM Device 2
DX Axis = Y Axis
Sensitivity = 100
Dead Zone = 0 {greyed out}

I used this script of yours: CMS.A1 = (JS1.A1/2 + JS1.A2/2);

"It gives me input from both pedals and requires both pedals to be down to get full brakes."


My HOTAS is all mapped to one device. Is this something that can&#39;t be done? Or do I need to remap stuff.

Until I can figure this out, I have to go back to my original way of working brakes, as this is starting to frusterate me again. I have been having a bad 6 months. Thanks for your patience, and do you have some to spare for me?

[MichaelCHProd]

It&#39;s time for you to post you map.

[Sykstring]

Ok, here is the original map I started with before trying to add scripts and the braking stuff.

I have radically changed the CMC file to suit my needs.

Thanks.

What I really want out of my brakes, is to have progressive braking, the more I push my pedal down, the more brake applied.

[MichaelCHProd]

Here you go.

You might have to do some creative mapping to get the assignments right if they are not already setup like it shows in the attached JPG.

[Sykstring]

Thanks, will give this a shot. So many things to learn. Great customer service here.

[Dracon]

Ok "sticky", Now that put me in overload!!

If I am using this script:

IF ([JS3.A1 > JS3.A2]) then // LEFT OR RIGHT TOE BRAKES
CMS.A1 = JS3.A1;
ELSE
CMS.A1 = JS3.A2;
ENDIF

and my Peds are CM Device 3....

I re-wrote your script:

if( [js3.a1 < 10 ] ) then
cms.a1 = 0;
else
cms.a1 = (255 * (js3.a1 - 10)) / 245;
endIf


I just added it to the cms. My final Forgotten Battles.cms looks like this!

// CMS Script File
//
// Game Title:
// Written By:
// Date:
//
script

IF ([JS3.A1 > JS3.A2]) then // LEFT OR RIGHT TOE BRAKES
CMS.A1 = JS3.A1;
ELSE
CMS.A1 = JS3.A2;
ENDIF

if( [js3.a1 < 10 ] ) then
cms.a1 = 0;
else
cms.a1 = (255 * (js3.a1 - 10)) / 245;
endIf

endScript

Hehehe! and "By God She&#39;s Holden&#39; tegether Cap&#39;n".

I mean this works slick. I use a 3 1/2 in binder under my pedals to achieve a more natural angle for my feet, but sometimes that&#39;s just not enough. 10% deadband is perfect!

Thanks all! I came in here to help out and ended up getting more help then I gave. Sometimes I&#39;ll think...Ahh I know the answer to that but then I get too damn lazy to type it out. A little extra effort sure paid off here :)
<S>
Dennis "Dracon" Horvath

[Dracon]

Ahhh! geez! That didn&#39;t work! Ok, Ok, what did I do wrong?
Thanks!
Dracon

[MichaelCHProd]

Ok what did not work?

[Bob Church]

Hey Dennis,

I didn&#39;t recognize you at first! How&#39;ve you&#39; been?

Anyway, I think the problem is that you need to apply the deadzone to the pedal that you&#39;re actually using, in which case probably easier to apply it to the output variable itself:

// First, start out just like you did to select the pedal output to use.
//
if( [ js3.a1 > js3.a2 ] ) then
cms.a1 = js3.a1;
else
cms.a1 = js3.a2;
endIf

// Then apply the deadzone to cms.a1 itself after you
// have made the axis selection.
//
if( [ cms.a1 < 10 ] ) then
cms.a1 = 0;
else
cms.a1 = (255 * (cms.a1 - 10)) / 245;
endIf

Now one or the other will have to go past 10 before they start to track. The way you had it, one pedal got deadzone but the other didn&#39;t.

By the way, it&#39;s not really a 10% deadzone, it&#39;s a 10 count deadzone. 10% would be a count of 25, you&#39;d need to adjust the numbers to use 25 instead of 10 and 255 - 25 = 230 instead of 245. If 10 works, though, that&#39;s probably better.

- Bob

The StickWorks
http://www.stickworks.com

[Dracon]

Bob "sticky" Church,

Heya, :) Yep it&#39;s me again! I was so very pleased to see you in this forum when I finally made the switch to total CH! Between you, MichaelCHProd, and the other genusis here all can be assurd of getting the most out of these excellent controllers. I point many pilots in several Sims to this forum. It rocks!

***For those that don&#39;t know....Bob is the wizard of "Sticks". He has personally helped me with about every stick I have ever had. We go back a bunch of years. My Saitek X-36 with CH pedals was a true challange. The best one was the USB Joysticks had a "memory" in Windows 98 and I couldn&#39;t get them to behave. I was also into GPL (Grand Prix Ledgends) at the time and had a Steering wheel to contend with too. He introduced me to his CH Delete and figured a work around to make everything work! I owe this guy so many bottles of beverage I can never repay him.

That said! Thanks again Bob! So for the purpose of adding info here. This is now my Forgotten Battles.cms:

// CMS Script File
//
// Game Title:
// Written By:
// Date:
//
script

IF ([JS3.A1 > JS3.A2]) then // LEFT OR RIGHT TOE BRAKES
CMS.A1 = JS3.A1;
ELSE
CMS.A1 = JS3.A2;
ENDIF

if( [ cms.a1 < 10 ] ) then
cms.a1 = 0;
else
cms.a1 = (255 * (cms.a1 - 10)) / 245;
endIf

endScript

<S>
Dracon / Dennis

[Flak_Rambler]

Hello Gents,
For a new one to the world of CH like me, you are to much to be follow and ended up with Dracon last script , but somewhere I lost the CM setting of the pedals and still don&#39;t know were the string of numbers go.
Could anyone sumarize everything for me, just to be sure?
Thanks

[Bob Church]

Hi Dennis,

Thanks for the kind words! I&#39;m glad to see you found your way over here, best place to come if you&#39;ve got CH stuff. If you need anything, just ask. You know we&#39;ll figure something out. :) Anyway, good to see you here!

- Bob

The StickWorks
http://www.stickworks.com

[Bob Church]

Flak Rambler,

Well, basically it all goes into the CMS script. To get that, you need to add the "CMS Controls" to your script, then click on the "CM Editor" button and you can type the script in as it&#39;s posted. You need to unassign your normal toe brakes and then assign CMS Axis 1 (cms.a1) to control the brakes on the CMS Control tab in the GUI.

That&#39;s all there is to it! :) I suspect it won&#39;t answer all the questions that will pop up along the way, thought. Have a look at the CMS Scripting section towards the end of the Users Guide, and come on back if you get lost. It&#39;s not nearly as complex as it looks at first. Are you also looking for brakes for IL2 or some other sim? It can make a difference.

Anyway, welcome to the Hangar!

- Bob

The StickWorks
http://www.stickworks.com

[Flak_Rambler]

Hello Bob,
Well, I went trough all the CMS guide as you recommended and guess it takes a lot of time for a person to really master its full potential, but clearly is out of my capacity, lol!
Anyway, did what you told me, copy/paste the script posted by Dracon in his last note (thanks Dracon!), assigned CMS axis 1 and my pedals are now working, not as I would like it , but working.
My final set up looks like this:

Rudder [A3]
Direct X mode CHECKED
DX Device = CM Device 1
Centered Box = CHECKED
DX Axis = Z Axis
Sensitivity = 100
Dead Zone = 0

Left Brake [A1]
Direct X mode = Checked
DX Device = CM Device 1
DX Axis - X Axis
Sensitivity = 100
Dead Zone = 0 {greyed out}

Right Brake [A2]
Direct X mode = Checked
DX Device = CM Device 1
DX Axis = Y Axis
Sensitivity = 100
Dead Zone = 0 {greyed out}

And HOTAS shows:
Rudder: Z Axis ID2
Brakes: X or Y Axis ID2, depending on which toe brake you hit first

What I don&#39;t get yet, is what you call progressive response from the rudder, I tried first to control it by changing Sensitivity, but what it does is to reduce the swing of the rudder. Then I tried with the Gain curve by pulling down the curve in the low-left box and seems to work but not entirely. So any suggestions are welcome.

As mentioned in some notes before, I will buy a CH Combat stick, so I will need your assistance to develop a script for the Pedals and the Stick to work with IL-2 and CFS1. Can we start working on both?
Thanks again,

[Dracon]

You&#39;re more than welcome! :)

Bob and other readers! "25 count" 10% ended up working the best for me. Here&#39;s the final:


// CMS Script File
//
// Game Title:
// Written By:
// Date:
//
script

IF ([JS3.A1 > JS3.A2]) then // LEFT OR RIGHT TOE BRAKES
CMS.A1 = JS3.A1;
ELSE
CMS.A1 = JS3.A2;
ENDIF

if( [ cms.a1 < 25 ] ) then
cms.a1 = 0;
else
cms.a1 = (255 * (cms.a1 - 25)) / 230;
endIf

endScript

Dennis/Dracon

[Bob Church]

Flak Rambler,

>> What I don&#39;t get yet, is what you call progressive response from the rudder, I tried first to control it by changing Sensitivity, but what it does is to reduce the swing of the rudder. Then I tried with the Gain curve by pulling down the curve in the low-left box and seems to work but not entirely. So any suggestions are welcome. <<

I&#39;m not entirely sure I understand what you mean, but I think you&#39;re saying that they sort of "snap" one way or the other, that they&#39;re difficult to control smoothly. Sensitivity would be the wrong thing to adjust, it&#39;s as you say. It just limits the value. If you&#39;ve got an aircraft that&#39;s just particularly sensitive to rudder, then sensitivity would be the best bet, but here it&#39;s probably the Gain setting. You want to go down with it so the curve is more horizontal near the center, more vertical at the ends. That makes it less sensitive around the center, but then picks back up out towards the ends so you still get full rudder travel when you need it. Make sure you&#39;re setting the gain on the CMS.A1 axis, not the actual joystick axes, since that&#39;s the axis that&#39;s going to Windows. Also, make sure that the pedals are calibrated in Direct Mode correctly.

Is that what you&#39;re doing? If that&#39;s still not getting you the result you need, I&#39;m not sure what to suggest. If there are in-game settings, you might need to play with those. How do the pedals look in the Control Manager test screen when the CM is in Direct Mode? They should sit at center and move smoothly to the ends of the display as you move the pedals. Do they look like they&#39;re doing that okay?

>> As I mentioned in some notes before, I will buy a CH Combat stick, so I will need your assistance to develop a script for the Pedals and the Stick to work with IL-2 and CFS1. Can we start working on both? <<

Sure, if you know what you want to do. Any time you&#39;re ready!

- Bob

The StickWorks
http://www.stickworks.com

[Bob Church]

Hi Dennis,

Yeah, 10 isn&#39;t really very much. Going to 25 gives a bit more room to play around in and you should still have plenty of resolution. If you&#39;re experimenting with the values, you can write the script this way:

script

%define DZ_VALUE 25

if ([js3.a1 > js3.a2]) then // LEFT OR RIGHT TOE BRAKES
cms.a1 = js3.a1;
else
cms.a1 = js3.a2;
endIf

if( [ cms.a1 < DZ_VALUE ] ) then
cms.a1 = 0;
else
cms.a1 = (255 * (cms.a1 - DZ_VALUE)) / (255 - DZ_VALUE);
endIf

endScript

and then you&#39;d only need to change the value in the %define statement each time. The other values will all change right along with it.

Actually, if you wanted to get a little carried away you could define it temporarily as:

%define DZ_VALUE js1.a3

That would pick the deadzone value up from the current throttle wheel setting on the main stick. With the wheel full forward you&#39;d have no deadzone, full back would be 255 deadzone. Anyway, you could just play with the throttle wheel until you got it to "feel right", then look at the Raw Data display for the throttle wheel (leave it in Mapped Mode). The value there would be what you want in the %define for the DZ_VALUE. Just go back and substitute it into the script in place of the js1.a3 reference and download again. It seems a bit elaborate, but in the end it could save a lot of trial-and-error downloading, a real pain if you have to shut the sim down each time.

- Bob

The StickWorks
http://www.stickworks.com

[Flak_Rambler]

Hello Bob and Dracon,
My last setting has now a value of 25 (10%), and the gain curve adjusted as recommended, it worked out much better. Rudder response behaves slowly at the begining, increases later on until I get a full swing.

Now if you may, we can move into the next topic, which is to define the settings for my brand new Combat stick, lol, and my pedals. Both should work together with CFS1 and IL-2 FB AEP and the configuration I came out with (all suggestions and recommendations are more than welcome), is as follows:

IL-2 FB - AEP CFS1
Button # 1 Fire Guns Fire Guns
Button # 2 External View Full View
Button # 3 ? Next Target
Button # 4 Release Bombs Release Bombs
Button # 5 WEP WEP
Button # 6 Fire Cannons Fire Cannons
POV Hat Up/Down/Right/Left Up/Down/Right/Left
Padlock Enemy
Hat # 1 /Enemy Ground Padlock View
Padlock Next
Padlock Previous

And of course, tied together with my pedals in a single CMS program!!

As you could appreciate I have tried to keep both sets as similar as possible, but you are the experts and I&#39;m open to any improvement.
Thanks,
Flak

[MichaelCHProd]

Looks fine to me

[Flak_Rambler]

Gents,
I forgot to mention that after I bought the pedals, found out that they won&#39;t work in CFS1 because it doesn&#39;t support more than one game device, and the only way to do it was by means of a CH stick, the question is how can I do it?

[MichaelCHProd]

If you have the Pro Pedals USB and a CH USB stick you merge them together in the Control Manager.

You can do this with the Map Wizard ftp://ftp.chproducts.com/pub/Postings/CM_wizard.jpg check out THIS (http://www.ch-hangar.com/forum/index.php?showtopic=228) thread

Or you can download a BASE map HERE (http://www.ch-hangar.com/forum/index.php?showforum=26) for your specific controllers.


Either way you can then download the CMC (the default commands for the game) from HERE (http://www.ch-hangar.com/forum/index.php?showtopic=119) and then use it to progrma your map.

Instructions on how to select a CMC file in your map are HERE (http://www.ch-hangar.com/forum/index.php?showtopic=238)

Instructions on how to use the CMC file in your map are HERE (http://www.ch-hangar.com/forum/index.php?showtopic=175)

[Flak_Rambler]

Let me work on it this weekend, and will come back to you

[Flak_Rambler]

Hello Gents,
Well, it wasn&#39;t until this weekend that I had the time to work on the CMS for my Combat stick and my Pedals. To make a long story short (and it was long, believe me, lol), what I ended up with is with two programs one for the CFS1 and other for IL-2FB developed from the basic structure the Wizard gave me, to which I inserted the specific commands for the bottons.
However, in both cases for no apparent reazon I got a blue screen from Windows telling me to disconect any new hardaware (which I didn&#39;t do it), and at the end of a memory dump to disc, it rebooted itself and then after, problem didn&#39;t showed up again. This happend a couple of times with CFS1 and I got a similar message with IL-2FB, but asking to run a CHKDSK /F command (which again I didn&#39;t do it). Any idea what is the cause?
As far as the CMS programs are concern, I still have some problems with the assignment of some commands:
For CFS1, can&#39;t assign the Padlock View to button # 4, and the Toe Break in the pedals are not working.
For IL-2FB, I have the same problem with button # 4 and the Throttle, in both cases what I&#39;m doing is to assign the command at time of Setting and Hotas.
Finally and this is not a technical question but do you know if IL-2FB have a similar command to CFS1&#39;s Next Target (Target lock), and Padlock View ??
Any suggestions and recommendations are more than welcome.
Flak

[MichaelCHProd]

Are you running Windows XP SP 2?

[Flak_Rambler]

Negative,
Still in SP-1 and have all updates applied, the last being Microsoft.NET Framework 1.1 Service Pack 1

[Flak_Rambler]

Well, no aswers so far and so I still face the same problems.
My stick and peddals are bearely working but far from what I expected, again:
1) got another blue screen,
2) when test the stick, no buttons appear and same when Settings on CFS1,
3) used Insert Commad and Record Keystrokes to assign button # 5 to release bombs but didn&#39;t work,
4) toe brake pedals don&#39;t work
Can anyone give me a hand?

[MichaelCHProd]

Looks like it may be the same bug that SP2 is showing the world. Hold tight we are on it.

[Flak_Rambler]

Michael,
OK, holding tight !
Just wanted to inform you that I got the blue screen with the IL-2 as well, however, I went back and run a test with the cms program developed by the wizard only (that is, no buttons assigned), and didn&#39;t get the blue screen.
Hope it helps.

[MichaelCHProd]

Noted.

[Flak_Rambler]

Hello Michael, any news ?

[MichaelCHProd]

CM3.5 fixed that bug. Plus it supports the TQ :)

[Flak_Rambler]

Great news!
Now, where and when can I get CM3.5

[MichaelCHProd]

Here at the Hangar or at the CH site

[Flak_Rambler]

Originally posted by MichaelCHProd@Sep 23 2004, 11:26 PM
Here at the Hangar or at the CH site
<div align="right">6884
[/quote]

Michael,
It was not until this week end that have the time to upgrade to CM3.5 and tested.
CFS1 worked just fine, but still have some problems with IL-2. Will let you know in case need help.
Thanks,

[MichaelCHProd]

you are welcome