What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Fix emulator input by finding the layer where the signal stops, then change only that layer. First verify that the operating system receives button and stick events and that the frontend assigns the intended device to player one. Next check the emulator or core mapping, then apply a per-game remap only when one title needs an exception. Treat a missing BIOS as a separate core-and-path problem: identify the exact core, confirm its system directory and required filename, and use a legally obtained dump from your own hardware or another licensed source. A new controller helps only when the existing hardware or input protocol is unreliable; it cannot repair a wrong remap or BIOS directory.
Start by locating the failing layer
Questions such as “Why is my controller not working in RetroArch?”, “How do I remap a gamepad in an emulator?”, “Where do I put BIOS files in RetroArch?”, “Why does my controller work in the frontend but not in the game?”, “Why are my buttons mapped wrong?”, and “Why does my emulator say BIOS missing?” describe several different failures. The same symptom can come from a disconnected device, an incorrect frontend profile, a core-level layout, a game-specific override, or a system file that the core cannot find.
Use this order: hardware and operating-system events, frontend detection, emulator/core input source, then game mapping. Do not edit a per-game profile while the frontend cannot see any input. Conversely, do not replace a working controller when the core is simply assigned to the wrong port.
| What you observe | Likely layer | First action |
|---|---|---|
| No buttons or axes appear in the operating system | Cable, Bluetooth pairing, charge, controller mode, or driver | Reconnect or re-pair, verify the device in the operating-system list, and test its events before opening the emulator. |
| The operating system sees events, but the frontend does not | Frontend input driver, device selection, or a virtual-device conflict | Disconnect extra controllers and virtual input devices, then select the intended device as player one. |
| The frontend menu works, but gameplay buttons are wrong | Core remap, game remap, or stale profile | Reset the active mapping, confirm the core layout, and save at the narrowest useful scope. |
| Only analog movement, triggers, or pressure controls fail | Unassigned axes or an incorrect axis direction | Test and bind each axis independently; do not assume that working face buttons prove the whole controller is mapped. |
| A game reports a missing BIOS | Core-specific system directory, filename, region, or required/optional status | Read that core’s BIOS instructions and verify the active system directory and exact file name. |
Verify the controller before changing emulator settings
1. Reduce the test to one physical device
Temporarily disconnect other gamepads, steering wheels, keyboard-to-gamepad utilities, remote-play devices, and virtual controllers. Multiple devices can claim player one or make an automatic profile attach to the wrong hardware. Leave one controller connected while diagnosing it.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
2. Check the physical and operating-system path
- For USB, try a known-good data cable and a different port. A charge-only cable can power a controller without carrying input data.
- For Bluetooth, confirm pairing, charge level, and the controller’s intended mode. Some pads expose different identities for XInput, DirectInput, or console modes.
- Open the operating system’s game-controller or device list and confirm that the controller appears under the expected name.
- Press every face button, shoulder button, trigger, D-pad direction, and stick. Confirm that the operating system reports each event and that a stick returns to center.
If no event appears at this stage, the emulator cannot correct the problem. Resolve the connection, mode, battery, or driver issue first. A driver-update utility can be an optional Windows troubleshooting step after the physical connection and input mode have been checked; it is not a BIOS tool and does not replace emulator configuration.
3. Confirm frontend ownership and player one
Open the frontend’s input or controller menu and identify the device assigned to player one. Move one stick or press one button while the menu is focused. If the frontend responds, its basic input path is alive. If it does not, stay at this layer: check the selected input driver, reconnect the device, and remove virtual-device conflicts instead of editing core or game remaps.
RetroArch: keep frontend, core, and game mappings separate
RetroArch exposes a controller through a common RetroPad abstraction. That abstraction is not the same as the layout expected by every libretro core, and a core layout is not necessarily the same as one game’s controls. A menu can therefore work while gameplay remains wrong.
Frontend or RetroPad binding
Use the frontend-level binding for the physical controller’s identity: which physical button is RetroPad A, B, X, Y, the D-pad, Start, Select, and each analog direction. This is the reusable profile that should follow the controller across cores. Save it only after testing all required buttons and axes.
Core remap
A core remap changes how a particular console core receives RetroPad input. Use it when the core’s expected console layout differs from your preferred physical arrangement. For example, a face-button orientation that feels natural in one console family may need a different arrangement in another. A core remap should affect that core rather than every system in RetroArch.
Game remap
A game remap is the narrowest override. Use it when one title has an unusual control scheme, a second-player exception, or a special button requirement. Do not use a game remap to compensate for a broken global profile; that creates a one-game fix and leaves the underlying controller wrong elsewhere.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Reset stale profiles before creating a new one
Automatic profiles can become stale after changing input drivers, switching controller modes, or testing manual bindings. Clear the existing mapping or restore the default controls first. Then create a fresh profile while only the intended controller is connected. Test the menu, a core, and one game before adding further overrides.
- Disconnect extra and virtual devices.
- Reset the current frontend or RetroPad mapping.
- Bind face buttons, D-pad, Start, Select, both sticks, and triggers while watching the displayed input names.
- Launch the target core and check whether its console buttons correspond to the expected actions.
- Save a core remap only if the core layout needs a change.
- Save a game remap only if that individual title still needs an exception.
After saving, close and reopen the core or game to verify that the profile loads. If the menu mapping works but the game does not, inspect the active remap and core assignment rather than repeating the frontend binding.
PCSX2: choose the input source before mapping buttons
PCSX2 has its own controller configuration and is not interchangeable with RetroArch’s RetroPad layers. Its documentation describes SDL as the preferred input source because it is cross-platform and should work for most controllers and operating systems. XInput is a Windows fallback, while DirectInput is best reserved for older or unusual devices when the other sources are unsuitable.
Configure the input source
- Open
Settings > Controllers. - Select SDL first and check whether the controller appears with live button and axis events.
- Use automatic mapping when PCSX2 offers a profile for that device.
- If SDL does not expose the controller correctly on Windows, try XInput.
- Use DirectInput only as a last resort, then test every control manually.
Automatic mapping is not guaranteed for every controller. When no suitable profile exists, bind each required button and analog axis yourself. A partially mapped device can appear functional in menus while a game that needs both sticks, triggers, or pressure-sensitive inputs remains unplayable.
Map port one before port two
Select the first controller port and verify it before configuring a second player. Games generally expect player one on port one; assigning the working device to port two can look like a dead controller even though the mapping is correct. Test Start, Select, the D-pad, both analog sticks, shoulder buttons, triggers, and any pressure-sensitive controls required by the game.
When a PCSX2 game still ignores input
- Confirm that the game is using the same controller port you configured.
- Check that the active input source did not change when you switched from SDL to XInput or DirectInput.
- Re-run automatic mapping or clear the profile if a previous controller mode left stale assignments.
- Move each stick through its full range and check that the axis direction is not inverted or assigned to a digital button.
Dolphin: match the emulated controller to the game
Dolphin requires the emulated controller type to match what the game expects. In its controller configuration, assign the physical device to the intended port and choose the corresponding emulated type. An unconfigured port may be treated as a dummy plugged-in controller, so a game can behave as though a controller is present while ignoring your actual device.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
For a physical GameCube controller
Dolphin documents support for the official Wii U GameCube Controller Adapter and compatible clones. This is a focused solution for players who specifically need original-style GameCube hardware; it is not the general answer to a RetroArch mapping or BIOS-path problem.
For another gamepad
- Open Dolphin’s controller configuration dialog.
- Choose the game-appropriate emulated controller type.
- Select the physical device for the correct port.
- Bind the D-pad, face buttons, shoulder buttons, triggers, Start, and both sticks.
- Enable background input only if you deliberately need input while Dolphin is not focused, and understand that it can make accidental input easier.
- Launch one known-good game and verify that the port and controller type remain selected.
If a GameCube title starts with no response, check the port assignment and emulated type before replacing the gamepad. Dolphin’s configuration model is separate from RetroArch’s core and game remaps.
Test analog axes and special controls explicitly
Face buttons are the easiest controls to notice, but many games depend on analog ranges, trigger thresholds, or pressure sensitivity. A controller can therefore “work” while still being incorrectly mapped.
- Move the left and right sticks slowly to every edge and confirm that each direction reaches the expected axis.
- Press each trigger through its full travel. If it is analog, verify that the emulator sees a range rather than a single on/off event.
- Tap every D-pad direction separately; a diagonal-only or stuck direction usually indicates a wrong hat or axis assignment.
- Test Start and Select, plus console-specific buttons such as Home, Z, or stick clicks when the core exposes them.
- Check for drift with the controller untouched. A drifting axis can trigger menus or movement even when all bindings are nominally correct.
Correct an axis at the layer where it was assigned. If every core sees the same reversed stick, fix the physical or frontend binding. If only one core is reversed, use a core remap. If one game alone needs a different sensitivity or button, keep the exception in that game’s profile.
Missing BIOS files are a separate, core-specific problem
A BIOS is a copy of the operating system used by the hardware that a core emulates. It is not a controller profile and not a game ROM. Libretro’s documentation says BIOS files usually go in RetroArch’s system directory, but the exact location, filename, region, and requirement are defined by the individual core.
Use this BIOS checklist
- Identify the exact console core and version, not merely the frontend name.
- Open RetroArch’s directory settings and inspect the active System/BIOS directory. The label can vary slightly by build, so use the path shown in your installation rather than assuming a default folder.
- Read the core’s documentation for the required filename, capitalization, subfolder, region, and whether the BIOS is optional or mandatory.
- Check the filename and capitalization exactly. A correctly dumped file in the wrong region folder is still a missing BIOS to the core.
- Use a legally obtained dump from your own hardware or another licensed source. Do not treat a BIOS as an ordinary free download.
- Restart the core or frontend after correcting the path, then test one known-good title.
Do not place a BIOS beside the game merely because that is where the game file is stored. A standalone emulator’s directory is also not automatically the directory used by a libretro core. The active system directory and the core’s documented subfolder take precedence.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Libretro Dolphin core
For the libretro Dolphin core, the GameCube BIOS is optional for most games. Libretro notes that certain titles, particularly those relying heavily on system fonts, can be unplayable without it. The documentation specifies a file named IPL.bin in a region-specific folder under the Dolphin user directory. Follow that core’s stated region folder and capitalization; do not substitute a similarly named file from another system.
Recommended Free Tools
Libretro PCSX2 core
The libretro PCSX2 setup requires BIOS configuration and directs the relevant files to RetroArch’s system directory, including a lower-case pcsx2 directory for the documented setup. A BIOS placed in a standalone PCSX2 folder, beside a game, or in another frontend’s system directory will not be found by this libretro core unless the core is explicitly configured to use that location.
What a BIOS error does and does not mean
- It does mean that the active core cannot locate or validate a required system image at its configured path.
- It does not prove that the controller is defective.
- It does not mean every game for that console needs a BIOS; requirements vary by core and title.
- It does not authorize downloading copyrighted system files from an unlicensed repository.
Choose hardware only when hardware is the actual problem
Once the operating-system and frontend tests show that the current controller is defective, unreliable, or stuck in an incompatible mode, a replacement can be sensible. Choose by input protocol, automatic-mapping support, operating-system compatibility, and whether you need original-console hardware.
| Option | Best fit | What it can solve | What it cannot solve |
|---|---|---|---|
| USB or XInput-compatible gamepad | General PC emulation across common frontends and standalone emulators | A failed controller, unreliable cable, or device mode that exposes an unsupported input path; XInput is a documented Windows fallback in PCSX2. | Wrong RetroArch core/game remaps, an incorrect emulator port, or a missing BIOS. |
| GameCube controller adapter for PC | Dolphin users who specifically want original-style GameCube controllers | Connection of supported official-style GameCube hardware; Dolphin documents the official Wii U adapter and compatible clones. | Generic gamepad mapping problems, unrelated cores, or BIOS-path errors. |
| Optional Windows driver-update utility | A device that still fails at the operating-system layer after cable, pairing, mode, and emulator input-source checks | Potentially locating or updating an operating-system driver. | Supplying BIOS files, creating core remaps, fixing a wrong player port, or guaranteeing emulator compatibility. |
Do not buy a controller to fix a message that says a BIOS is missing. Do not buy an adapter because one game has a stale game remap. Hardware is the final choice after the software layer has been identified.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common failure branches and precise fixes
The frontend sees the controller, but the game does not
Compare the active core or standalone emulator with the frontend settings. In RetroArch, inspect whether a core remap or game remap overrides the working RetroPad profile. In PCSX2, confirm the selected input source and controller port. In Dolphin, confirm the emulated controller type and assigned port. Reset only the stale layer, then test again.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Buttons are consistently shifted or rotated
Clear the automatic profile and bind the physical buttons again while watching the displayed names. If the mismatch occurs in every core, correct the frontend or RetroPad profile. If it occurs in one core, save a core remap. If it affects one title, save a game remap rather than changing the global arrangement.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Only one player works
Disconnect unused devices and assign the intended controller explicitly to player one. In PCSX2, configure the first controller port before the second. In Dolphin, verify that the game-appropriate controller is assigned to the expected port and that the port is not left as a dummy device.
Input works until another device is connected
Virtual and secondary devices can take the player-one slot or trigger a different automatic profile. Reconnect devices one at a time and watch which name the frontend assigns. Keep the intended controller selected instead of relying on whichever device was enumerated first.
The BIOS file exists, but the core still reports it missing
Check the active system directory, core-specific subfolder, exact filename, capitalization, region, and whether you are running a libretro core or a standalone emulator. A file can be valid yet invisible to the program because it is in the wrong installation’s directory.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchAutomatic mapping is close but not correct
Do not layer more overrides onto a stale profile. Reset it, select the documented input source, and map the missing buttons and axes manually. Automatic mapping is a convenience, not a guarantee; PCSX2 explicitly provides a manual fallback for unsupported controllers.
A repeatable setup routine for future systems
- Connect one controller and prove that the operating system reports every required event.
- Assign that device to player one in the frontend or emulator.
- Choose the emulator’s preferred input source: SDL first in PCSX2, XInput as a Windows fallback, and DirectInput only when necessary.
- Create or reset the global/frontend profile and test all buttons, sticks, triggers, and system controls.
- Launch the core or standalone emulator and verify the correct controller type and port.
- Apply a core remap only when the console layout needs a different arrangement.
- Apply a game remap only for a title-specific exception.
- If a BIOS warning appears, stop changing controller mappings and follow the exact core-specific path and filename instructions.
- Restart the relevant core or emulator and retest one known-good game after each change.
This sequence keeps a working layer intact while you repair the next one. It also makes rollback straightforward: remove the newest core or game override instead of rebuilding every controller profile.
Legal and practical BIOS handling
Obtain BIOS files by dumping them from hardware you own or through another licensed source permitted in your jurisdiction. Documentation explains what a BIOS is and where a core expects it; it does not authorize downloading copyrighted system files. Keep each dump associated with the exact console region and core instructions that require it, and avoid renaming files unless the documentation calls for a specific name.
Keep game content and system files organized separately. A clean directory structure makes it easier to tell whether a failure is a missing game, a missing BIOS, or an input configuration issue, and it prevents a standalone emulator’s files from being mistaken for RetroArch’s active system directory.
Free tools Windows power users keep installed
One-click scans. No signup required.
When the controller is fixed but the game still feels wrong
Once every input event reaches the correct port, check the game’s own control options and sensitivity settings. Some titles deliberately use unusual layouts, require an analog trigger range, or expect a system-specific button. Preserve the working global profile and make only the smallest game-level adjustment needed. If the same adjustment is needed across that entire console core, move it up to a core remap instead of maintaining multiple identical game exceptions.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
