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

Senik · Dec 28, 2015

ExoForce said:
Avoiding interdiction with a rocker switch.

Can you please explain this one? I'm assuming you mean setting yaw/pitch/roll to a switch so you can instantly hit the maximum rate, but I don't see how that would make a huge difference. The escape vector doesn't move so rapidly that I can't keep up using analog controls.

ExoForce · Dec 30, 2015

I dont use jaw on joystick. If somebody is trying to interdict me, I will switch my Hotas-X rocker-switch yaw (lateral thrusters in combat) from analog to digital. Much faster reaction, so horizontal component of the escape vector can be followed faster. I can also anticipate change of escape vector horizontal direction, so I will press oposite direction as soon it slows down.

Disclaimer: non native speaker, also did some measurement in some controllers software where I got this idea in the first place. It is much faster, at least for me...

benkei · Dec 30, 2015

That site with the binding upload is awesome!
I did it out of curiosity, not expecting anything really, and that sheet is great aaand...

...it stated "misconfiguration noticed" or something like that and told me that my 'Thrust up/down' was badly configured like in his example!eleven!1!

Thanks!

M. Grey · Dec 30, 2015

Thx! Awesome site, have some rep!

CHOPP3R · Dec 30, 2015

jgm said:
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

Thank you! I'd somehow managed to set my turret on my SRV up like this when I set keybindings after the Horizons update! I was wondering why it was so bloody hard to aim at anything!

Senik · Dec 30, 2015

ExoForce said:
Much faster reaction, so horizontal component of the escape vector can be followed faster.

Thanks, this makes sense. The yaw controls on the X52 are a bit sluggish. I'll give this a try and see if it helps me. +Rep

glojo · Jul 24, 2016

Just found this old thread and many many thanks to the author BUT....

How do we delete the incorrect key bindings please?

Bacalao · Jul 24, 2016

glojo said:
Just found this old thread and many many thanks to the author BUT....

How do we delete the incorrect key bindings please?

Select it and hit the escape key.

glojo · Jul 24, 2016

Bacalao said:
Select it and hit the escape key.

What service. Much appreciated and a MILLION THANK YOU's to the author of this thread

Nomad15A · Nov 6, 2016

This thread is complete gold. I've been playing over a year with most of my direction controls mapped to a digital on the HOTAS. It was always kinda crappy but much better than mouse and keyboard so I just went with it.

Cheers for fixing me.

VerticalBlank · Dec 1, 2016

I'm seeing a false positive for this on my vertical thrust landing override for the Thrustmaster FCS HOTAS: http://www.mcdee.net/elite/binds/fsayic
Thought you should know.

Alec Turner · Dec 1, 2016

Great thread! Knew about this already but did suspect that a lot of new HOTAS X owners were binding their directional controls as digital inputs.

Incidentally, the following post may also be relevant re: using a yaw axis curve to refine the use of HOTAS yaw to control the SRV (apparently it made a massive improvement to handling for Aken).

https://forums.frontier.co.uk/showt...n-like-hell)?p=4849238&viewfull=1#post4849238

jgm · Dec 1, 2016

VerticalBlank said:
I'm seeing a false positive for this on my vertical thrust landing override for the Thrustmaster FCS HOTAS: http://www.mcdee.net/elite/binds/fsayic
Thought you should know.

This was an issue with the control definition for vertical thrust; should now be fixed. Thanks for reporting it.

shadragon · Dec 1, 2016

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

I have my HOTAS set in this manner. If I pull back a little, my nose comes up slightly, if I pull back hard, it comes up quickly. There is no 1 or 0 digital input, it transitions gracefully.

Nothing against the curves software, but my out of the box config works great.

VerticalBlank · Dec 1, 2016

jgm said:
This was an issue with the control definition for vertical thrust; should now be fixed. Thanks for reporting it.

Fix confirmed: http://www.mcdee.net/elite/binds/oltmon
impressively fast response! Can't rep you any more right now

IndigoWyrd · Dec 1, 2016

This is good information to be sure. I'll definitely check my setup. This could explain a good number of things I've always wondered...

Ugh.. back to Tutorial mode to experiment with controller changes.. but better than paying for Rebuy when things go south!

---

Yep, sure enough, I was doing the digital too... oh, that sounds really bad... Great info! Not too hard to get use to the change, but I did have to tweak the deadzone a bit.

TomT · Dec 3, 2016

First of all, great tool - it's very helpful.

I have a CH Pro Throttle, and use the small joystick for thrusting (up, down, left, right) and I believe I have it configured properly in the bindings, however the tool is showing it's misconfigured. Each of these thrust directions is assigned to a position of the joystick, not an axis.

Here is the file if you're interested:

https://drive.google.com/file/d/0B2s01RfdX1rQQUo5VW5TQnVTcmc/view?usp=sharing

Thanks

PS: Here's the results in your config tool: http://www.mcdee.net/elite/binds/glbgsh

jgm · Dec 3, 2016

TomT said:
First of all, great tool - it's very helpful.

I have a CH Pro Throttle, and use the small joystick for thrusting (up, down, left, right) and I believe I have it configured properly in the bindings, however the tool is showing it's misconfigured. Each of these thrust directions is assigned to a position of the joystick, not an axis.

Here is the file if you're interested:

https://drive.google.com/file/d/0B2s01RfdX1rQQUo5VW5TQnVTcmc/view?usp=sharing

Thanks

PS: Here's the results in your config tool: http://www.mcdee.net/elite/binds/glbgsh

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.

Kingston@# · Dec 3, 2016

thought I would check out this and give my hotas a go instead of 360pad. all I get though is..
No bindings file supplied; please go back and select your binds file as per the instructions.

Please direct questions and suggestions and support requests to the thread on the official Elite: Dangerous forums.

jgm · Dec 4, 2016

Kingston@# said:
thought I would check out this and give my hotas a go instead of 360pad. all I get though is..
No bindings file supplied; please go back and select your binds file as per the instructions.

Please direct questions and suggestions and support requests to the thread on the official Elite: Dangerous forums.

Are you selecting your binds file with the "choose file" button?