Most Resident Evil 2 Remake co-op input failures come from assigning the wrong device, mapping Player 2 with unreliable auto-map, using a controller the game cannot detect, or running an incompatible REFramework build. Open the Local Couch Co-op menu, assign each player by the controller’s device name, manually map and test Player 2’s controls, then check the framework and the Player 2 removal log if the problem persists. Some apparent button failures are intentional limits: most switches and other interactions remain Player 1-only.
What this guide covers
This guide is for the PC version of Resident Evil 2 Remake using the Local Couch Co-op mod, formerly called HUNK’y Friend. The mod’s installation instructions, supported devices and required REFramework version can change, so compare your files with the current mod page before changing anything. The procedure below separates four different causes that often look identical in-game:
As an Amazon Associate I earn from qualifying purchases.
- Assignment problems: the controller is connected but assigned to the wrong player.
- Mapping problems: Player 2 has a device, but buttons or sticks are bound incorrectly.
- Detection and framework problems: the game or REFramework cannot expose the device to the mod.
- Design limits: an interaction, camera behavior or input action is restricted by the selected co-op mode.
Do the checks in that order. Buying another controller will not correct a wrong assignment or a framework mismatch.
Fastest fix: assign and map Player 2 explicitly
- Launch the game with the co-op mod and open its co-op menu.
- Open Controls.
- Select the controller assigned to Player 1 and the controller assigned to Player 2 by the device names shown in the menu. Do not rely on the order in which Windows, Steam or the game happened to enumerate them.
- Remember that Player 1 may use keyboard and mouse. Player 2 must use a controller that appears in the mod’s available input slots, or a supported helper plug-in for devices the game does not normally expose.
- For Player 2, open the button mapper, select one control and press the physical button or move the stick you want to use for it.
- Continue through the controls in sequence if you prefer. The interface indicates a control when the corresponding input is pressed, which lets you verify each binding immediately.
- Save or leave the mapper only after testing every important button, both sticks, triggers and the menu controls in a safe game area.
The mod author specifically warns that auto-map can be glitchy. If a trigger becomes a shoulder button, a stick is inverted or several actions share one input, clear the affected entries and map them manually rather than repeatedly running auto-map.
#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.
How to diagnose a controller that is missing from the list
Recognize the device categories the mod documents
The Local Couch Co-op documentation lists DualSense, DualShock 4, Switch Pro and generic pads as detected input slots. A generic pad is not guaranteed to use the same button labels as an Xbox-style layout, so the mapper’s live input indication is more reliable than the printed symbol on the controller.
When the game itself cannot see the device
Some PS3 controllers, generic USB or DirectInput pads and arcade sticks may be invisible to the game even though the operating system reports that they are connected. The optional re2coop_pads.dll plug-in can expose some of those devices for Player 2. It is a compatibility aid, not a promise that every third-party controller will work, and it does not replace assigning the device in the Controls menu.
If you use the plug-in, install the exact file and location specified by the current Local Couch Co-op instructions, restart the game, and then return to Controls to assign the newly exposed device. If it still does not appear, treat the controller as unsupported or game-invisible rather than trying to fix it with additional mappings.
Check the physical path before changing the mod
- Confirm that the controller is powered and connected before launching the game.
- Check whether the game recognizes the device at all; a pad that is absent from the game cannot be selected by the co-op menu.
- Disconnect duplicate or unused pads temporarily so you can identify the correct device name.
- After reconnecting a pad, reopen the Controls screen and assign it again. A reconnect can change the device entry even when the same physical controller is used.
Fixing wrong buttons, dead sticks and incorrect layouts
Map one control at a time
Select a single action in Player 2’s mapper, press the desired physical control, and watch for the on-screen confirmation. Repeat for movement, camera, aim, attack, interact, inventory and menu navigation. Mapping in a deliberate sequence makes it easy to identify the first wrong binding instead of debugging an entire profile.
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
Test both sticks and analog triggers
Move each stick through its full range while the mapper is focused on that action. A button press that works in the menu but not in gameplay can indicate that the action was assigned to the wrong control, not that the controller is dead. Test left and right triggers separately; generic and DirectInput devices can report them in an order different from the labels printed on the shell.
Use manual mapping after auto-map errors
Auto-map is convenient but is documented as potentially glitchy. Clear only the incorrect entries, then assign them manually and test them in a quiet room before starting a story sequence. Do not infer Player 2’s layout from Player 1’s device: each controller must be selected and mapped independently.
Framework and startup errors
Why a runtime error often points to REFramework
If the game crashes at startup, the mod fails to open its menu or displays a runtime error, verify the REFramework version required by the current Local Couch Co-op page. The mod’s troubleshooting note says, “If it’s a "Runtime Error" it is more then likely an issue of being the wrong Reframework version.” In practice, check the framework first rather than rebuilding every controller profile.
Install the correct non-VR framework file
The REFramework README’s non-VR instructions say to extract only dinput8.dll into the game folder. Use the build and installation directions appropriate to your game environment; do not copy unrelated files from another configuration. If you changed between framework builds, remove stale copies before installing the current required file so the game does not load an older DLL from the same directory.
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.
DirectX and Proton considerations
The framework documentation lists support for both DirectX 11 and DirectX 12 and includes a launch option for Proton/Linux. Select the instructions that match the renderer and operating environment you actually use. A setup that works under one renderer or under Windows is not evidence that the same DLL placement is correct for another environment.
Recheck versions after an update
REFramework has stable and nightly builds, and mod requirements can change. If a previously working co-op installation breaks after a game, framework or mod update, compare the current required version with the file you installed. Keep a copy of your working configuration, but do not assume an old guide’s version is still valid.
When Player 2 disappears
Read the removal log
The mod records reasons for Player 2 being removed in:
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 →reframework/data/re2coop_p2_log.txt
Open that file after reproducing the problem and include it in a bug report. The log is more useful than a description such as “the second player vanished,” because it can distinguish a deliberate removal, an input disconnect or another mod-side condition.
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
Close menus before spawning or removing a player
Close in-game menus before you spawn Player 2 or remove Player 2. Leaving a menu open during that operation can interfere with the mod’s input state and make a normal controller problem look like a player-removal failure.
Check reconnect behavior
The mod has a history of fixes for controller disconnect and reconnect behavior and for player-removal issues. Use the live mod page’s current notes rather than an old video or guide. After reconnecting a controller, return to Controls, confirm the device name is still assigned to Player 2, and test the mapper before resuming play.
Separate input faults from intentional co-op limits
Player 1-only interactions
Most switches and other interactions remain Player 1-only. If Player 2 can move, aim and attack but cannot operate a switch, pickup or similar object, that behavior may be a documented design limit rather than a dead button. Have Player 1 perform the interaction and continue testing Player 2 with actions the selected mode supports.
Bring a left-behind Player 2 to Player 1
Use L3 + R3 to bring a left-behind Player 2 next to Player 1. This is a positioning function, not a replacement for movement mapping: it helps when the second character is separated by the map or camera and appears to have stopped responding.
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
Camera behavior can look like an input failure
The camera follows Player 1 unless you select Split Screen or Fixed Camera. Player 2 may therefore move outside the visible area or appear unable to aim independently even though the controller is working. Confirm the camera mode before remapping the right stick.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Co-op modes and what they mean for controller troubleshooting
| Mode | Camera and input context | Second-controller assignment | Important qualification |
|---|---|---|---|
| Shared Screen | Players share the normal camera context; Player 1 remains the camera reference. | Assign a Player 2 device in Controls. | Independent-aiming behavior is not stated in the mod notes; test the exact action in your build. |
| Fixed Camera | The camera uses fixed-camera behavior rather than following free movement in the usual way. | Assign and map Player 2 normally. | Camera limits can be mistaken for a right-stick or aiming fault. |
| Split Screen | Each player receives a separate view, allowing independent spatial awareness. | Assign a second controller and map it before starting. | Experimental; the mod author says the game is drawn twice, so a lower frame rate is expected. No numerical performance figure is provided. |
| AI Companion | Player 2’s role is represented by an AI companion in this mode. | Whether a second controller is used depends on the mode’s current implementation; verify its in-game Controls entries. | Do not treat the absence of a controllable Player 2 as a failed controller assignment without checking the mode. |
| HUNK-y Friend Classic | Classic-style co-op behavior. | Use the mode’s own control assignment and mapping entries. | Requires the Resident Evil 2 Remake Classic mod; install and version requirements must match the current mod documentation. |
This table is for diagnosis, not a universal ranking. If a control works in Shared Screen but not in Split Screen, compare the mode’s documented behavior before replacing the controller.
Symptom-by-symptom troubleshooting
| Symptom | Likely cause | Action |
|---|---|---|
| Player 2 controls Player 1 | Devices were assigned by enumeration order or the wrong name. | Open Controls and select each player’s device explicitly by name, then remap Player 2. |
| Player 2 has movement but no attack or interact | Incomplete or incorrect mapper entries. | Map the missing actions manually and test each physical button; do not rerun unreliable auto-map blindly. |
| A controller is absent from Controls | The game cannot see the device, or it is outside the documented input slots. | Identify whether it is a DualSense, DualShock 4, Switch Pro, generic pad, PS3, DirectInput pad or arcade stick. For some game-invisible devices, try the optional re2coop_pads.dll helper for Player 2. |
| The right stick moves the wrong way | Auto-map or a generic-device axis order produced an incorrect binding. | Clear the right-stick entries, map each axis manually and test camera movement in the selected mode. |
| Runtime error or crash at launch | Wrong REFramework version or incorrect framework installation. | Recheck the mod’s current requirement and the REFramework installation; for non-VR, the README specifies extracting only dinput8.dll into the game folder. |
| Player 2 vanishes after joining or reconnecting | Disconnect/reconnect handling, a removal condition or an operation performed while a menu was open. | Close menus, reassign the reconnected device, reproduce the issue and inspect reframework/data/re2coop_p2_log.txt. |
| Player 2 cannot operate a switch | Documented Player 1-only interaction. | Have Player 1 perform the interaction; do not treat it as proof that the controller mapping failed. |
| Player 2 seems off-screen | Shared camera follows Player 1. | Use L3 + R3 to bring Player 2 beside Player 1, or evaluate Fixed Camera or experimental Split Screen behavior. |
A clean reset procedure
When several symptoms occur at once, reset in a controlled order instead of changing multiple files simultaneously:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Exit the game completely.
- Disconnect extra controllers and leave only the intended Player 1 and Player 2 devices connected.
- Confirm that the Local Couch Co-op files and the REFramework build match the current requirements.
- For a non-VR installation, verify that the correct
dinput8.dllis in the game folder and that no obsolete copy is being loaded from the same location. - Start the game and open the co-op Controls menu.
- Assign Player 1 and Player 2 by device name.
- Map Player 2 manually, beginning with movement and camera controls, then test attack, aim, interact and menus.
- Spawn Player 2 only after closing menus.
- If Player 2 disappears, reproduce the problem once and save the removal log before making further changes.
This sequence leaves a clear record of which change fixed the problem and avoids confusing a framework error with a mapper error.
What to include in a useful bug report
A report that contains only “no controllers were found” gives maintainers little to investigate. Include:
- The exact co-op mode in use.
- Which device name was selected for Player 1 and Player 2.
- The controller type: DualSense, DualShock 4, Switch Pro, generic, PS3, DirectInput or arcade stick.
- Whether the game itself detected the controller and whether
re2coop_pads.dllwas installed. - The REFramework build type and version, plus whether the game uses DirectX 11, DirectX 12 or Proton/Linux.
- The precise action that fails and whether it fails in the mapper, in gameplay or only in one camera mode.
- The contents of
reframework/data/re2coop_p2_log.txtwhen Player 2 disappears. - Whether the failure began after a disconnect, reconnect, game update, mod update or framework update.
Do not attach a controller purchase receipt as a substitute for these details. A replacement pad is useful only when the original hardware is faulty or incompatible; it cannot repair a bad assignment, unsupported device path or framework mismatch.
Practical prevention
- Assign controllers by their displayed names every time you change the connected devices.
- Keep a known-good manual Player 2 mapping instead of depending on auto-map.
- Record the framework and mod versions that work together before updating.
- Close menus before spawning or removing Player 2.
- Test controls in a safe area after reconnecting a controller.
- Remember the Player 1-only interaction rule and camera behavior before diagnosing a button as dead.
- Use the current Local Couch Co-op and REFramework documentation because both requirements and fixes can change.
Final diagnosis
Start with explicit device assignment, then manually map and test Player 2. If the device is missing, determine whether the game can see it and use the optional helper only for the categories it is intended to expose. If the mod fails at startup, verify REFramework and the non-VR dinput8.dll installation. If Player 2 disappears, close menus and read the removal log. Finally, check the selected mode’s limits: Player 1 handles most interactions, the camera normally follows Player 1, and Split Screen is experimental and more demanding because it renders the game twice.
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 errorsQuick 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.
