A noticeable drop in frame rate after installing REFramework in Monster Hunter Wilds is a common concern, and it’s a fair one to have. In most cases though, the framework itself is not the direct cause of the slowdown. The actual cost usually comes from the scripts running through it, specific features it enables, or a system that was already close to its limit before REFramework entered the picture. This guide walks through the most common causes of FPS loss and how to isolate which one is actually affecting you.
Script execution overhead
REFramework itself acts as a lightweight hook into the game. It is not the part doing the heavy lifting. Any Lua scripts running through Script Runner are what actually consume CPU time, and every script placed in the autorun folder executes continuously during gameplay. When several scripts are active at once, their combined processing time adds up and can measurably affect performance.
You can narrow this down without guessing. Open the REFramework menu with the Insert key and go to Script Runner, where you can disable individual scripts one at a time and watch for a change in frame rate. If turning off a specific script noticeably improves performance, that script is your answer. This is slower than reading an exact number off the screen, but it works regardless of which REFramework build you’re on, and it tells you definitively which script is responsible rather than leaving you to guess.
Frame generation conflicts
Some versions of Monster Hunter Wilds show conflicts between REFramework and GPU frame generation technologies. The pattern to watch for is reduced GPU utilization while frame generation is turned on, paired with a lower or less stable frame rate than you’d expect given your hardware.
If this matches what you’re seeing, disable frame generation in the game’s graphics settings and compare performance with it off. If frame rate stabilizes, that’s your answer. It’s also worth checking the download page for a newer build, since compatibility issues between the framework and frame generation features tend to get addressed in updates as they’re identified.
Memory and VRAM usage
REFramework increases overall memory usage on its own, and it also makes it easy to load additional assets like high-resolution texture mods, which adds further VRAM pressure on top of that. On systems with limited VRAM, this combination can push memory usage past what the card can handle cleanly, and the game responds with sudden FPS drops or stuttering, particularly during movement or camera rotation when new assets are being streamed in.
If this sounds like your situation, lowering texture quality in the game’s graphics settings is the first thing to try, followed by cutting back on high-resolution texture mods specifically, since those tend to be the biggest VRAM consumers. REFramework also includes optimization settings of its own that are worth checking, since some of them exist specifically to reduce this kind of load.
Running a clean baseline test
The most reliable way to figure out whether REFramework itself or a specific mod is responsible for a performance problem is to strip everything back and test in stages.
- Rename the
dinput8.dllfile so REFramework does not load, then launch the game and record performance in a demanding scenario you can repeat. - Restore the file, but remove every script from the
autorunfolder, then launch again and compare against your first test. - If performance in step two matches the base game from step one, REFramework itself is not the cause. Add scripts back one at a time to find which one is responsible.
This process takes a few extra minutes but removes the guesswork entirely. Chasing a performance issue without a baseline usually means changing several things at once and never being sure which change actually fixed anything.
General optimization recommendations
A handful of habits reduce overhead regardless of what’s causing a specific slowdown:
- Keep the REFramework menu closed during gameplay, since having it open adds its own rendering overhead
- Keep graphics drivers up to date
- Check REFramework’s own performance-related settings and enable the ones relevant to your setup
- Add mods gradually and test performance after each one rather than installing several at once
- Avoid running multiple heavy scripts at the same time
Common symptoms and what they usually mean
| Symptom | Likely cause | What to try |
|---|---|---|
| Lower frame rate with frame generation enabled | Compatibility conflict | Disable the feature or update REFramework |
| Stuttering during camera movement | Memory or asset loading limits | Lower texture settings, reduce texture mods |
| Consistently low performance across sessions | High script execution load | Disable scripts one at a time in Script Runner to isolate the cause |
| Lag specifically in menus or UI | UI-related mod interference | Remove or replace the mod affecting the interface |
Conclusion
Most performance complaints tied to REFramework trace back to something running through it rather than the framework itself. Frame generation conflicts, heavy scripts, and VRAM pressure from texture mods account for the large majority of cases, and each one has a specific way to confirm it before you start disabling things at random. Running a clean baseline test first, then isolating scripts one at a time in Script Runner, gives you an actual answer instead of a guess, and usually gets frame rate back to where it should be within a few minutes of testing.
Keeping graphics drivers current matters more than it gets credit for here too, since frame generation compatibility fixes often land in NVIDIA or AMD driver updates before they land anywhere else. If none of the fixes above resolve things, the troubleshooting guide covers other REFramework issues that can present as performance problems even when they aren’t really about frame rate at all.