You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RetroArch crashes when using Beetle PSX HW and pressing F1 (open the RetroArch quickmenu) it works fine with other cores.
It also crashes when I press any F-Key even with nothing bound to them.
Expected behavior
Open the RetroArch Quickmenu without crashing. Or whatever function is bound to that F-Key.
Actual behavior
RetroArch crashes
Steps to reproduce the bug
Start RetroArch
Start a PS1 game that uses the Beetle PSX HW Core
Press any F-Key
Bisect results
How would I get an old version to do this?
I only installed RetroArch less than 2 weeks ago, and it worked then.
Version/Commit
tried with these versions
RetroArch 1.14.0 - Beetle PSX HW (0.9.44.1 234433f)
RetroArch 1.15.0 - Beetle PSX HW (0.9.44.1 fd812d4)
Now I updated to RetroArch 1.15 and this happens again.
After some fiddling around I can say this happens when pressing one of the F-Keys even when nothing is bound to them.
Metal-Snake
changed the title
Crash when trying to open the QuickMenu
Crash when pressing one of the F-Keys
Mar 12, 2023
Description
RetroArch crashes when using Beetle PSX HW and pressing F1 (open the RetroArch quickmenu) it works fine with other cores.
It also crashes when I press any F-Key even with nothing bound to them.
Expected behavior
Open the RetroArch Quickmenu without crashing. Or whatever function is bound to that F-Key.
Actual behavior
RetroArch crashes
Steps to reproduce the bug
Bisect results
How would I get an old version to do this?
I only installed RetroArch less than 2 weeks ago, and it worked then.
Version/Commit
tried with these versions
RetroArch 1.14.0 - Beetle PSX HW (0.9.44.1 234433f)
RetroArch 1.15.0 - Beetle PSX HW (0.9.44.1 fd812d4)
Core options
[List all the core options you have changed]
Happens with default options
Environment information
The crashlog which macOS gives:
crashlog.txt
The text was updated successfully, but these errors were encountered: