How to run RetroPie without controllers?

johnklos

Hi,

I'd like to use RetroPie, but I can't figure out how to get past the controller configuration screen with just a keyboard and mouse. How do I use my keyboard as my primary controller?

Thanks!

n2185x

@johnklos It turns out that you can press a key on the keyboard when you're on that screen and it'll recognize the keyboard as a "controller". You then just have to press the key you want for each controller button that it shows (hold a key for a while to get it to assign no key to the button).

For getting around the EmulationStation menu, you'll need to do assignments for the D-pad directions, A, B, X, Y, Start, and Select.

johnklos

@n2185x Thank you. Although the interface is poor and there's no way to navigate or correct errors, I can get through the whole thing.

I then get to where every button is configured. The "OK" button is selected, but I can't proceed after that unless I read the docs which say to press whatever is configured as the "A" key.

The on-screen message really should say how to proceed...

Ashpool

@johnklos said in How to run RetroPie without controllers?:

I then get to where every button is configured. The "OK" button is selected, but I can't proceed after that unless I read the docs which say to press whatever is configured as the "A" key.
The on-screen message really should say how to proceed...

In a way it is telling you "how to proceed": You acknowledge the OK by pressing the button/key you configured as the A-Button. ...

johnklos

@ashpool No, it's actually not telling me how to proceed. If, on the screen, it said, "Press the button configured to "A" to proceed", that would be telling me how to proceed.

Ashpool

@johnklos I've said "in a way": It is a regular API/UI requester asking for confirmation/cancelation... part of the RTFM and learning procedure we all went through, and in time you will see and understand that, in Computer(OS/API/UI) context, there are certain patterns which do not need any further explanation, as they are simply and frankly put self explaining through context/environment (of course it helps if one had previous experiences on game consoles and computers and assembled the knowledge of concepts over time and systems to understand the context) ...

Edit: Ok, this addition to my post may make it sound like even more patronizing (which isn't my intend).... but I think it may make my previous message more understandable (for some users):

RetroPie 1st Setup:

We have a clean system with an unidentified method of input/user feedback

System asking for a device/how input should be handled
(remark: we are still considering no keyboard no input besides 2beConfigured Controller)

We are setting up the Axes/Buttons/Key for the recognized controller
*In the End System is aksing to Accept/Reject...

So What? We have here a System that previously had no information about our input device, so it is IMHO most logical that the keys now needed are taken from the configuration we just went through.... And A/B Button whatsoever (Tab/Return/etc.) is intuitive for most people with background knowledge, for others... well, in previous times we had manuals of book size coming with computer systems and at least dime novel size for consoles, so @johnklos you did made it right in reading the docs and learning about the A-Key ;), but the reading should have been before the using ]:>

johnklos

@ashpool There's the issue - if one has prior experience with RetroPie, it'd make sense, but it one doesn't, then it's not exactly intuitive.

The controller configuration really should say, "Press (A) to continue".

Ashpool

@johnklos Sorry, my Edits of my previous Message collided with your answer...
But saying press (A) to continue would be IMHO missunderstandable in the same way by others [edit: by/of/from different background]... The only essential change for the initial configuration I see is in the line of adding the information that: if no gamepad is detected, the keyboard may substitute for one...