The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →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
Most second-controller failures in Resident Evil 2 Remake co-op mods come from three places: the mod has the wrong device assigned to Player 2, the button map is incorrect, or REFramework and the mod are not on compatible versions. Start by assigning each device by its displayed name, map Player 2 manually and test every input, then verify the framework installation. If Player 2 vanishes, inspect the removal log before changing controls. Some apparent input failures are intentional limits: most switches and other interactions remain Player 1-only.
What you need before changing controls
This guide applies to the PC version of Resident Evil 2 Remake running the Local Couch Co-op mod, formerly called HUNK’y Friend. The mod depends on REFramework, so both the game-mod build and the framework build matter. The Local Couch Co-op documentation is updated over time; use its current requirement and notes rather than an old installation guide.
- A working game installation that can launch normally without the co-op mod.
- The current REFramework build required by the mod. REFramework documentation distinguishes stable and nightly builds, and its installation method depends on the game environment.
- The current Local Couch Co-op files, installed exactly as their page specifies.
- Two input devices if both players are using controllers. Player 1 may use keyboard and mouse instead.
- Permission to write to the game directory, because REFramework creates a
reframeworkfolder and the mod writes diagnostic files there.
Disconnect unnecessary gamepads, fight sticks and virtual controllers while diagnosing. Multiple devices can make it difficult to tell which name the mod is assigning, although the final assignment must still be made in the mod menu rather than inferred from connection order.
Assign the correct device to each player
Open the co-op control assignment
- Launch the game with the mod enabled.
- Open the Local Couch Co-op menu.
- Choose Controls.
- For Player 1 and Player 2, select the controller by the device name shown in the menu. Do not assume that the first controller detected is Player 1 or that the second one is Player 2.
Player 1 can be assigned a controller or remain on keyboard and mouse. Player 2 needs an explicitly selected input device; an unassigned or incorrectly assigned slot can look like dead buttons even when Windows or the game can see the controller.
#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.
Map Player 2 manually and test as you go
Use Player 2’s button mapper rather than relying on a remembered layout from another game. Select a control in the mapper, press the physical button or move the stick you want to use, and continue through the controls in sequence. The interface indicates controls as they are mapped, giving you an immediate way to verify that the press was received.
The mod author warns that automatic mapping can be glitchy. If auto-map produces swapped triggers, missing sticks or unusable face buttons, clear or replace those entries with manual mapping. Test the result in a safe area before starting a difficult encounter: move in each direction, rotate the camera, aim, fire, interact where Player 2 is allowed to interact, open the inventory if that mode supports it, and confirm every shoulder, trigger and stick-click input.
- If one physical button appears under two actions, remap the duplicate entries manually.
- If a stick moves in the wrong direction, map the individual axes again instead of accepting the automatic result.
- If a control does nothing in gameplay but registers in the mapper, check whether that action is Player 1-only; mapping cannot remove a game-design restriction.
When the controller is not listed
Identify the device class first
The mod documents detected input slots for DualSense, DualShock 4, Switch Pro and generic gamepads. A controller can be connected to the operating system yet absent from the mod if the game itself does not expose that device type.
Some PS3 controllers, generic USB or DirectInput pads, and arcade sticks that the game cannot see can be enabled for Player 2 with the optional re2coop_pads.dll helper plug-in. This helper is specifically a Player 2 path; it is not a promise that every third-party controller will work, and it does not correct a bad REFramework installation.
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
Check the practical connection path
- Close the game and connect only the controller you are testing.
- Reconnect it directly to the PC rather than through an unpowered hub, then start the game again.
- Return to Controls and look for the device’s exact displayed name.
- If it is a PS3, DirectInput or arcade device that the game normally ignores, install and enable
re2coop_pads.dllaccording to the mod’s current files and location instructions. - Restart the game, assign the newly exposed device to Player 2, and run the manual mapping test.
Buying a different USB controller is only a hardware option after checking the supported-device path and mapping behavior. A new pad will not fix a controller assigned to the wrong player, an incompatible framework version or an interaction that is intentionally restricted to Player 1.
Fix crashes, startup failures and runtime errors
Recheck the REFramework version
If the game crashes at launch or the mod reports a runtime error, the Local Couch Co-op troubleshooting note says that a wrong REFramework version is the more likely cause. Do not assume that a build that worked with an older mod release is still valid. Compare the framework requirement on the mod’s live page with the installed build, and replace the framework with the required current version when they differ.
REFramework’s project README documents both stable and nightly builds. Use the build the mod currently requires rather than mixing files from several versions. Remove obsolete framework files before reinstalling if an update left duplicate or conflicting files.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Install the non-VR framework files in the right place
For a normal non-VR installation, the REFramework README says to extract only dinput8.dll into the game folder. That means the directory containing the game’s executable, not a random download folder, the mod archive, or a subfolder inside reframework. The framework then creates or uses its own data directories when the game starts.
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.
Use the README’s separate instructions for the environment you actually run. It lists DirectX 11 and DirectX 12 support and includes a launch option for Proton/Linux. A Windows procedure copied into a Proton installation, or a DirectX assumption that does not match the game launch path, can produce a failure that looks like a controller problem.
Use a clean isolation test
- Launch the unmodified game. If it already crashes, repair the base game before troubleshooting co-op input.
- Launch with REFramework but without the co-op files. If the framework itself fails, resolve that installation first.
- Add the Local Couch Co-op files and test with one known-supported controller.
- Only after that works, add the optional pad helper or additional devices.
This order prevents a helper plug-in, an old mod file and a framework mismatch from being treated as one unexplained “controller” fault.
Use the symptom to choose the next check
| Symptom | First check | Most useful evidence |
|---|---|---|
| Player 2 moves, but buttons are wrong | Open Player 2’s mapper and replace automatic entries manually. | The mapper’s confirmation for each physical press. |
| The intended pad is absent from Controls | Identify whether it is a PS3, DirectInput, generic USB pad or arcade stick. | The device name shown after reconnecting, with the optional helper enabled when applicable. |
| The game crashes or shows a runtime error | Compare the installed REFramework build with the mod’s current requirement. | The exact framework and mod versions, plus the game environment. |
| Player 2 disappears during play | Inspect the Player 2 removal log and avoid spawning or removing players while an in-game menu is open. | reframework/data/re2coop_p2_log.txt. |
| A switch or environmental interaction does nothing | Determine whether the interaction is Player 1-only by design. | Whether Player 1 can perform it in the same scene. |
| The picture slows after enabling split screen | Return to Shared Screen, Fixed Camera or another mode to compare. | Whether the slowdown appears only in Split Screen. |
Recover when Player 2 disappears
Read the removal log
The mod records reasons for Player 2 being removed in reframework/data/re2coop_p2_log.txt. Check this file immediately after the disappearance, before relaunching repeatedly or deleting configuration files. Include the complete log in a bug report so the maintainer can see the removal event rather than receiving only a description such as “the controller stopped.”
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsAvoid menu-state conflicts
The mod documentation specifically warns against spawning or removing Player 2 while an in-game menu is open. Close inventory, map, pause and other in-game overlays before creating or removing the second player. Then retry the operation in active gameplay.
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
Account for connection history
The project has received fixes for controller disconnect and reconnect behavior and for player-removal issues. That history is a reason to follow the current mod notes instead of applying an old workaround unchanged. If a cable or wireless connection drops, restore the device first, close any open game menu, and then check whether the current build restores Player 2 or records a removal event.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Separate input faults from mode limitations
Not every missing action indicates a failed map. The co-op mod changes how two characters are controlled, but the underlying game still assigns many interactions to Player 1. Most switches and other environmental interactions remain Player 1-only. If Player 2 can move, aim and use mapped combat controls while a switch does nothing, have Player 1 perform the interaction before changing the mapping.
When Player 2 is left behind, use L3 + R3 to bring that character next to Player 1. This is a repositioning function, not evidence that the second controller has disconnected.
The camera normally follows Player 1. A second player therefore may appear to be unresponsive when the character is simply outside the current view. Use Fixed Camera or Split Screen when the selected mode supports it and independent visibility is important.
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
Compare the available play modes before diagnosing camera or aiming
| Mode | Camera context | Player 2 aiming and input | Requirement or caveat |
|---|---|---|---|
| Shared Screen | Both characters use one shared view that follows the active scene’s camera behavior. | Player 2 receives a separate assigned controller and mapped controls, but can leave the camera’s visible area. | Use L3 + R3 to regroup a left-behind Player 2. |
| Fixed Camera | The view uses fixed-camera behavior rather than following every movement freely. | Player 2 retains the assigned device and mapped input within that view. | A camera that does not track the second character is expected in this mode. |
| Split Screen | Each player receives a portion of the display. | Player 2 can aim independently because the screen is divided between players. | Experimental; the mod author says the game is drawn twice, so a lower frame rate is expected. |
| AI Companion | Camera behavior follows the mode’s companion design rather than two fully human viewpoints. | It is not the same test as assigning a second physical controller for independent co-op input. | Use a human-controlled mode when diagnosing a missing Player 2 device. |
| HUNK-y Friend Classic | Uses the classic mode’s camera and co-op behavior. | Check its control assignment separately from newer modes. | Requires the Resident Evil 2 Remake Classic mod. |
Use mode comparison as a diagnostic: if Player 2 works in Shared Screen but the view appears wrong in Split Screen, the symptom is likely camera or performance behavior rather than a dead input. If the controller is absent in every mode, return to device detection, helper-plug-in and framework checks.
A repeatable end-to-end test
- Start with one known-supported controller and keyboard-and-mouse Player 1.
- Open Controls and assign the device by its displayed name to Player 2.
- Map Player 2 manually, pressing each physical control once and confirming the on-screen indication.
- Test movement, camera, aim, attack, shoulder buttons, triggers and stick clicks in a safe area.
- Test an interaction that should be available to Player 2, then test a switch to confirm whether the latter is a Player 1-only limitation.
- Walk far enough to check camera behavior, then use L3 + R3 to regroup.
- Close all in-game menus before spawning or removing Player 2.
- Disconnect and reconnect the controller only after saving a copy of the current configuration and, if Player 2 vanishes, the removal log.
- Change one variable at a time: device, map, helper plug-in, framework build or play mode. A simultaneous reinstall of everything hides the cause.
What to include in a useful problem report
A maintainer can diagnose a missing player more quickly when the report preserves the conditions that produced it. Include:
- The game edition and launch environment, including DirectX 11, DirectX 12 or Proton/Linux where relevant.
- The exact REFramework build and the Local Couch Co-op version required by the current mod page.
- Each controller’s displayed device name and whether Player 1 used keyboard and mouse.
- Whether controls were auto-mapped or entered manually, and which physical input failed.
- The selected mode: Shared Screen, Fixed Camera, Split Screen, AI Companion or HUNK-y Friend Classic.
- Whether
re2coop_pads.dllwas enabled. - The contents of
reframework/data/re2coop_p2_log.txtwhen Player 2 disappeared. - The precise point of failure: startup, assignment, mapping, reconnect, spawning, removal, camera tracking or an interaction.
Do not report “controller not working” when the mapper registers the button but the scene’s switch is Player 1-only; those are different defects and require different fixes.
Quick Recap
Decision checklist
- Wrong actions: select the correct named device and manually remap Player 2.
- Missing device: identify the controller class; use the optional pad helper only for devices the game cannot expose itself.
- Runtime error: verify the framework version and the correct
dinput8.dllinstallation for the game environment. - Player 2 removed: close menus, retry in active gameplay and preserve the removal log.
- No switch or environmental response: test with Player 1 because most such interactions are intentionally Player 1-only.
- Camera or slowdown complaint: compare the selected mode, remembering that Split Screen is experimental and renders the game twice.
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.
