-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Increase New 3DS C-stick dead zone #94
Comments
I've actually just noticed I can generate spurious C-stick inputs by manipulating the hinge. I'm guessing the movement of the magnet located on the top-half's right side, which triggers the sleep mode, is interfering with the C-stick. Great design on Nintendo's part. Even with the dead zone at EDIT: For a pure dead zone approach, I can still cause this issue with a dead zone of I can still "force" the issue by manually adjusting the hinge beyond what gravity alone can do, but notably the issue stops again when I reach the next hinge "snap" position. Perhaps there's some software/hardware trickery going on where the console knows to correct the C-stick inputs relative to the magnetic interference from the three "locked" positions, but no specific handling for when you're in-between locked positions? i.e. I don't think the 3DS is strictly aware of the hinge position in an electronic sense, but it may be able to tell "C-stick inputs are being skewed by an amount roughly equivalent to the known interference from the hinge being in this position, so correct them by that amount." I'm sorry that this issue got a lot more complicated than it originally seemed. EDIT2: Video of the behavior: VID_20240320_231722.mp4 |
Feature Request
What feature are you suggesting?
Overview:
5
to a higher value, perhaps10
. Personally, the dead zone of5
set out here ...3ds-hbmenu/source/ui.c
Lines 71 to 72 in c63d531
... is not quite enough on my New 3DS XL sometimes. Often, I'll have no problems, but other times I'll get the list slowly drifting up or down. I made a build locally where I bumped it up to
10
and so far I've seen no issues. Sensitivity of the C-stick when using it intentionally does not feel noticeably reduced to me.Nature of Request:
Why would this feature be useful?
Reduces unintended input without heavily impacting intended input.
Pull request
I'm of course happy to PR this change if desired, but I figured it was worth opening a discussion before unilaterally deciding
10
is the "correct" dead zone value.The text was updated successfully, but these errors were encountered: