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

Deadzone isn't visible to other applications #4

Open
JohnStrunk opened this issue Nov 22, 2018 · 1 comment
Open

Deadzone isn't visible to other applications #4

JohnStrunk opened this issue Nov 22, 2018 · 1 comment
Labels
bug Something isn't working

Comments

@JohnStrunk
Copy link
Owner

Describe the bug
tilt-wizard sets the deadzone, but the changes don't seem to be visible to other applications.

Steps to reproduce
Steps to reproduce the behavior:

  1. Run tilt-wizard
  2. Give it a bit to settle
  3. Launch an application that reads the same device
  4. Note that there is no deadzone in effect

Actual results
tilt-wizard can't set the deadzone

Expected behavior
The deadzone settings should be visible in other applications.

Additional context
Add any other context about the problem here.

@JohnStrunk JohnStrunk added the bug Something isn't working label Nov 22, 2018
@JohnStrunk
Copy link
Owner Author

It's not clear whether Windows actually supports this or not. DXTweak says DZ settings aren't saved/preserved, but we don't need long-term, just current setting.

This may be related to not calling IDirectInputJoyConfig8::SendNotify after setting the device calibration.

SendNotify notes:

As a stopgap, we could output the recommended DZ percent as a part of the application output. Looks like the DZ should be: stdev * 4 * 100 / axis_range

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant