-
Notifications
You must be signed in to change notification settings - Fork 81
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
Phantom 2040 - random inputs during lag frames #348
Comments
Are you using a USB controller, BliSSter, or SNAC? |
Oh just realized you are probably using a RetroSpy ;) I wonder if the core is slightly more sensitive than a real system. Does the same thing occur without the RetroSpy hardware involved? |
I'm using Super Famicom controller + Raphnet adapter. Yes, confirmed that it still happens without RetroSpy or any sort of input capture software on. The inputs that it decides to fire seem random, sometimes it will be Start, sometimes A, sometimes B, etc. |
Can you test what the controller does with the two snes test roms for me? snip It almost sounds like a multiplexing issue or something... BTW, if you are a speed runner and want to skip the USB port, host, and minimal MiSTer binary's handling of USB, you can use SNAC instead --> https://misteraddons.com/products/serial-native-accessory-converter-snac + https://misteraddons.com/collections/parts/products/bliss-style-controller-adapters-for-snac - or - https://misterfpga.co.uk/product/mister-snac-controller-adapters/ - (albeit this won't work with a usb input capture software like RetroSpy). |
Here's the controller tests from both roms: https://drive.google.com/file/d/12cwF2gkB9VLA7N9hQSHeSxTcP6pC-bXg/view?usp=sharing |
Is this still happening? If so, where? I have tried to reproduce this using spread in the beginning levels but it didn't happen. |
I'm a speedrunner of Phantom 2040 and there's some issues with the inputs that I have come across. When mashing during heavy lag frames, random inputs will start firing. This does not happen on console.
One example: https://drive.google.com/file/d/1fJ9wnh_I9YBgdWkxwxiFaQ-BKQ8Ao921/view?usp=sharing
In this example, when trying to use spread to lag out the game, you can see from the input viewer that I'm only mashing Y and X, however you can also see that the rope comes out (green line), which is an A input.
There are other times where START will spam, which pauses the game and brings up the menu, instead of A even though it was never pressed. If you need more examples I can try and get some video of them.
The text was updated successfully, but these errors were encountered: