The same goes for left and right that make up the X-Axis. As up and down make the complete Y-Axis, both will have an identical name. After that, press your left analog stick in the up direction and you will notice that it is given an ABS_ name. Make a note of it's name and repeat with each button until all the names are known. Now, when you press any button on your controller, a few lines of text will appear that make reference to the button's event BTN_ name. Wait for it to finish and you will be met with a message that reads, "Testing. Here you will see a printout of information regarding your controller. Make sure to replace with the controllers event number, then press 'Enter'. Now let's move on to discovering the event codes for each button of the controller by typing: evtest /dev/input/event If you find that your controller is not listed by name, you can substitute the event number when it comes time. In the event that you see multiple entries, look for the listing containing "event" in the title. Press 'Enter' and your device should be listed here by name. To do that that, type: ls /dev/input/by-id/ Next, we'll also need to make note of the event location by name for later use. Once you find it, make a note of it's event number next to the line beginning with H: Handlers=. It can be identified by it's name in the device groupings next to the line beginning with N: Name=. Press 'Enter' and look for the controller in the list of devices. To do this, drop down to the command line by pressing 'F4' on your keyboard, then type: cat /proc/bus/input/devices With xboxdrv now installed, we now need to discover the core-level device input codes for each button and axis on the physical controller, so that we may then map them to the virtual XBox360 controller. Since we will be adding our own custom configuration there later, this command should be removed by selecting 'Disable xboxdrv' from the same menu we enabled it from. Once installed and enabled, a configuration will be added to /etc/rc.local. From here, select 'Enable xboxdrv' and wait for it to finish. Navigate from 'Configuration / Tools' to 'xboxdrv - XBox / XBox360 gamepad driver'. This can be done from the 'RetroPie Setup' listing in the 'RetroPie' menu of Emulation Station. However, this same process can also be used to fine-tune a controller in much the same way that you might normally only find in Windows-based solutions.įirst, we need to make sure xboxdrv is installed. Simply mapping a troublesome controller to be read as a standardized XBox360 controller can solve many communication problems without any additional tweaking. The sheer multitude of existing controllers and their loose implementation of "standards" presents a problem to computer software that has a limited definition of what to expect from controller input. None of what is to follow can be accomplished without this first step. Mapping any controller to be read as a standard XBox360 controller
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |