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
I am experiencing an issue with hotkey sequences to bring up in-game functionality. When I got my EZ Flash Omega, the MENU KEY sequence worked every time. Now it works very inconsistently. I believe this happened because I changed various settings, not because of any hardware issue.
Here is a YouTube video showing the issue. First, I display my settings page, showing that MENU KEY is set to L+R+START. Then, I show that my L, R, and START buttons work perfectly in the main menu. Finally, I boot a game and show that pressing L+R+START rarely brings up the menu (3 out of 24 times in the video).
I think this problem would go away if I could factory reset the device settings. If this is not the case, could you recommend a solution for my issue?
Cheers,
Chris
The text was updated successfully, but these errors were encountered:
chrisdonahue
changed the title
Factory reset feature request
Bug with hotkey sequences
May 12, 2019
I was able to work around this issue by changing L+R+START to L+START+R. If anyone else has a similar issue I would suggest trying different permutations of their hotkey sequence.
Hello,
I am experiencing an issue with hotkey sequences to bring up in-game functionality. When I got my EZ Flash Omega, the
MENU KEY
sequence worked every time. Now it works very inconsistently. I believe this happened because I changed various settings, not because of any hardware issue.Here is a YouTube video showing the issue. First, I display my settings page, showing that
MENU KEY
is set toL+R+START
. Then, I show that myL
,R
, andSTART
buttons work perfectly in the main menu. Finally, I boot a game and show that pressingL+R+START
rarely brings up the menu (3 out of 24 times in the video).I think this problem would go away if I could factory reset the device settings. If this is not the case, could you recommend a solution for my issue?
Cheers,
Chris
The text was updated successfully, but these errors were encountered: