Yipi:
It is a "relatively" simple thing to do using CH Control Manager 2.x's scripting ability. The old Pedals "combined" the two axes into a single rudder input "electrically" (i.e., using a resistor network) when the switch was set to "plane." As you know, there is no such switch on the Pro Pedals, so you have to combine the two axes programmatically (i.e., you have to write a simple script to do it).
Here is a simple one-line script that accomplishes the feat:
cms.a1 = 127 + (js3.a2 - js3.a1)/2;
The script assumes that your pro pedals are the third controller in the map (i.e., that they are the third tab from the left, after a stick and throttle, most likely). If not, just change the two occurrences of "js3" to "js1" or "js2", as appropriate.
In the one-line script above, js3.a1 is the left toe brake axis and js3.a2 is the right toe brake axis. This is just the way that Control Manager defines them (note that the physical rudder axis is js3.a3) and is evident from the Control Manager GUI. You can figure out why the simple one-line equation works with the following information: When not depressed, each toe axis registers a value of 0 and when fully depressed each registers a value of 255. The physical rudder is zero when fully left, 127 (or 128) when centered, and 255 when fully right.
Note that this will work only if your map has CMS scripting enabled, so that there is a "CMS Controls" tab in the Control Manager GUI. Click on the CMS Controls tab and assign the "A1" axis to whatever DirectX axis you want to be the rudder input. For example, you can use "CM Device 1, R Axis" if you want.
If you have no experience with Control Manager, this may seem a bit confusing. If you want to send me a profile with CMS controls enabled, I will insert this bit of functionality and send it back to you.
I hope this is helpful,
JNOV
