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

Pressing Down in Menu Jumps down 2 Spots #572

Open
TradeDraft opened this issue Jan 8, 2025 · 4 comments
Open

Pressing Down in Menu Jumps down 2 Spots #572

TradeDraft opened this issue Jan 8, 2025 · 4 comments

Comments

@TradeDraft
Copy link

I am using the Retroarch 1.20.0 and latest version of the Dosbox Pure Core

When Pressing Down goes down 2 spots and not 1. It's okay going up as go up by 1 instead of 2.

Video Showing what Happens:

https://youtu.be/OSf6gaJ1ddw

@schellingb
Copy link
Owner

schellingb commented Jan 8, 2025

Platform? Device? Input driver? Input device? Using RetroArch's game focus?

It is very likely that this isn't something that happens everywhere so you have to provide these crucial details when reporting an issue. Attaching a video is great but this one doesn't add anything that wasn't covered with the words you have already written.

@TradeDraft
Copy link
Author

TradeDraft commented Jan 8, 2025

Windows 10 64 Bit

on a PC

Input Driver is Dinput

Using Microsoft Keyboard

Happens when Game Focus is On and Off

@PoloniumRain
Copy link
Contributor

Can't replicate this on Win10 or 11. Although i remember a similar problem existing ages ago, but it was fixed...

What region layout is your keyboard? Does it happen with a controller?

It can possibly be caused by some random peripheral interfering, so you could try disconnecting everything else and see if that helps. Or sometimes after updating RetroArch from an older version, it can cause problems. For the latter you could try deleting the retroarch.cfg file in the RetroArch folder. It will reset all settings to default.

@TradeDraft
Copy link
Author

TradeDraft commented Jan 10, 2025

I deleted the retroarch.cfg file to start a Fresh Config File and so far it seems to have fixed the Issue

I updated from 1.19.1 to 1.20.0

Had to do something like before when I was having a Issue that Re-Setting a Fresh Config File that it Fixed

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

3 participants