Guide with player reports
Mistfall Hunter Known Issues and Performance Status
Official launch optimization work, documented bug fixes, clearly labeled beta observations and the checks still required for the release build.
Official status
The June 17 Open Beta update said it improved first-entry stutter and crash cases and fixed several control, marker and equipment-display problems. The Open Beta later ended, so those notes describe a historic test build rather than a guarantee about launch performance.
In the July 17 launch announcement, Bellring Games says it has focused on Unreal Engine shader precompilation stutter, smoother asset loading when many characters appear, average frame rate and memory usage. It also reports fixes for crashes linked to vegetation animations and AMD graphics-card hair rendering. These are developer-reported changes, not independent launch benchmarks.
DevNote #7 adds device-tier presets, console and lower-end PC tuning, 2K and 4K output work, camp frame-rate improvements, smoother inventory and map interfaces, and reductions to combat microstutter. The developer also says shader precompilation can still create first-use work that varies by hardware.
Launch fixes named by the developer
The same announcement lists fixes for Quick Buy failures, Spectator mode exits, server mail, stage-selection errors, Xbox-friends login overflow, loading-screen reconnects, a low-terrain softlock, controller invitation UI freezes, Soul Ferry audio, class-switch skill problems and occasional loot pickup failures.
Quick Buy still carries an official caveat: rapidly changing market prices may require another attempt. Performance work is described as ongoing after launch, so a clean release-build benchmark is still required before this wiki marks the broader issues as resolved.
Community observations
Players in a Google-ranking Reddit discussion reported periodic stutter, frame-rate drops and questions about field-of-view controls. These reports come from a completed test and may vary with hardware, drivers, shaders, servers and build versions.
This page does not recommend registry changes, launch flags or speculative fixes. It records the questions so they can be retested against the release client.
What to check at launch
After release, testing should record the game build, hardware, graphics preset, resolution, driver version and a reproducible location before publishing a performance conclusion.
- Shader and first-entry stutter
- Crash frequency
- Frame pacing across maps
- Field-of-view options
- Controller prompts and remapping
- Network latency and desync
Questions answered
Did Bellring Games fix beta stutter?
Bellring Games reports more shader, asset-loading and combat microstutter work in DevNote #7, but the July 30 release build still needs reproducible hardware testing before the issue can be considered resolved.
Can the field of view be changed?
A definitive launch-build FOV option has not been confirmed by the official sources reviewed here.
Are Reddit performance reports conclusive?
No. They are player observations from earlier builds and remain version- and hardware-dependent until reproduced.