RetroArch is the official front end for the libretro API. RetroArch and libretro provide a way to take an existing emulator and load that emulator as a library or 'core'. RetroArch then handles the input (controls) and output (graphics and audio) while the emulator core handles the emulation of the original system. With a few simple changes to the emulator source code, almost any existing emulator could become a libretro core.

In RetroPie, the libretro emulator cores are identified with a lr- in front of their name. For example, lr-snes9x2010 is the libretro core of the SNES emulator called snes9x2010. Dblue stretch vst download.

The Retrolink adapter does not follow the USB HIB specification (section 5.10 and 6.2.25) and returns out-of-bound values. Contrary to the former, the HID driver strictly follows the specification and ignores such values. I have not been able to get my Retrolink NES USB controller to work with Windows 10 at all. It worked fine with Windows 7 but once I updated to 10 it no linger worked. If anyone hears of a solution please let me know! We developed the game using a 360 controller which was recommended by Steam in order to claim full controller support.

RETROLINK N64 USB DRIVERS DOWNLOAD. Nes controller review. Kb raw blame history. Driver become redditor, usb controller project64, uninstall re install drivers. Usb enabled wired controller, buy retro link wired. Nintendo entertainment system. Super smash bros gamecube, ports plug play. How to set up a retrolink nintendo 64 controller. Dec 25, 2018 RETROLINK GAMECUBE DRIVER - Seller information jackswarehouse Learn more - opens in a new window or tab. Log in or sign up in seconds. Should be a good controller for playing.

RetroArch and libretro provide ability to configure controllers once for many emulators instead of having to configure each emulator individually. However, RetroArch also provides the freedom to configure specific emulators individually and even individual games differently if the user wants. This allows a specific setting or button mapping for a certain console or even just for a certain game.

For emulators which are not libretro cores, there are emulator-specific configurations under the respective system's wiki page.

The RetroPad concept

When you configure your controller in EmulationStation, the RetroPie setup script automatically configures RetroArch with the same controls.

RetroArch controls map real-world controller buttons to a virtual controller called a 'RetroPad'. A RetroPad does not exist in real life, it's a concept only within RetroArch. A RetroPad has an ABXY layout like a SNES controller plus four shoulder buttons and dual analog sticks like a Sony DualShock.

You don't have to map all of the RetroPad buttons to a real world button. If your real controller has less buttons than a DualShock, then the virtual RetroPad also has less buttons, that's perfectly fine.

As RetroArch starts an emulator core, it maps the RetroPad configuration to the emulated system's original controls. The mapping for many consoles is represented by the pictures below and on each system's wiki page. If you wish, you can reconfigure this control mapping, either for all RetroArch, for a specific system, or even for a specific ROM.

Retroarch Controls

There are 3 main ways to configure input for RetroArch:

Autoconfigurations - made in EmulationStation
Hardcoded Configurations - made by editing retroarch.cfg file(s)
Core Input Remapping - an easy way to do specific control configurations for specific cores, made in the RetroArch RGUI

AutoConfigurations

RetroArch controls have been integrated into EmulationStation and will be the first thing you see when you boot from the RetroPie SD image the first time. You can also access it from the start menu within EmulationStation under the Configure Input option. Your joypad is automagically configured for libretro (RetroArch) emulators when you configure your controller in EmulationStation. You'll know if your controller has been automagically configured if you see a flash of yellow text on the bottom of the screen with your gamepad ID when you start a game.

The following diagrams are for the 3 most common controllers: Super Nintendo, Xbox 360, and PlayStation 3. They can be used as a reference when configuring your controllers. Each emulator page on the wiki has a diagram of the original controller for its respective console that will correspond to the same inputs listed below.

After you've configured your controller the autoconfig will be created here:

This is an example config for a USB SNES controller

As seen above in the config for the USB SNES controller, each input on the controller has an associated value. When setting up the controller in EmulationStation, these values are then assigned a respective action on RetroArch.

For example, suppose the 'A' button on a USB SNES controller has a value of '1.' When setting up the controller, EmulationStation would prompt you to press the 'A' button on your controller. Pressing the 'A' button would then record into the config file as input_a_btn = '1', so RetroArch will know that the 'A' button on your physical controller corresponds to the 'A' button on RetroArch's virtual controller, the RetroPad. Therefore, the next time you play a game such as Super Mario Bros. pressing the 'A' button will tell RetroArch to press the 'A' button on its RetroPad, causing Mario to jump. If you accidentally pressed the 'B' button with a value of '2' during setup when it prompted for 'A,' then it would be recorded into the config file as input_a_btn = '2', so if you want to jump in Super Mario Bros., you would have to press 'B' on your controller.

Hotkeys

Hotkeys are combinations of buttons you can press in order to access options such as saving, loading, and exiting games. The following defaults are set automatically the first time you set up your controller from EmulationStation (the numbers will vary depending the controller you use).

Default joypad hotkeys:

Hotkeys	Action	Code Example
Select	Hotkey	input_enable_hotkey_btn = '6'
Select+Start	Exit	input_exit_emulator_btn = '7'
Select+Right Shoulder	Save	input_save_state_btn = '5'
Select+Left Shoulder	Load	input_load_state_btn = '4'
Select+Right	Input State Slot Increase	input_state_slot_increase_btn = 'h0right'
Select+Left	Input State Slot Decrease	input_state_slot_decrease_btn = 'h0left'
Select+X	RGUI Menu	input_menu_toggle_btn = '3'
Select+B	Reset	input_reset_btn = '0'

Determining Button Values

If you want to edit the entries in the .cfg file for your controller, you will need to know the values corresponding to the buttons on your controller. Usually the relationship between the two can be deduced by looking at the file and noting the entries' names along with the values next to them, assuming that the values have not been jumbled from previous edits or been mixed up due to unknown issues. For example, the USB gamepad above has an entry for input_x_btn = '0', indicating that the 'X' button on the controller (or the button that you associated as 'X' during controller setup in EmulationStation) has a value of '0.'

On the other hand, maybe you are not sure if the values in the .cfg file is correct or the file is missing entries for buttons that are available on your own controller, such as a 'Home' button. You can run jstest (joystick test) in the terminal by selecting Quit EmulationStation (a keyboard will be required for the following steps).

In the terminal, type and enter
jstest /dev/input/js0

Replace js0 with js1, js2, js3, etc. as needed if not detected.

A multitude of rows and columns should appear. Pressing buttons or moving analog sticks/joystick will cause various entries in the columns to swap between on and off and fluctuate through a r

Retrolink Gamecube Controller Driver Download