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

Workaround for slow functions causing skipped inputs #801

Open
Vortetty opened this issue Jan 24, 2024 · 0 comments
Open

Workaround for slow functions causing skipped inputs #801

Vortetty opened this issue Jan 24, 2024 · 0 comments

Comments

@Vortetty
Copy link

This may not be an issue with the library itself, but this is seemingly the best place to ask.

I am attempting to adapt an xbox controller to a gamecube console, which is a much slower protocol. It's taking between 1.09 and 1.12ms to send a single frame to the gamecube, generally being 1.11ms. after adding code to convert the xbox status report into a gamecube status report, it takes around 1.5-1.9ms (depending on implementation). this is seemingly enough that even having constant polling outside of that or even running 20 polls before reading the controller's state, it still skips most inputs or has stuck inputs.

are there any workarounds for this? i have attempted running the gamecube status reports even just once a second and it is still enough to throw off the usb, i can't really find any conflicts between the two libraries aside from interrupts being disabled to send the gamecube's status reports, if that is an issue is there a rate at which i could run one library to not interfere, or a way to set the shield to have slower polling, since i only need it polled at 60hz or so at the most rather than the 250hz it seems to use now

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

No branches or pull requests

1 participant