t flight rudder pedals mapping problem

[cmdr Temeleen]

Hi,
have been searching for ages but found no solution, so wanted to ask here.

I cannot for the love of god figure out how to map this thing. No matter what I do ed always uses only one pedal axis as full control (so i can use only one pedal and have it half pressed to stand still), the other pedal is disregarded. Originally I wanted to use them as thrust forward / backward (as I did with old racing pedals and it worked fine without any problem), however this happens for any axis i try (yaw, roll...). Always mapped on one pedal only.

I got the target software but i cant really figure out what to do with it. I tried remapping axis in there but that had basically no effect (im not sure if im doing it right tough). Also theres a swtich on the usb adapter between airplane and car, tried both and noticed no difference.

Anyone?

edit: only thing that i was able to do was use one pedal as throttle in forward only and use second pedal as reverse thrust switch, but thats kinda meh solution :/

 

[DNA-Decay]

Hi,
have been searching for ages but found no solution, so wanted to ask here.

I cannot for the love of god figure out how to map this thing. No matter what I do ed always uses only one pedal axis as full control (so i can use only one pedal and have it half pressed to stand still), the other pedal is disregarded. Originally I wanted to use them as thrust forward / backward (as I did with old racing pedals and it worked fine without any problem), however this happens for any axis i try (yaw, roll...). Always mapped on one pedal only.

I got the target software but i cant really figure out what to do with it. I tried remapping axis in there but that had basically no effect (im not sure if im doing it right tough). Also theres a swtich on the usb adapter between airplane and car, tried both and noticed no difference.

Anyone?

edit: only thing that i was able to do was use one pedal as throttle in forward only and use second pedal as reverse thrust switch, but thats kinda meh solution :/

ED could definitely use a pass to look at some usage cases for Rudder Pedals.

I don't quite get what you're saying is the problem.
But for my Saitek pedals I have this issue:
Rudders are generally a 3 axis joystick.

Yaw is the obvious axis with a center all good, thanks.
Now the left and right toe axes - what can we do with them that is useful.

In my case I have right thrust mapped to left toe and vice versa.

This means that when my right foot and toe is at full extension I am turning right and strafing left.
Describing a circle around my target.
Good good thank you.

BUT!

You can map the left <> right lateral thrust to an axis with a center.
OR
You can have full lateral thrust mapped to two key binds.

But you can't have left thrust on one axis and right thrust on another.
So instead of fine lateral thrust control in my toes, I only have full On / full Off control.

Which is similar to OP's problem.

I believe he wants to be able to separate "halves" of an axis into each foot.

It's no good to have forward and back thrust mapped into one toe, because you have to hold your foot halfway forever.

He wants forward thrust on an axis, and back thrust on another axis.

I want left thrust on one axis, and right thrust on another axis.

It's the same problem, different mappings.

Please FDev, have a look at usage cases for rudders - and implement seperable axes for forward reverse, left right, and up down.

I know it's kind of an edge case, but Elite is a driver of hardware purchases.
It's worth doing well.

 

[Pville_Piper]

From what I understand the TARGET software will only work with the TFRP pedals if they are attached to the new throttle unit.

I know what you mean about the frustration of the axis being separate on each pedal. I currently bind the as up and down thrust with no analog.

 

[Krycka]

yes more axis please.

 

[Gorgath]

I had that exact issue with my CH Pro Pedals. What I had to do was program the pedals (with some scripting) with the following rules:

- Assign the pressing of both pedals to only one axis.
- Make that when both pedals are unpressed, that axis is in middle value.
- When pressing right pedal, value goes from middle to top.
- When pressing left pedal, value goes from middle to bottom.

Then assign that axis in game to horizontal thrusters.

And it works like a charm.

I don't know if the thrustmaster programming software will let you do stuff like that, but I hope the idea helps you.

Good luck!

 

[Daitya Zo]

I had that exact issue with my CH Pro Pedals. What I had to do was program the pedals (with some scripting) with the following rules:

- Assign the pressing of both pedals to only one axis.
- Make that when both pedals are unpressed, that axis is in middle value.
- When pressing right pedal, value goes from middle to top.
- When pressing left pedal, value goes from middle to bottom.

Then assign that axis in game to horizontal thrusters.

And it works like a charm.

I don't know if the thrustmaster programming software will let you do stuff like that, but I hope the idea helps you.

Good luck!

I'm using digital increments / axis + to get my ch pedals working. Did you script that to make it happen? Want to share a few lines of ch script when you get a chance? I've got a pretty fancy foghterstick setup but just got the pedals.

 

[Gorgath]

I'm using digital increments / axis + to get my ch pedals working. Did you script that to make it happen? Want to share a few lines of ch script when you get a chance? I've got a pretty fancy foghterstick setup but just got the pedals.

First of all, sorry to the OP for the offtopic!

This is how I did it:

No need to say this only works for mapped mode.

1. Set DX Device and Axis to "none" to both Left and Right Brakes.
2. In the CM Editor, use write this:

script
%define PEDAL_L js3.a1
%define PEDAL_R js3.a2
%define TROTTLE_POSITION cms.a1
cms.a1 = (128 + (PEDAL_R/2)) - (PEDAL_L/2);
endScript

I think that for this to work, where it says js3.a1 and js3.a2, the number you have to use depends on where your pro pedals appear in the CH Control Manager. I mean, in the manager tabs I've got "Programsettings|Fighterstick|ProThrottle|ProPedals|CMSControls", and the number it works for me is 3. So you'll have to see in what position your pedals are, and change it accordingly, if needed.

3. In CMS Controls, select "Axis 1" (Click the first square below Axes) and select a DX Device and an axis for it.

Done. If you test/calibrate that selected device, it should work.

As I don't know if I made myself clear, so I'll let you the link to where I learnt all this, maybe it's easier for you that way:
http://www.ch-hangar.com/forum/inde...ls-any-way-to-combine-toe-brakes-to-one-axis/

If you have any doubts and can't get it to work, just PM me, and I'll try to help

 

[Candergart]

The absolute easiest solution would still be an option in game to map separate axis to throttle up / down (or back and forward), and for SRV throttle too (Analog, not digital)

I tried installing Vjoy to create a virtual joystick that would use 2 separate axis but I just do not have the energy to sit and fiddle just to get something like that to work.
So as it is no, I don't even use my pedals.

Please o please give us the option to use separate axis (analog input) for up/down, forward/back , driving throttle back and forward.

/Me

 

[DNA-Decay]

First of all, sorry to the OP for the offtopic!

This is how I did it:

No need to say this only works for mapped mode.

1. Set DX Device and Axis to "none" to both Left and Right Brakes.
2. In the CM Editor, use write this:

script
%define PEDAL_L js3.a1
%define PEDAL_R js3.a2
%define TROTTLE_POSITION cms.a1
cms.a1 = (128 + (PEDAL_R/2)) - (PEDAL_L/2);
endScript

I think that for this to work, where it says js3.a1 and js3.a2, the number you have to use depends on where your pro pedals appear in the CH Control Manager. I mean, in the manager tabs I've got "Programsettings|Fighterstick|ProThrottle|ProPedals|CMSControls", and the number it works for me is 3. So you'll have to see in what position your pedals are, and change it accordingly, if needed.

3. In CMS Controls, select "Axis 1" (Click the first square below Axes) and select a DX Device and an axis for it.

Done. If you test/calibrate that selected device, it should work.

As I don't know if I made myself clear, so I'll let you the link to where I learnt all this, maybe it's easier for you that way:
http://www.ch-hangar.com/forum/inde...ls-any-way-to-combine-toe-brakes-to-one-axis/

If you have any doubts and can't get it to work, just PM me, and I'll try to help

Hmm.
I wonder if the CH software can recognize saitek pedals.
Or maybe the Warthog software can do this trick, and I can splash out on those pedals.
Or maybe the Warthog software recognizes saitek pedals.
Hmm.

Actually I can probably test that - I'm not running the Warthog Target software at the moment.
I've got a couple of other problems that it might clean up.
(Slightly off center calibration on the joystick and saitek throttle quad center cals are jittery).

It's a shame that target software is so opaque.


My rig is a bit of a Frankenstein monster of classy and crass.
Bit like me.

Spoiler

 

[Tervuren]

Same problem, and all these years later I'm not finding a solution after a lot of looking through all the bindings. I would love to have fowards on one pedal, and reverse on the other for flight
.
The SRV offers these axis as a split binding option, it'd be nice to have it in flight mode for thrust as well.

 

[cmdr Temeleen]

acrually i solved this issue years ago, i found thurstmaster target script for combining two pedals into one axis. works like a charm

 

[Misty_Dark]

acrually i solved this issue years ago, i found thurstmaster target script for combining two pedals into one axis. works like a charm

Sad that we don't have this as options, so instead of having to combine two axis, we would be able to assign one axis for thrust forward and then add another axis for thrust backward... instead of having to use full range where the middle is zero point.

I would expect this to work like
Assign axis and get an option for if it is full range or just forward/up/etc and if that is choosen, we get another axis option to assign a secondary axis for the other direction, so this could be reused for all analog axis.


Part of this is already present for the throttle, but here we get the option to assign a button for reverse thrust.