8000 occasional N64 button glitches · Issue #171 · retrospy/RetroSpy · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

occasional N64 button glitches #171

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.

Sign up for GitHub

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

Jump to bottom
Open
alkamaass opened this issue Jan 5, 2021 · 7 comments
Open

occasional N64 button glitches #171

alkamaass opened this issue Jan 5, 2021 · 7 comments
Labels
known issue Acknowledged bug, but is low priority to fix.

Comments

@alkamaass
8000
Copy link

https://youtu.be/XOhhDUVIEfU?t=117

I have all the blink reduction options turned on, and I still get occasional button glitches though, is there a specific part of my input display I should be insulating more or something? Or is this a software issue
image
@zoggins
Copy link
Member
zoggins commented Jan 5, 2021 via email

@zoggins zoggins added the more info needed Further information is requested label Dec 1, 2021
@zoggins
Copy link
Member
zoggins commented Dec 9, 2021

closing from inactivity. Feel free to repopen if necessary.

@zoggins zoggins closed this as completed Dec 9, 2021
@Haplo064
Copy link
Haplo064 commented Jul 10, 2022 •
edited
Loading

Heya, I come with more information on this.
The majority of games work fine, but some games have repeated 'ghost' inputs, even when not doing any rumble or memory card reading. This is from the main menu of Jet Force Gemini, for example.

RetroSpy_885rOr0ySA

No inputs from the controller during this, no memory card inserted, no rumble pack inserted.
If you need, I can probably capture the packets if there's a guide on how to do so.

From the times that I've encountered this, it's likely that the devs did some funky code on the games, as it's not super common, but the games that either push the system a bit or have other issues themselves.

@zoggins zoggins reopened this Jul 10, 2022
@zoggins zoggins added need to test Something that I need to test. and removed more info needed Further information is requested labels Jul 11, 2022
@zoggins zoggins added known issue Acknowledged bug, but is low priority to fix. and removed need to test Something that I need to test. labels Nov 24, 2022
@zoggins
Copy link
Member
zoggins commented Nov 24, 2022

After some testing this is a known issue of using the Arduino to spy on the N64. The arduino is just barely fast enough to handle the datastream from the controller and in some cases it just can't do it right hence the random inputs. The only 100% way to ensure this not happening is to switch to a Teensy 3.5 for spying instead of Arduino, which is much much faster. unfortunately right now Teensy's are really hard to find, but its an option when they become available again.

@Haplo064
Copy link

Hi Zoggins,

Is there anything preventing trying it out on a Teensy 4.1? The board is basically the same, just faster. Plus they're in stock compared to the 3.5.

@zoggins
Copy link
Member
zoggins commented Nov 25, 2022

I just ordered one. I know it will require some minor code changes, but I am pretty sure I can get it working.

@zoggins
Copy link
Member
zoggins commented Nov 25, 2022

I got it working with a Teensy 4.0. I have a Teensy 4.1 on the way to test, but it should be fine. I will do a release in a few days. I will also likely port Gamecube also, which suffers from the same problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
known issue Acknowledged bug, but is low priority to fix.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Haplo064 @zoggins @alkamaass
0