Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Most second-controller problems in Resident Evil 2 Remake co-op mods come from one of four causes: the mod assigned the wrong device, Player 2 controls were never mapped, Windows exposes the pad differently from the game, or REFramework and the co-op mod are on incompatible versions. Fix them in that order. Do not assume the second pad is automatically Player 2.
The steps below target the current Local Couch Co-op mod (formerly HUNK’y Friend) and its REFramework-based setup. Menu labels and supported devices can change, so compare your installation with the mod page’s latest notes. The troubleshooting guidance cited here was current on October 13, 2026.
As an Amazon Associate I earn from qualifying purchases.
Start by separating setup faults from mod limits
Before changing files, identify exactly what is failing. “No controllers were found,” a wrong button, a dead stick, a crash at launch and a missing Player 2 are different problems with different fixes.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems- Only the wrong person moves: the physical devices are detected, but the player-to-device assignment is wrong.
- A pad appears but buttons do nothing: Player 2’s mapper is incomplete or the controls were mapped to a different device.
- The controller is absent from the co-op menu: the game or mod does not see that input type; a helper plug-in may be needed.
- The game crashes or reports a runtime error: check REFramework installation and version compatibility before remapping anything.
- Player 2 vanishes after joining: inspect the removal log and the circumstances of the disappearance.
- A switch or interaction cannot be used by Player 2: this can be an intentional design limitation rather than a controller fault.
Disconnect extra pads while diagnosing. Leave only the keyboard/mouse you use for Player 1 and the intended second controller connected, then relaunch the game so the mod gets a clean device list.
#1 Best Overall
- With broad game support, the Logitech Gamepad F310 works with old standbys to today's biggest titles, so it's easy to set up and use with your favorite games.
- Profiler software allows the gamepad to be programmed to perform keyboard and mouse commands for games without gamepad support.* * Requires software installation.
- A familiar control layout that doesn't require a learning curve to be able to use, with all the same buttons as on an Xbox 360.
- The unique floating D-pad rests on four switches-instead of a single pivot point-making it responsive to quick changes in direction.
- The six-foot cord lets you lean back and play a comfortable distance from your PC monitor.
1. Assign each controller explicitly in the co-op menu
Open the Local Couch Co-op menu, choose Controls, and select the controller assigned to each player by its device name. Player 1 may use either a controller or keyboard and mouse. Player 2 must be assigned a detected controller.
- Start the game with the co-op mod loaded.
- Open the mod’s co-op menu and enter Controls.
- Open the Player 1 device selector and choose the exact device name for the first player.
- Open the Player 2 selector and choose the exact name of the second pad.
- Move a stick or press a face button on each physical device to confirm that the highlighted device responds to the pad in your hands.
- Save or leave the menu using the mod’s normal confirmation control, then test movement before entering a long session.
Controller order in Windows, Steam or the game is not a reliable player order. A pad listed first can become Player 2, especially after reconnecting USB devices or waking a wireless controller. Device-name assignment removes that ambiguity. If both pads have indistinguishable names, unplug one, identify the remaining entry, reconnect the other and assign them one at a time.
2. Map Player 2’s inputs manually and test every control
Player 2 has a separate button mapper. In Controls, select a Player 2 action, then press the physical button or move the stick you want to use for that action. You can map controls one at a time or proceed through the mapper in sequence.
Recommended Free Tools
- Select the Player 2 action you want to configure, such as movement, camera, interact or attack.
- Press the desired physical button, trigger or stick direction on the controller assigned to Player 2.
- Watch for the interface to display the newly mapped control. That visual change is the immediate confirmation that the mod received the input.
- Continue through every required action, including both stick-clicks if the mode uses them.
- Leave the mapper and test movement, camera, aiming, attack, interact and menu navigation in a safe area.
- Return to the mapper and correct any action that triggers the wrong command.
The mod author warns that automatic mapping can be glitchy. If auto-map produces swapped buttons, duplicate assignments or missing axes, discard that result and map the controls manually. Do not try to repair a bad automatic layout by guessing which device is active; first verify the Player 2 device selection, then remap.
Symptoms of an incorrect map
- Every button is shifted: the pad may have been mapped using a different layout, or the wrong controller was selected.
- One trigger or stick is dead: remap that axis manually and check whether the mapper visibly registers movement.
- Buttons work in menus but not gameplay: the action may be unassigned in the gameplay profile, or the mode may reserve that interaction for Player 1.
- Both players react to one pad: the same device was assigned to both players; return to the device selectors and choose distinct names.
3. When the controller is not listed
The co-op page documents detected input slots for DualSense, DualShock 4, Switch Pro and generic pads. Detection in this list is the important test; a controller that works in another PC game is not automatically visible to this mod.
Check the device category first
Look at the name shown in the mod’s controller selector. If the pad is listed under a generic or unexpected name, select it and test the mapper instead of assuming it is unsupported. Reconnect the controller before launching the game, and avoid changing connection mode while the co-op menu is open.
Rank #2
- Wide Compatibility: VOYEE wired 360 controller compatible with Microsoft Xbox 360 & Slim/ PC (Windows 11/10/8.1/8/7). Just plug and play, not for FPS games
- Enhanced Game Controller: Upgraded PC 360 controller with new left and right trigger buttons and more sensitive joysticks and buttons - Respond quickly to player commands without delay
- Astonishing Gaming Experience: VOYEE wired pc controller provides rumble control and according to the game automatic vibration feedback to enhanced game experience and match your personal preference
- Ergonomic Design: Grips's contours have been designed to fit your hands more comfortably to hold for a long time and 7.2ft cord allows greater
- What You Get: VOYEE wired 360/PC Controller, 45 Days Money Back, 365 Days Guarantee Against quality defect and 24 Hours Friendly Customer Support
Use the optional helper for game-invisible pads
Some PS3 controllers, generic USB or DirectInput pads and arcade sticks that the game itself cannot see can be enabled for Player 2 with the optional re2coop_pads.dll plug-in. This helper is specifically useful when the mod has no Player 2 entry for a device that is otherwise functional in Windows.
- Close the game and confirm that your device belongs to one of the categories described by the mod page.
- Install
re2coop_pads.dllaccording to the current Local Couch Co-op instructions. - Launch the game and inspect the Player 2 device list again.
- Assign the newly exposed device by name, then map its controls manually.
The helper does not guarantee compatibility with every third-party controller. If the device still does not appear, test a controller type that the mod documents as detected before concluding that the co-op setup is broken. A new controller cannot fix a framework-version mismatch or a wrong player assignment.
4. Fix crashes, startup failures and “Runtime Error” messages
If the game crashes when the mod loads, or the co-op menu never appears, verify the foundation before touching input mappings. The mod author states:
“If it’s a “Runtime Error” it is more then likely an issue of being the wrong Reframework version.”
Use the REFramework build required by the current co-op mod page. Framework builds change, and an older guide can point to a version that no longer matches the mod.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Verify the non-VR REFramework installation
For the standard non-VR game, the REFramework README instructs users to extract only dinput8.dll into the game folder. Do not scatter framework files through unrelated directories or place the DLL in a general Windows system folder. If you previously installed several builds, remove the obsolete copy before installing the required one so the game cannot load the wrong DLL.
Rank #3
- ✅【Compatibility】Compatible with Raspberry Pi, Windows PC, Linux ,Mac. Specifically designed for playing classic old school retro snes games on computer or laptop.This is the USB controller what has a USB plug for PC, NOT compatible for Original SNES super Nintendo console
- ✅ 【Ergonomic Design】Super precise cross key and function buttons,the cross direction key adopts frosted concave design,anti-sweat and anti-slip.The shape of the controller is designed to fit the contour of your hands,easy and comfortable to hold.
- ✅ 【Advanced Game Experience】PC running operating system:Windows 98/2000/ ME/XP/Vista/Win7/8/8.1/11 or later,or Mac running OS X 10.0/Mac OS X or above.It works with most of emulators you wish to download and use,such as VirtuaNES(PC),sens9x,Zsens,sensgt,Uosnesw,RetroArch,OpenEmu(MAC),NESEmu and Jnes etc.
- ✅ 【Wired USB Connection】Standard USB 2.0 port with a 1.5 meters (5ft) cable, don't need to install any drivers, you must manually set the buttons and directionals within the emulator you're using, and the controller not automatically assigns buttons/directional axes. Notice: please download the game emulator first before start the games, you can download the emulator “VirtuaNES” on PC and “OpenEmu”on MAC.
- ✅【Satisfaction】Third party controller(USB Version), not for original snes console and not support for switch. If there is an incompatibility on MAC or Raspberry Pi , please contact the seller for a support.
- Exit the game and any launcher that may keep its process open.
- Check the co-op mod page for the currently required REFramework version.
- Download the matching stable or nightly build specified for your setup.
- For non-VR play, place the required
dinput8.dllin the Resident Evil 2 Remake game directory as described in the REFramework README. - Launch the game without changing controller connections and confirm that REFramework initializes.
- Load the co-op mod and test the Controls menu before starting a campaign session.
REFramework’s README documents DirectX 11 and DirectX 12 support and includes a Proton/Linux launch option. Follow the instructions for the renderer and operating environment you actually use; a Windows DLL placement procedure is not a substitute for the Linux/Proton instructions. The README is framework documentation, not a promise that every mod release supports every build, so the co-op mod’s stated requirement takes precedence.
If updating the framework does not help
- Confirm that only one REFramework installation is active in the game directory.
- Temporarily remove unrelated REFramework mods and launch with only the framework and co-op mod.
- Check whether the crash occurs before the co-op menu appears; that points to framework or mod loading rather than a button map.
- Restore the last known working framework/mod pair instead of mixing a new framework with an old co-op release.
5. Recover when Player 2 disappears
When Player 2 vanishes after joining, the Local Couch Co-op mod records removal reasons in reframework/data/re2coop_p2_log.txt. Open that file after reproducing the problem and include it in a support report. The log is more useful than a description such as “the second player disappeared,” because it records why the mod removed the player.
- Reproduce the disappearance once, noting whether it follows a disconnect, a scene change, a menu action or a specific interaction.
- Exit to desktop without deleting the log.
- Open
reframework/data/re2coop_p2_log.txt. - Copy the relevant entries and report them with your game version, REFramework version, co-op mod version, controller types and play mode.
Close in-game menus before spawning or removing Player 2. Menu transitions can interfere with those operations. Also test the controller cable, wireless connection or USB port separately: a genuine disconnect can look like a mod removal.
The mod has a history of fixes for controller disconnect/reconnect behavior and player-removal issues. That history is why an old forum post may describe a failure that the current release already fixes, or prescribe a workaround that now causes a new problem. Use the live mod page’s current notes when deciding whether an issue is already addressed.
6. Recognize limitations that look like input failures
Player 1-only switches and interactions
Most switches and other interactions remain Player 1-only. If Player 2 can move, aim and attack but cannot operate a particular switch, that is normally a design limit rather than a dead button. Move Player 1 to the interaction and let Player 2 continue with combat or positioning.
Bring a separated Player 2 back
Use L3 + R3 to bring a left-behind Player 2 next to Player 1. This is a gameplay command, not a remapping cure: it helps when the second character is too far away, but it will not restore a controller that is disconnected or unassigned.
Rank #4
- 【Supported Operating System】The Game Controller is specifically designed for playing classic old school retro snes games on computer or laptop. Compatible with Windows 98 / ME / Vista / 2000/2003 / XP / 7 / 8 / 8.1 / 10/11, Mac OS X/ OS X 10.0 and beyond, Raspberry Pi, Raspberry PI 2 model B,Model A, Raspberry Pi 1 Model B+, Raspberry Pi 2,Raspberry Pi OS, Raspberry Pi 3 Model B+, Raspberry Pi 3, Raspberry Pi Zero.
- 【Simple USB Plug and Play】If your program or application accepts USB controller input, this classic game controller do not need install drivers or patches. 1.5 meter external cable(approx. 5 ft. Long). Notice: Please download the game emulator first before start the games, and then you must manually set the buttons and directionals within the emulator you're using, and the controller not automatically assigns buttons/directional axes. If on the Steam platform, you need to first enable Steam's "Universal Controller Configuration Support" and then restart Steam. After entering the game, you also need to manually bind key positions in the game
- 【High Sensitivity without Delay】Super sensitive buttons for precision control: 6 fire buttons, a 'Start' button and a 'Select' button, motion control cross. Play your favorite old school games with classic retro feel. Fits perfectly in the hand and also perfect for two player action.Note: Not applicable to Switch/PS games. Not Compatible with TV/ TV Box, third Mini Games Box and Tesla Model 3
- 【Supported Game Emulators】The game controller works with most emulators. Download any emulator you wish to download and use from Google and do the same with ROMS. Notice:Third party controller, not original controller. But it works phenomenal with the Raspberry Pi game emulation and so on
- 【Product Service】If you have any problem during use, send message to us and we will help you to solve the problem soon
Camera behavior
The camera follows Player 1 unless you select Split Screen or Fixed Camera. Player 2 may therefore appear to have a camera or aiming problem when the selected mode intentionally centers the view on Player 1. Test camera controls in the mode you intend to play before changing the button map.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
7. Choose the mode that matches the symptom
The co-op mod offers several play modes with different camera and input behavior. Use the table to identify whether you are troubleshooting a controller assignment or an expected mode characteristic.
| Mode | Camera context | Player 2 input/aiming | Second controller assignment | Extra requirement or caution |
|---|---|---|---|---|
| Shared Screen | One shared view | Player 2 uses the mapped controls within the shared camera | Required | Player 1 remains the camera reference |
| Fixed Camera | Fixed-camera presentation | Player 2 controls depend on the selected map | Required | Camera behavior can make movement feel different from free-camera play |
| Split Screen | Separate view areas | Independent aiming is available within the mode | Required | Experimental; the game is drawn twice, so a lower frame rate is expected |
| AI Companion | Camera follows the active play setup | Player 2 behavior is companion-oriented rather than a normal second human input profile | Not necessarily used as a standard second-controller mode | Check the mode’s own controls before diagnosing a pad |
| HUNK-y Friend Classic | Classic mode presentation | Use the mode-specific control behavior | Check the mode’s device assignment | Requires the Resident Evil 2 Remake Classic mod |
Switch to a simple shared-screen setup while diagnosing. Once both devices map correctly, return to Split Screen, Fixed Camera or another mode and test its camera assumptions separately. Split Screen’s performance cost is a rendering consequence, not evidence that a controller is malfunctioning.
8. A complete clean-room troubleshooting order
Use this sequence when several symptoms appear at once. It prevents a mapping change from hiding a framework problem.
- Record the environment: note the Resident Evil 2 Remake edition, renderer (DirectX 11, DirectX 12 or Proton), co-op mod version and REFramework version.
- Reduce hardware: connect only the intended Player 2 controller and the Player 1 input device.
- Confirm framework loading: verify the required REFramework build and the correct
dinput8.dllplacement for non-VR Windows play. - Open Controls: assign Player 1 and Player 2 by device name rather than list position.
- Map manually: avoid auto-map until every Player 2 action has been tested.
- Test a documented mode: use Shared Screen first, then test the mode you actually want.
- Check limitations: try a Player 1-only switch and camera behavior only after basic movement and combat work.
- Reproduce disconnects deliberately: if Player 2 disappears, inspect
reframework/data/re2coop_p2_log.txtand save the entries. - Add optional support last: install
re2coop_pads.dllonly when the device is one the helper is intended to expose and the standard device list cannot see it.
9. What to include in a useful support report
A report that includes only “controller not working” leaves out the information needed to distinguish input, framework and design issues. Include:
- The exact device names shown in the co-op Controls menu.
- Which device is assigned to Player 1 and Player 2.
- Whether Player 1 uses keyboard/mouse or a controller.
- The controller type: DualSense, DualShock 4, Switch Pro, generic pad, PS3 pad, DirectInput pad or arcade stick.
- The renderer and operating environment, including Proton/Linux when applicable.
- The Local Couch Co-op version and the REFramework version.
- The selected play mode.
- The first action that fails and whether the mapper displays the input when you press it.
- The contents of
reframework/data/re2coop_p2_log.txtwhen Player 2 disappears. - Whether the issue survives a clean launch with unrelated REFramework mods removed.
Do not attach a log containing unrelated personal files. Include the relevant lines and enough version information for the maintainer to reproduce the same software combination.
Best Value
- COMPATIBILITY: Support PC Computer, Laptop, Notebook. Windows XP/7/8/10/11, Steam, PS 3
- COMPATIBILITY FOR ANDROID: Support Android Mobile Phone/Tablet/TV/Box(system version 4.0 or above, and the device must fully support OTG function). Need to purchase a OTG adapter or cable for the Android device with Type-C or Micro-USB port.
- PLUG AND PLAY: Only for PC games supporting Xinput mode / Android mobile games supporting Android mode / PS 3. No need to install drivers except for Windows XP.
- PRODUCT FEATURE: Multi-mode: Xinput & Dinput & Android & PS 3 / Vibration Feedback Function / JD-SWTICH Function / TURBO Function
- NOTICE: This USB Wired PC Controller Gamepad does not support the Xbox 360 / Xbox One / Mac OS / PS4
10. Quick decision tree
The pad is not listed
Check whether it is one of the documented detected types. If it is a PS3, generic USB/DirectInput pad or arcade stick invisible to the game, try the optional re2coop_pads.dll helper. If it remains absent, the device may not be supported.
The pad is listed but the wrong player moves
Return to Controls and assign devices by their names. Do not rely on controller order. Then remap Player 2 manually.
The mapper does not show a button press
Verify that the correct device is selected, reconnect it before launching and test a different USB port or connection mode. If the device is game-invisible, use the helper only when it matches the documented categories.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated 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 matchThe game crashes before the menu opens
Check the current REFramework requirement, remove duplicate or stale framework files, and follow the correct DirectX or Proton installation path. A runtime error is more likely to be a version mismatch than a bad button map.
Player 2 disappears during play
Close menus before spawning or removing the player, reproduce the issue once, and inspect reframework/data/re2coop_p2_log.txt. Include that log with your version and device details when reporting the problem.
Only an interaction or camera behavior seems wrong
Test whether the action is Player 1-only or whether the selected mode follows Player 1’s camera. Use L3 + R3 to regroup a separated Player 2, and do not treat Split Screen’s expected frame-rate reduction as an input failure.
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.
