mwyndham.dev


The Ultimate Monster Hunter Wilds OBT 2 Graphic Setting Guide

Updated at January 30, 2025

Published January 28, 2025

NonWork
MonsterHunter
Guide
Cover Image

This will be guide, as thorough as I possibly can do, regarding Graphic Setting for Monster Hunter Open Beta test. This guide aims for people to have their best experience coming into Open Beta Test 2.

Disclaimer

  • This guide only cover the Graphic Setting as available from the first Open Beta, there's small chances that some setting will be different for OBT 2 and will certainly differs from the final product.

  • Performance stated here are firmly for OBT, don't extrapolate performance number stated here as representative of the final product.

  • Most of the settings recommended here are tested with AMD Graphics Card, but most likely covers all GPU use case except RTX 4000 Series due to frame-gen advantage.

  • I will not shy on recommending frame-gen. I've tested thoroughly with various frame-gen solutions and conclude that this game is enjoyable with it, even with sub 60 FPS base framerate, though there are nuances that will be detailed later down below.

  • The game code is simply not optimized. Without frame-gen (or baller folks with 7800x3d or higher CPUs) the FPS will be hovering around 30-45 FPS on the savannah region which is the hardest to run playable area, with the biggest culprit of performance tank around trees with traps. This area will tank the performance even on R7 5700X3D CPU.

  • This OBT Build loves high CPU frequency. So if you're out of luck CPU wise, try to OC your CPU to gain some grounds.

  • Minimum recommended GPU to follow this guide is DX12 Ultimate compatible GPU with 8GB of VRAM or more, though will give recommendation for cards with 6GB of VRAM later (sorry RX 580).

  • Other Mandatory Minimum Specs include 16GB of RAM, SSD, and CPU not older than Ryzen 3000 / Intel 10th Gen with 6 cores or more.

TL;DR

General Recommendation

Another reminder that the game is simply hard-capped FPS wise around 45 FPS on the savannah area even with R7 5700X3D, so example, if your FPS is already reaching 45 FPS, any extra setting that theoritically gives performance won't work. But if your FPS says 30-35, it will nett you extra FPS.

General Graphic Preset recommendation is as follow:

  • Low Preset for RTX 2060 Super or lower,

  • Medium Preset up until RX 6700XT class performance GPU.

  • Higher card can work with High Preset.

  • RX 7800XT class and above can deal with Ultra.

  • Set Variable Rate Shading (VRS) to Performance. Free 1-2 fps with 0 visible downgrade.

  • Texture Quality and Shadow Quality depend on VRAM (Don't Push your luck on this unless you wanted origami monsters).

    • < 8GB of VRAM should stick with Low or Very Low,

    • 8 GB cards should stick with Medium,

    • 12 GB can go to High,

    • 16 GB can reliably use the Hi-Res texture.

  • Texture filtering is whatever you want, not very noticeable. also applicable to:

    • Sky Quality

    • Ambient Occlusion

    • Contact Shadow

    • Bloom

  • Do not touch shadow related settings except Shadow Quality, let it defaults from presets.

  • Settings that affects performance as follows:

    • Grass and Tree Quality (3 fps per setting level)

    • Subsurface Scattering (1 fps per setting level)

    • Ambient Lighting (1-3 fps per setting level)

    • Volumetric Fog (5 fps per setting level)

    • Mesh Quality (4-5 fps per setting level)

    • Motion Blur will tank the performance as well (up to 5 FPS), and it looks bad anyway. Disable it.

  • For AMD and Intel GPU, Upscaling is to taste between FSR and XeSS.

    • FSR will be sharper but more pixelated and has ghosting issue on swaying vegetations.

    • XeSS will be fuller but also blurrier. XeSS also has performance hit vs FSR, around 2-4 FPS.

  • For RTX 4000 Series GPU DLSS is no brainer. Including frame-gen.

  • For RTX 2000 and 3000 Series it depends, more on that below on frame-gen section.

  • Upscaling Quality wise for 1440p:

    • RX 6600XT card or lower should stick with Balance or lower,

    • Higher cards can do Quality.

  • For 1080p:

    • RX 6600XT card or lower should stick with Quality (no need to be lower unless it has less than 8GB of VRAM),

    • Higher cards can do Native AA, but I still recommends FSR /XeSS even on it.

Frame-Gen Recommendation

A Lengthy Preface to Frame-Gen

If you think I'm crazy that I recommend frame-gen here, I can't help but agree. But it is the only choice if you want to get that sweet 60 FPS experience, and honestly? it wasn't that bad.

Monster Hunter has been generally controller heavy games, and the i-frame is pretty generous. I tried with basically every melee weapons + bow and find that it's totally playable and enjoyable with frame-gen... with some caveat.

So here's general rule of thumb for frame-gen:

  • Framegen at minimum should be at least 30 FPS. There's no wiggle room here.

  • If you use Mouse + Keyboard, sorry. Any frame-gen with base FPS less than 60 will feel bad. No recourse for you on that.

  • There are 4 different frame-gen solution that you can use (more details below):

    • DLSS frame-gen -> Has pretty bad input latency unless you enable Reflex.

    • FSR frame-gen -> Has pretty bad input latency and has no latency mitigation outside Anti-Lag (which is bad).

    • AMD Fluid Motion Frame 2 (driver level frame-gen) -> Noticable but small input latency, though the smoothness is not very good if your base FPS is less than 40.

    • Lossless Scaling -> Magical input latency. If there's any, I can't notice it via Bluetooth Controller at all.

  • For weapon that don't rely on fast camera movement (even in focus mode) such as Hunting Horn, Hammer, Great Sword, Switch Axe, and Bow. Then you guys got nothing to worry about. Even base 30 FPS will suffice.

  • For weapon that rely on fast camera movement such as Insect Glaive, Longsword, Gunlance, Lance, and Charge Blade, my recommendation is to test which is acceptable for you:

    • Frame-gen at less than base 40 FPS (except when using AFMF2 or Lossless Scaling) will gives that yo-yo feeling to the camera movement, especially if you rotate the camera often. So try to have at least 40 FPS base and still you try for yourself is it to your liking or not.

    • No frame-gen will generally gives noticably better camera control (except, again if you're using AFMF2 or Lossless Scaling), but then it's sub-60 FPS experience.

  • On the topic of sub 40 base FPS, again except for AFMF2 and Lossless Scaling framegen, your parry i-frame will be affected due to input latency.

    This particularly affect Longsword (Iai Spirit Slash), Lance (Counter Thrust) and Switch-Axe hard. So if you use frame-gen and notice that you constantly whiff ISS, try disabling frame-gen or use AFMF2 / Lossless Scaling.

Frame-Gen Recommendation

If you're RTX 4000 Series owner, congrats! your choice is simple: Want 60 FPS? Enable Frame-Gen + Reflex and vice versa if you dislike the latency.

For other folks, I'll split this into 3 categories:

  • PC with CPU equivalent of Ryzen 5 3600 class (Intel equivalent: i5 10400) + AMD GPU

  • PC with CPU equivalent of Ryzen 5 3600 class (Intel equivalent: i5 10400) + Non AMD GPU

  • CPU equivalent of Ryzen 7 5700X3D or higher (Intel equivalent: i7 12700K).

Reasoning: The CPU Performance will impact your options the framegen solution available to you.

AMD GPU + R5 3600

If you're okay with little but of input latency, you can enable frame-gen (though then you'll have to stick with FSR). It has one big deal-breaker outside latency though: ghosting.

Apparently it'll be fixed for release version but ALAS, it'll be there for OBT unless Capcom gives us a surprise.

If you sensitive to input latency / dislike ghosting, I recommend not using the in-game frame-gen. Instead use AFMF2 built into AMD Adrenaline app.

During in game, press Alt + R > Enable AMD Fluid Motion Frame 2 > Set Search Mode to High & Performance Mode to Quality.

Non AMD GPU + R5 3600

It'll be similar to the one above, except that you don't have the options for AFMF2. There are alternative solution using Lossless Scaling (see the next section) but I do not recommend due to the CPU limitation.

Using Lossless Scaling will causes issue such as reverse ghosting issues around player character, where some important features such as face can just disappear when panning around player character, akin to screen tearing.

it'll also have very bad stutter issues, especially when it comes to rapid camera movement (target camera, focus mode).

For RTX 2000 & 3000 series, you'll have to pick your poison: DLSS without frame-gen (you won't go higher than 45 FPS average on savannah region, guaranteed) or go with FSR and enable frame-gen.

I saw some methods that maybe possible to spoof the game so it'll able to use DLSS with FSR frame-gen, though I haven't been so lucky: https://github.com/cdozdil/OptiScaler.

Any GPU With R7 5700X3D or Higher

This section exists for one sole reason: Lossless Scaling.

Outside DLSS Framegen, Lossless Scaling is the best Framegen implementation out there. It has incredibly low latency penalty (on controller it's basically indistinguishable from non-framegen) and the image quality is very good for External Framegen.

But there are several caveats to this:

  1. It's paid app, so you have to buy it.

  2. FPS after framegen shouldn't exceed screen refresh rate.

  3. Unstable FPS could cause stuttering.

  4. Heavy on CPU Requirement.

Reason No. 4 is the reason this section exists, and to mitigate reason No. 2 & 3, we need to find the best framerate cap you need to set the game.

General Rule of Thumb for the framerate cap:

  • If you have 60Hz monitor, your only choice is 30fps cap.

  • If you have high refresh rate with VRR support, set the fps cap to the 1% lows (not .1% lows!) of the game.

  • For Wilds OBT, my best guesstimation is around 35 fps to 40 fps. I highly doubt you can get 60 FPS without something like 7800X3D CPU to brute force your way.

Now, step by step on how to get the best result with Lossless Scaling:

  1. Install Lossless Scaling and Riva Tuner Statistics Server. RTSS will be used to set framerate cap. In-game framerate cap is not very good and will introduce stutter.

  2. Open RTSS.

  3. Click Add, select the .exe of the game.

  4. Set Framerate limit to the FPS you choose from previous step.

  5. Open the game.

  6. Go to setting and make sure Framerate is Uncapped & VSync is disabled.

  7. Next open Lossless Scaling, set the settings to LSFG 3.0.

  8. Click Scale, and go back to your game.

  9. Give it 5-10 seconds untill Lossless Scaling is detecting the active window.

  10. For the first minute or 2, the game will be stuttery due to the Lossless Scaling algorithm. It'll get better soon after.

Thats It!

Next time you play, you can skip step 1, 3, 4, 6 and 7.

#NonWork #Guide #MonsterHunter