REFramework: A Mod Loader and VR Layer for Every RE Engine Game

One Hook for a Whole Engine Family

The project is written in C++, and it borrows code from Kanan, another RE Engine modding project. That lineage is visible in the low-level approach: the DLL hooks DirectX 11 and DirectX 12, which is why it can offer features like a free camera and FOV slider without touching each game's source. The README does not explain the internal hooking mechanism in detail, but the fact that it supports both DX11 and DX12 suggests a layered approach: one part intercepts the graphics API, another part interacts with the engine's object model. For the user, that means a single dinput8.dll file can do a lot of work.

Installation: One DLL, or the Whole Zip for VR

Linux users get a specific instruction: add the launch option WINEDLLOVERRIDES="dinput8.dll=n,b" to the game in Steam's properties. That tells Wine to load the native DLL instead of its own implementation. The README does not mention Proton explicitly, but the command is standard for Proton users. This is a concrete, actionable step, but it assumes you already know how to edit Steam launch options. For a tool aimed at modders, that is a reasonable assumption.

What You Get: Scripting, VR, and a Bag of Fixes

The included fixes are more interesting because they show the project's real-world priorities. There is a fix for Resident Evil Village startup crashes and stutters that occur when killing enemies or taking damage. There is also a fix for crashes in Monster Hunter Rise and RE8 that are caused by third-party DLLs. These are not generic engine fixes; they are targeted patches for specific bugs that Capcom has not addressed. That is the pragmatic value of a community mod loader: it can ship fixes faster than the official developer. But it also means the project's maintenance burden is tied to the whims of game updates. A single patch from Capcom could break all of these fixes at once.

Developer Tools and the Limits of the Documentation

The developer tools are a clear signal that the project is aimed at people who are comfortable with low-level debugging. The Object Explorer alone suggests that you can inspect the live game object hierarchy, which is essential for writing scripts that target specific entities. But without a tutorial or example scripts in the README, most users will bounce off. The README mentions that alphaZomega and The Hitchhiker helped stress test and create scripts, but it does not include any of those scripts. That is a missed opportunity to show what the Lua API can do.

The Wrong Tool for Some Games and Some Users

There is also the VR requirement. If you want VR, you need a compatible headset and SteamVR. The README points to a VR troubleshooting wiki, but it does not summarize common issues. That is a red flag for a feature that is often finicky. The motion controls only work for four games, so if you are a Resident Evil 4 VR enthusiast, you will be disappointed. The VR implementation is generic, which means it may not have the polish of a dedicated VR mod. For users who just want to play RE2 in first person, the non-VR features are more reliable.

Alternatives: Per-Game Mod Loaders and Official VR Ports

The main alternative to REFramework is a per-game mod loader like Fluffy Mod Manager or Vortex, which handle mod installation for specific titles. These tools do not provide scripting or VR support; they only manage files. That is a different approach: instead of hooking the engine, they replace game files. That is less risky in terms of compatibility, but it also means you cannot inject Lua scripts or modify camera behavior. Another alternative is official VR ports, such as the Resident Evil 4 VR mode on PSVR2, but those are platform-specific and not available for all games. The difference is fundamental: REFramework is an injection layer, while file-based loaders are passive. If a game update changes the file structure, a file-based loader can still work as long as the files are in the right place. If an update changes the engine's hook points, REFramework breaks. The trade-off is that REFramework offers features that file-based loaders cannot, like a free camera and timescale.

Maintenance, License, and Upgrade Costs

The upgrade cost is mostly about game compatibility. Each time a supported game receives a major update, you may need to wait for a new REFramework release. The project's rapid release history suggests that the maintainer is responsive, but there is no guarantee. The README does not list any known issues or limitations, which is a gap. You have to rely on the wiki and community reports. For a tool that hooks into the engine at such a low level, that is a risk you should be aware of.

Editorial conclusion

Adopt REFramework if you mod or play multiple RE Engine titles and want one tool for Lua scripts, VR, and common fixes like ultrawide or FOV. Do not adopt it if you need official support or if you are sensitive to the risk of game updates breaking the hook. Before installing, verify that your specific game version is listed in the README and check the VR troubleshooting wiki if you plan to use motion controls. The project is MIT licensed, so you can inspect and fork the code, but you must handle the dinput8.dll override manually on Linux. REFramework is a practical, community-driven tool, but it is not a polished commercial product.

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes