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

[Feature Request] An option for proper handling of Left+Right and Up+Down #322

Closed
EricICX opened this issue Jul 16, 2022 · 5 comments
Closed

Comments

@EricICX
Copy link

EricICX commented Jul 16, 2022

Almost every other NES emulator in existence, such as FCEUX, Nestopia, and Mesen, has an option for not allowing the illegal sets of inputs, Left+Right and Up+Down.
image
image
image

Currently, the absence of this feature makes it so that the MiSTer cannot be used to speedrun certain games, so it would be nice if this was implemented.

@Kitrinx
Copy link
Member

Kitrinx commented Jul 16, 2022

AFAIK nothing prevents this. You simply need a controller that physically allows it.

@Kitrinx
Copy link
Member

Kitrinx commented Jul 16, 2022

I just double checked to be extra sure, nothing in the NES core will prevent any combination of buttons. It generates NES protocol directly from what it receives from the framework, so there is no actionable items here. If you feel the framework's controller handling is interfering with your ability to do this, the correct place for an issue is here:

https://github.com/MiSTer-devel/Main_MiSTer/issues

@Kitrinx Kitrinx closed this as completed Jul 16, 2022
@EricICX
Copy link
Author

EricICX commented Jul 16, 2022

AFAIK nothing prevents this. You simply need a controller that physically allows it.

I'm not sure if you understood what I asked. I was asking for an option for these inputs to be disallowed with a controller that physically allows them, such as a keyboard.

@Kitrinx
Copy link
Member

Kitrinx commented Jul 16, 2022

even so, it is not a core-level decision, the core just works like the hardware did, and things like SNAC cannot be restricted in such a way as they are opaque. If you want to add such a restriction, this is still a component of the framework which does all the keyboard/joystick input handling.

@EricICX
Copy link
Author

EricICX commented Jul 16, 2022

Okay thank you, I'll ask there.

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

No branches or pull requests

2 participants