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

Add axis specific last win SOCD cleaning #1119

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

nevius
Copy link

@nevius nevius commented Aug 18, 2024

It's a feature my Punk Workshop Leverless had before I changed the PCB to a RP2040.

I think it's quite useful for certain games. For example in Street Fighter doing fast dive kicks with Cammy, I would often miss the DOWN input on the QCB, because my thumb as still on UP. With Y-Axis Last Win, the problem can be solved while still allowing for SOCD dashing on the X-Axis.

Is this something you would be willing to include in the main branch?

TODO

  • Translations for JP / CN / BR are still missing

* Add axis specific last win SOCD cleaning

* Fix formatting
@@ -86,7 +86,7 @@ export const tiltScheme = {
tiltSOCDMode: yup
.number()
.label('Tilt SOCE Mode')
.validateSelectionWhenValue('TiltInputEnabled', SOCD_MODES),
.validateSelectionWhenValue('TiltInputEnabled', TILT_SOCD_MODES),
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looked wrong to me, so I changed it.

case SOCD_MODE_UP_PRIORITY: statusBar += " SOCD-U"; break;
case SOCD_MODE_SECOND_INPUT_PRIORITY: statusBar += " SOCD-L"; break;
case SOCD_MODE_FIRST_INPUT_PRIORITY: statusBar += " SOCD-F"; break;
case SOCD_MODE_BYPASS: statusBar += " SOCD-O"; break;
Copy link
Author

@nevius nevius Aug 18, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed this to SOCD-O (for Off) because I wanted to use SOCD-X for the new one. Not sure if that's OK.

@arntsonl
Copy link
Contributor

For this one, we've been talking internally a bit and it might make more sense to have a per axis SOCD rather than the one-off combinational solutions. I see exactly what you're going for, but I think we're still deciding on how to go forward on this one. Thanks for the PR!!

@nevius
Copy link
Author

nevius commented Aug 31, 2024

@arntsonl Thank you. Let me know if I can be of assistance.

@mizma
Copy link
Contributor

mizma commented Sep 29, 2024

@nevius if you need JP translation, ping me via discord.

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

Successfully merging this pull request may close these issues.

3 participants