You're Doing It Wrong: Analogue Vs Digital Settings in E:D

You might want to give this thread a look too. https://forums.frontier.co.uk/showt...Limit-Request-for-Analog-Sticks-Pretty-Please!

Basically, with contemporary analog sticks, I get roughly a 19% multi-axes maneuverability handicap. That being said, I still prefer using them as analog sticks instead of digital for rate control.

This is something that could be resolved with an "axis hotzone limit" if Frontier implemented it as an additional axis control option.
 
Last edited:
The tool is correct, you've assigned digital controls to the analogue directions. For example:

Code:
        <LateralThrustRaw>
                <Binding Device="{NoDevice}" Key="" />
                <Inverted Value="0" />
                <Deadzone Value="0.09825753" />
        </LateralThrustRaw>
        <LeftThrustButton>
                <Primary Device="CHProThrottle2" Key="Neg_Joy_XAxis" />
                <Secondary Device="{NoDevice}" Key="" />
        </LeftThrustButton>
        <RightThrustButton>
                <Primary Device="CHProThrottle2" Key="Pos_Joy_XAxis" />
                <Secondary Device="{NoDevice}" Key="" />
        </RightThrustButton>

If you set up the controls to use the analogue axes you'll find it a lot easier to control.

Ok, it's just been too long and I overlooked the obvious. Thanks for helping me figure it out.

+1
 
While building my HOTAS reference sheet generator I have noticed an ongoing problem in many of the configurations, with a confusion between using analogue and digital bindings.

I'll use pitch as an example. here is a good setting for pitch, using the analogue binding.

View attachment 82906

This binds your stick's Y axis to pitch using the analogue range of the stick, resulting in this basic response curve:

View attachment 82910

No surprises here: as you increase pitch on the stick your ship responds accordingly.

However, many users have their configuration set to something like the below.

View attachment 82912

It doesn't look radically different, but the bindings set here are digital. This means that the response curve now looks like this:

View attachment 82913

So if you're flying with a HOTAS it might be worth checking to ensure that all of your analogue controls are mapped appropriately, otherwise you're missing out on a lot of the precision that should be available to you.

(I'm going to see if I can flag these badly-mapped controls in the reference sheet generator, but am aware that lots of people don't use it so I'm putting this up here as well).

I love this tool, however my configuration HOTAS SAITEK X52 when run against your mapper, keeps telling me I have misconfigured, I have tried many times to follow your example but each time apparently I am still misfigured. Can you help me out, should I be analog or digital?

Many thanks
 
I love this tool, however my configuration HOTAS SAITEK X52 when run against your mapper, keeps telling me I have misconfigured, I have tried many times to follow your example but each time apparently I am still misfigured. Can you help me out, should I be analog or digital?

Many thanks

What are your binds? The generator should give a URL
 
I get the same message, but I guess that's because I use multiple non-standard analogue axes as well as the x52. Perhaps he's using a complex scheme.
 
Hi there - I think I sorted it just after I sent this, the axis has to have nothing bound to it so the pitch up and down is just the joystick not set to pitch up (pull back) and pitch down (push down).

It really has made a huge difference to me already.

So thank you for this tool.
 
Back
Top Bottom