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

Controls nonresponsive when polling behavior set to "Normal" #7

Closed
Sanaki opened this issue Sep 11, 2022 · 8 comments
Closed

Controls nonresponsive when polling behavior set to "Normal" #7

Sanaki opened this issue Sep 11, 2022 · 8 comments

Comments

@Sanaki
Copy link

Sanaki commented Sep 11, 2022

Seems all controls, including RetroArch hotkeys, stop responding when Latency > Polling Behavior is set to Normal. Both Early and Late work fine for me. I witnessed a report of this from a Windows user before checking it myself.

Arduous: aed5050
RetroArch: libretro/RetroArch@422d2fcf12
Compiler: GCC (11.1.0) 64-bit
Linux Mint 19.3 x86_64

@gouchi
Copy link
Member

gouchi commented May 2, 2023

I confirm this issue also on Linux.

@jmaroeder Maybe you have an idea how to fix this issue ?

Thank you for your help.

@Ninoh-FOX
Copy link
Contributor

fixed

@phcoder
Copy link
Collaborator

phcoder commented Jan 17, 2024

Closing based on last comment

@phcoder phcoder closed this as completed Jan 17, 2024
@gouchi
Copy link
Member

gouchi commented Jan 17, 2024

I am still experiencing this issue using latest RA.

@Sanaki Are you still having the issue ?

@Ninoh-FOX Are you sure you did restart RA after changing polling behavior ?

@Ninoh-FOX
Copy link
Contributor

To me work fine in 1.15.0, this fixed the message "disconnect gamepad port 1" in the RA secuencie.

@Sanaki
Copy link
Author

Sanaki commented Jan 18, 2024

As of libretro/RetroArch@824a0f86fd this is definitely not fixed. Changing to normal locks out controls immediately, without even needing a restart, and loading with it set to normal has the same effect. I haven't tested newer than that commit at this time, but I'd be shocked if a retroarch update changed things.

@Ninoh-FOX
Copy link
Contributor

@gouchi
Copy link
Member

gouchi commented Jan 21, 2024

@Ninoh-FOX I tested your update and it is working.

So, you should provide the fix with a PR ;)

Thank you.

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

4 participants