-
Notifications
You must be signed in to change notification settings - Fork 61
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
Lode Runner joystick buttons trigger extra man cheat #202
Comments
This is an interesting bug. For various reasons, I had great difficulty testing this in a VM and gave up. However, I do have some observations that might help locate the underlying issue. The extra man "cheat" in Lode Runner is CTRL-SHIFT-2. This is interesting for a couple of reasons.
EDIT: I was unable to reproduce the problem in a Linux Mint VM with Linapple built from this repo at the time of this post. I used the mouse buttons to emulate the paddle buttons. They functioned normally in Lode Runner and did not appear to produce any keyboard activity at all in further testing. |
I will pair my controller with my PC again and see if the problem occurs in AppleWin as well. PS With a wired controller, the problem does not occur in AppleWin. I am assuming that provided the software detects the joystick, it doesn't matter whether it's a wireless or wired controller. (I'd rather not have to try to re-pair my controller with the Raspberry Pi after because that was a real pain.) |
A few thoughts: (1) Possibly avoidable if CTRL-SHIFT-2 was not used by LinApple. I might have to investigate making a local build of LinApple... is it possible to change the control code? |
Hi,
I have tested this with multiple different ROM files and it seems to happen on all of them. This is with Retropie on a Raspberry Pi 4 with the most recent build of linapple as of 2023/08/30.
If I use the keyboard (I think U and O for digging) this doesn't happen, but with joystick, either left or right button does a dig, but it also gives a free life, which is ... just annoying?
The text was updated successfully, but these errors were encountered: