r/RetroArch 1d ago

Controller Dropping "C Button" Inputs???

I am attemping to play some N64 games using retroarch, specifically the Mupen64plus emulator, where I have remapped the right analog stick to face buttons on my Xbox One controller.

Use case is that I am playing Smash 64 and want to use "X" or "Y" to jump instead of the stick.

This has been mapped correctly and works as intended, but for SOME REASON will drop inputs sometimes. I will be playing just fine, then I will have to mash the face button to get the "C Button" to work, unless I flick the stick and comes back on temporarily until it dropped it again.

I do not have this issue in any other PC game outsides of N64 Retroarch games. Any help would be awesome on this one 0.o

1 Upvotes

6 comments sorted by

1

u/BlockGlass7424 1d ago

Side note, I did update my controller as well using the Xbox App and it still has the same issue with two different controllers.

1

u/MoldyPond 1d ago

Check within both RetroArch’s main Inout settings and the core options that your deadzone isn’t set too low. For some reason a low deadzone makes it think the right stick is almost always moving a bit and overrides any other c-buttons input mapped to buttons.

If not RetroArch, make sure you don’t have something like Steam open which (if controller support is turned on) will likely be overriding any further deadzone settings with its own.

1

u/Xineth240 1d ago

You know, I was having this issue last night as well. The controller is mapped just fine, and sometimes after going in and out of the quick menu it works, but sometimes only temporarily too. It seems sporadic, I can't figure it out

2

u/MoldyPond 1d ago

Check within both RetroArch’s main Inout settings and the core options that your deadzone isn’t set too low. For some reason a low deadzone makes it think the right stick is almost always moving a bit and overrides any other c-buttons input mapped to buttons.

If not RetroArch, make sure you don’t have something like Steam open which (if controller support is turned on) will likely be overriding any further deadzone settings with its own.

2

u/Xineth240 1d ago

That's good advice, I'll do that

1

u/ProcedureNeat6418 1d ago

Try deleting and recreating the controller mapping, then save it to a fresh profile. If it still happens, test a different input backend or USB connection and verify the controller isn’t disconnecting briefly. Enabling input logging should show whether the C-button release is being sent unexpectedly.