A lot of you with the CH pedals will have already figured this out, and some might never have though of it, but for reference, here's how to do it, and a link to the original forum thread. Massive, massive thanks to Thorne1 on the War Thunder forum:
http://forum.warthunder.com/index.php?/topic/49883-assistance-with-ch-pro-pedals/
Here's Thorne1's method:
In CH Control Manager start the Control Wizard by clicking on the icon of a blank page with a lightning on it.
First page of the wizard add the CH controllers you want to map, select the ProPedals by clicking on it and press "Okay".
Wizard asks you if you want to combine controllers, this will create virtual input devices. Select "Yes".
For starters, select 4 axes and 4 buttons, press "Okay".
Wizard asks if you want CMS capability, select "Yes".
Press "Finish".
The second tab in the main window will now show your first mapped input device which should be the ProPedals. The name of the first device in the first controller GUI tab will be named "JS1" in CMS scripts.
Click on the toe brake axes in the window and note the text on the right side changes to the name of the axis. Right of the axis name in brackets, it'll show "A1" for left toe brake and "A2" for right toe brake, the rudder axis is "A3".
The third tab "CMS Controls" shows the buttons and axes of the virtual device(s). Select it.
Select axis A1 (leftmost, upper row in "Axes") on this tab. Check checkbox "DX Mode".
In "DirectX Function" in "DX Device" select "CM Device 1", check "Centered", in "DX Axis" select "R Axis"
Start CMS Editor by clicking on the "CM Editor" icon (7th icon in toolbar from the left).
Copy/paste the following script:
SCRIPT
CMS.A1 = 128 + (JS1.A2/2) - (JS1.A1/2);
ENDSCRIPT
This script will map the input from the two toe axes (JS1.A1 and JS1.A2) to the first axis of the virtual device(s) (CMS.A1).
Just close the script editor window then (contents won't be lost).
"Download" this mapping you just created to activate it by pressing the "Download" icon (8th icon in toolbar from the left).
You have now added a virtual controller device to Windows.
Check "Devices and Printers" in Windows start menu to find a new "HID-compliant game controller". This is the virtual "CH Control Manager Device 1".
Start the Test/Calibrate function of CH Control Manager by pressing the "Test/Calibrate" function icon (10th icon in toolbar from the left).
Select "Control Manager Device 1" when asked which device to test/calibrate.
You should now see you have a controller with an R axis that can be controlled with presses of the two toe brake axes.
You should now save you mapping for later reloads and mapping by "downloading" by pressing the disk icon.
Btw. after "downloading" there is no need to still have CH Control Manager running, the mapping will work even without it.
After reboots just load the saved mapping and apply mapping again by "downloading" it.
In WT then just map the yaw axis to the axis of the virtual device.
No need for a key, just map an axis to an input device axis.
WT won't know and won't care it's only a virtual input device.
http://forum.warthunder.com/index.php?/topic/49883-assistance-with-ch-pro-pedals/
Here's Thorne1's method:
In CH Control Manager start the Control Wizard by clicking on the icon of a blank page with a lightning on it.
First page of the wizard add the CH controllers you want to map, select the ProPedals by clicking on it and press "Okay".
Wizard asks you if you want to combine controllers, this will create virtual input devices. Select "Yes".
For starters, select 4 axes and 4 buttons, press "Okay".
Wizard asks if you want CMS capability, select "Yes".
Press "Finish".
The second tab in the main window will now show your first mapped input device which should be the ProPedals. The name of the first device in the first controller GUI tab will be named "JS1" in CMS scripts.
Click on the toe brake axes in the window and note the text on the right side changes to the name of the axis. Right of the axis name in brackets, it'll show "A1" for left toe brake and "A2" for right toe brake, the rudder axis is "A3".
The third tab "CMS Controls" shows the buttons and axes of the virtual device(s). Select it.
Select axis A1 (leftmost, upper row in "Axes") on this tab. Check checkbox "DX Mode".
In "DirectX Function" in "DX Device" select "CM Device 1", check "Centered", in "DX Axis" select "R Axis"
Start CMS Editor by clicking on the "CM Editor" icon (7th icon in toolbar from the left).
Copy/paste the following script:
SCRIPT
CMS.A1 = 128 + (JS1.A2/2) - (JS1.A1/2);
ENDSCRIPT
This script will map the input from the two toe axes (JS1.A1 and JS1.A2) to the first axis of the virtual device(s) (CMS.A1).
Just close the script editor window then (contents won't be lost).
"Download" this mapping you just created to activate it by pressing the "Download" icon (8th icon in toolbar from the left).
You have now added a virtual controller device to Windows.
Check "Devices and Printers" in Windows start menu to find a new "HID-compliant game controller". This is the virtual "CH Control Manager Device 1".
Start the Test/Calibrate function of CH Control Manager by pressing the "Test/Calibrate" function icon (10th icon in toolbar from the left).
Select "Control Manager Device 1" when asked which device to test/calibrate.
You should now see you have a controller with an R axis that can be controlled with presses of the two toe brake axes.
You should now save you mapping for later reloads and mapping by "downloading" by pressing the disk icon.
Btw. after "downloading" there is no need to still have CH Control Manager running, the mapping will work even without it.
After reboots just load the saved mapping and apply mapping again by "downloading" it.
In WT then just map the yaw axis to the axis of the virtual device.
No need for a key, just map an axis to an input device axis.
WT won't know and won't care it's only a virtual input device.
