Getting controller input right in RE Engine games is one of those things that either works invisibly or ruins the experience. A bad mapping setup means missed inputs, menus skipping items, or VR controls that drift when you don’t touch them. This guide covers the setup that actually holds up across Resident Evil, Monster Hunter, and Street Fighter 6, whether you’re playing flatscreen or in VR.
Before setting any of this up, make sure REFramework itself is installed and running, since several of the checks below depend on the in-game menu being reachable.
Why controller mapping matters more with REFramework installed
RE Engine games already ship with reasonable controller support out of the box. The problem starts once REFramework enters the picture. The framework hooks directly into input handling so it can open its own menu, run Lua scripts that read controller state, and in some cases remap functions like free camera movement or time scale controls to specific buttons. If your controller setup is inconsistent underneath that layer, REFramework inherits the inconsistency. A stick that drifts slightly on your desktop will drift the same way in the REFramework free camera. A controller that gets recognized as two separate devices in Windows will confuse REFramework’s own input reading the same way it confuses the base game.
That is why the fixes below focus on cleaning up input at the Windows and driver level first, rather than trying to patch symptoms inside individual games.
The best mapping method: Xbox emulation
RE Engine games are built around XInput, the same input system Xbox controllers use natively. DirectInput, which is the older standard most PlayStation controllers use by default on PC, does not map cleanly onto the button and trigger layout these games expect. If you’re on a PlayStation controller like a DualSense or DualShock 4, the cleanest fix is emulating an Xbox controller rather than fighting with native PlayStation input.
DS4Windows handles this well for both DualShock 4 and DualSense controllers. Set the output profile to Xbox 360 controller rather than DirectInput or any of the other emulation modes. Once your controller is emulated this way, the game recognizes it through the default XInput path immediately. Every button, including triggers and the touchpad, maps correctly without manual remapping, and REFramework hooks into input without any conflicts, since as far as the operating system is concerned, you are now using an Xbox controller.
One detail worth knowing: DS4Windows has an older built-in option called Hide DS4 Controllers, sometimes referred to as exclusive mode, that asks Windows for exclusive access to your controller. It exists, but it is not the recommended fix anymore. Windows can deny that exclusive access request if another process already has a connection to the controller, and the setting tends to break the moment your controller disconnects and reconnects, like when a Bluetooth connection drops. The reliable fix for double input is covered in the next section.
Fixing double input
Double input shows up when the game sees two controllers at once: your physical pad and the virtual Xbox controller created by DS4Windows. The symptom is usually menus skipping entries, characters moving twice as fast as expected, or actions firing when you only pressed a button once.
If DS4Windows exclusive access does not solve it, or you’d rather skip that unreliable option entirely, the dependable fix is HidHide, a kernel level filter driver made for exactly this problem. Install it, add your physical controller to the device list inside the HidHide configuration client, enable the hide option for that device, and then whitelist DS4Windows so it remains the only application allowed to see the raw controller. Once that is set, the game only receives one clean signal, the emulated Xbox controller, and the duplication goes away entirely, without the reliability problems that come from asking Windows for exclusive access. This is worth setting up even if double input seems absent during a quick test, since the problem often only shows up in specific menus or during specific actions, and can be easy to miss.
VR controller mapping
VR mods add a layer of complexity because standard button inputs get converted into 6-degree-of-freedom motion controls, and the physical buttons on a VR controller do not map one to one onto a traditional gamepad layout.
Most VR mods built on REFramework use a shift button system to work around this. Left Trigger is a common choice as a modifier key, so holding it changes what the other buttons do, similar to how a shift key on a keyboard changes what a letter key types. A common example is holding Left Trigger to open a weapon wheel instead of firing, using the same trigger that would otherwise pull the weapon’s actual trigger.
If you’re on a Valve Index or HTC Vive controller, dead zone tuning matters more than it does on a standard gamepad, since VR controllers report analog stick and touchpad position with more sensitivity to small unintentional movements. Check the thumbstick or touchpad dead zones inside the REFramework menu, opened with the Insert key. The full range of menu options available there, including camera and VR specific settings, is covered in the documentation if you want a complete picture of what is adjustable. Loose dead zones are the most common cause of unwanted drift or camera creep in VR sessions.
If you’re already running DS4Windows for a traditional controller alongside your VR setup, disable Steam Input for that specific game in its Steam properties. Running Steam Input and DS4Windows at the same time is a frequent source of conflicting inputs, since both are trying to translate the same physical device. Steam Input is really only worth enabling if you’re using something DS4Windows does not cover well, such as a Nintendo Switch Pro Controller, and you don’t have any other mapping software running for that device.
Button layout tweaks worth trying
A few remapping choices consistently make REFramework and RE Engine games easier to play once your base input is stable.
- Touchpad Press mapped to the REFramework menu shortcut, so you can reach mod settings, Object Explorer, or VR options without needing a keyboard nearby.
- L3 plus R3 mapped together to toggle first-person and third-person view, which is particularly useful in Resident Evil 2 and Resident Evil 3 where both perspectives are supported by community mods.
- Right Trigger set to Hair Trigger mode under DS4Windows’ Two-Stage Trigger settings, which makes the full-pull action fire the moment the trigger reaches maximum value instead of waiting for the soft-pull action to release first. In practice this makes shooting feel faster and more responsive during fast combat.
None of these require editing Lua scripts or touching REFramework’s own configuration files. They are all handled at the DS4Windows profile level, which keeps your setup portable if you switch games or reinstall REFramework later.
Common problems and quick fixes
REFramework menu is stealing input. If the overlay is open, it captures controller input before the underlying game sees it. This is expected behavior, not a bug, since the menu needs to read your inputs to let you navigate it. Close it with Insert before testing gameplay to confirm whether an input issue is actually coming from the game or just from the menu still being open.
Wrong controller assigned as Player 1. Windows sometimes hands Player 1 to the wrong device, including things like a numpad or an unrelated HID device that happens to register itself as a controller. Check DS4Windows and confirm your actual controller is set as Controller 1 in its device list, and disconnect anything else that might be competing for that slot.
Steam controller settings conflicting. Go to Steam, Settings, Controller, and make sure the correct controller support option is enabled for the platform you’re actually using. Leaving both PlayStation Configuration Support and Xbox Configuration Support enabled at the same time, while also running DS4Windows, is a common way to end up with the exact double input problem covered earlier.
If none of these fixes resolve your setup, the troubleshooting guide covers a wider set of REFramework issues, including crashes and menu access problems, that might be the actual underlying cause rather than the controller itself.
Conclusion
A good controller setup for REFramework is one you stop thinking about once it’s done. DS4Windows with Xbox 360 emulation, paired with HidHide to eliminate duplicate signals, is the combination that holds up consistently across every RE Engine title, whether you’re playing on a flat screen or in VR. Get that foundation right first, tune dead zones and trigger sensitivity to your own preference second, and REFramework will run the way it’s supposed to, with your mods behaving exactly as intended rather than fighting against input problems underneath them.