Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Deadzone control for both ends of axis #46

Open
diVineProportion opened this issue Oct 11, 2018 · 6 comments
Open

Feature: Deadzone control for both ends of axis #46

diVineProportion opened this issue Oct 11, 2018 · 6 comments

Comments

@diVineProportion
Copy link

Any chance for something like this:
image
In both UCR and UCR-C you can only control the deadzone around the center of the axis correct?

@Snoothy
Copy link
Owner

Snoothy commented Oct 23, 2018

Great suggestion, I will look into this at a later point

@evilC
Copy link
Collaborator

evilC commented Oct 23, 2018

What code is used for each plugin to handle deadzones is dictated by the plugin itself.
There would be nothing stopping you from writing new code, and making a plugin use that code instead for deadzones.
Plugin calling DZ function
Existing DeadzoneHelper class

So you could write an alternative DeadzoneHelper, then make a plugin that uses it.

@Snoothy
Copy link
Owner

Snoothy commented Oct 23, 2018

Having a dual slider version and quad slider, as seen above, as input selectors would be a great addition to existing GUI configuration (int, string, enum)

@evilC
Copy link
Collaborator

evilC commented Oct 23, 2018

I am against anything using sliders, period.
UNLESS:
There is an equivalent text box to type exact value.
OR
You can use eg arrow keys to select exact value.
Otherwise, unless the slider is over 100px wide, it's impossible to select all values, and even then it's a right pain to select the exact value you want.

@evilC
Copy link
Collaborator

evilC commented Dec 7, 2018

A thought - given that the DZ on each of the scales is identical, a linear sensitivity option of <100% would achieve the same result, so all the examples in the above image are currently supported by the AxisToAxis plugin

@diVineProportion
Copy link
Author

diVineProportion commented Jan 13, 2019

I completely agree about having the text box to help hone in on the specific value.

The DZ are not necessarily identical on each end. I'll give you an example. First I will point out that the GUI I referenced in the OP was from the Saitek (now under Logitech) X52 Professional and I didn't think to show one of it's other features. If you right clicked in the one of the DZ areas where you see the current DZ value, you get this:

image

So the identical linked DZ's work great for something like my RX axis seen here
zxfievvepv

But what about the case of my throttle quadrant where physically I have each of the axis set at 50% (Throttle, Pitch and Yaw are all equal in straight line right at 50%), but logically they appear like this:
image

If I didn't have the ability to unlink the DZ's, I'd be forced to sacrifice axis positions as seen here

image

Whereas unlinking the axes would allow:
image

You may be wondering why exactly i care to do this when they are not logically at 50%. The thing is that it isn't important what they are at, rather that I know i can physically put each axis at the physical 50% mark, and I know that they will be residing in a DZ and not interfere etc,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants