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

Fix Walk Speed Input Polling #765

Open
wants to merge 9 commits into
base: develop/2.4.0
Choose a base branch
from

Conversation

YoshiMilkman
Copy link
Contributor

This adds a define to make accelerating from idle more consistent. Some controllers don't end up outputting a high enough magnitude frame 1, meaning Mario's acceleration can be inconsistent. This PR aims to add a define that fixes that.

Copy link
Collaborator

@arthurtilly arthurtilly left a comment

Choose a reason for hiding this comment

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

not a chance we are having a define for this

@gheskett gheskett added the enhancement New feature or request label Feb 10, 2024
@gheskett gheskett added this to the 2.2 milestone Feb 10, 2024
@gheskett
Copy link
Collaborator

Duplicate of: #506

@arthurtilly
Copy link
Collaborator

does this now fix the thing where if you were walking backwards and held forwards it'd snap forward

@gheskett gheskett modified the milestones: 2.2, 2.3 Mar 2, 2024
@gheskett gheskett changed the base branch from develop/2.2.0 to develop/2.3.0 March 2, 2024 13:41
@gheskett gheskett modified the milestones: 2.3, 2.4 Jul 4, 2024
@gheskett gheskett added the needs verification Needs to be tested to ensure functionality label Jul 4, 2024
@gheskett gheskett changed the base branch from develop/2.3.0 to develop/2.4.0 July 4, 2024 07:09
// When starting a walk, make a few checks and set Mario's speed to 8 on the first frame.
// This ensures Mario's speed is set consistently when starting a walk.
// We use m->actionArg here since it's a global variable that gets initalized to 0 elsewhere.
if (m->forwardVel <= 8.f && !m->actionArg
Copy link
Collaborator

Choose a reason for hiding this comment

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

Probably makes more sense to use actionTimer for this instead of actionArg. actionTimer would need to be incremented somewhere (probably this function) rather than hardset to 1, and would need a conditional to cap it.

This is still a movement change so I'm hesitant to merge this without some sort of define for this, even if it's ultimately not inside a config file. Seems like this isn't even useful for framewalking thanks to the steep slope check, so idk how much benefit this offers anyway (Kaze seems to think it's noticeable though).

Copy link
Collaborator

Choose a reason for hiding this comment

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

WE ARE NOT MAKING THIS A DEFINE!!!!!!

Copy link
Collaborator

Choose a reason for hiding this comment

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

Hey, I did say it'd need to be housed outside of the config file...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs verification Needs to be tested to ensure functionality
Projects
Status: In progress
Development

Successfully merging this pull request may close these issues.

3 participants