So you installed MGSHDFix, launched the game, and nothing changed. Or the resolution stayed stubbornly the same. Or your settings seem to evaporate between sessions. Take a breath: nearly every MGSHDFix problem has a boring cause and a five minute fix, and the same handful of mistakes account for almost all of them. The fix itself is reliable; it is the chain of small steps around it, the right folder, the right launcher setting, the right DLL, that tends to break. This guide walks through the common problems in the order you should check them, for the Metal Gear Solid Master Collection Vol. 1 on PC, Steam Deck, and Linux.
Problem 1: The fix does not load at all
Your game looks completely vanilla, the custom resolution is nowhere to be found, and the Config Tool’s settings have zero effect. This almost always means the game never loaded the fix, and the usual cause is the extraction folder. The contents of the MGSHDFix zip must sit directly in the folder of the specific game, next to the game’s executable, for example steamapps\common\MGS2 or steamapps\common\MGS3. If the files landed in a subfolder, in the collection’s shared folder, or in the wrong game’s folder, the game will never see the d3d11.dll proxy that loads the fix. Re-extract into the correct folder, and remember that each game needs its own install.
The second classic cause only affects people updating: you extracted a new version over an old one without deleting the old d3d11.dll first. The project specifically tells updaters to delete that file before extracting a new release. Remove it, extract fresh, and try again.
Problem 2: The resolution will not change
You set a custom resolution in the Config Tool, but the game keeps rendering at its old size. Nine times out of ten, the game’s launcher is overriding you. Open the launcher and set both Internal Resolution and Internal Upscaling to Default / Original. Resolution is handled entirely by MGSHDFix, and if the launcher insists on its own internal resolution, the two fight and the launcher wins in the worst way. Also double check that the custom resolution you entered actually matches your monitor. A typo in a resolution field produces a game that quietly falls back to something safe.
Problem 3: Settings do not apply or do not stick
If you changed options and nothing happened, ask yourself one question: did you run the Config Tool? On a first install, running the MGSHDFix Config Tool from the game’s /plugins folder generates the settings file the fix reads at launch. No settings file means the fix has nothing to apply, however many times you launch the game. Run the tool, make your changes, save, and relaunch. Also confirm you are editing the tool for the right game, since MGS2 and MGS3 each keep their own settings, and check that you closed the game before editing, so the file is not overwritten on exit.
Problem 4: The HUD looks stretched on ultrawide
You got the game world filling your ultrawide monitor, but the HUD and menus look stretched or out of place. That is what the experimental 16:9 HUD option in the Config Tool is for. It resizes the HUD and movies in MGS2 and MGS3 for widescreen play. Try it on; if elements still sit oddly, try it off. Both presentations are legitimate, the option is labelled experimental for a reason, and the right answer is whichever looks correct on your screen. If the whole image, not just the HUD, looks stretched, that points back to Problem 2: a resolution mismatch between the Config Tool and your actual monitor.
Problem 5: The image looks blurry
A soft, smeared image usually comes down to filtering. Try disabling bilinear texture filtering in the settings for a sharper, pixel crisp look, especially in the MSX games, and raise anisotropic filtering in MGS2 and MGS3 so textures at an angle stay detailed. Also confirm the game is truly rendering at your monitor’s native resolution rather than a lower custom resolution being stretched to fill the screen. Blurry plus stretched almost always means a resolution problem, not a filtering problem.
Problem 6: CPU usage is still very high
If one CPU core sits near 100 percent in menus and gameplay alike, you are probably running an old version of MGSHDFix, or none. Konami’s 1.4.0 patch introduced a busy-wait regression, and the fix for it arrived in MGSHDFix 3.0.3. Update to the current release, remembering to delete the old d3d11.dll before extracting. If CPU usage stays high after a proper update, suspect that the fix is not loading at all, and go back to Problem 1.
Problem 7: Steam Deck or Linux, the fix does nothing
On Steam Deck and Linux, the extra failure point is the launch option. The game runs through Proton, and Proton will ignore the fix’s DLL unless the game has the WINEDLLOVERRIDES launch option set in its Steam Properties. Add the exact line from the install instructions on the MGSHDFix release page, per game, and paste it rather than retyping it, because the string is punctuation sensitive. Windows players do not need this step, which is why friends on Windows cannot reproduce your problem.
Problem 8: Weird visual glitches at high resolutions
The project itself documents this one: some visual glitches and post-processing strength oddities at higher resolutions are known issues. If effects look unnaturally strong or something renders strangely after you pushed resolution hard, lower the custom resolution a step and test again. You are looking for the highest resolution that stays clean on your setup, and for most players that sweet spot appears quickly.
Problem 9: It worked, then Steam broke it
If the fix worked yesterday and stopped after Steam did something, file verification is the likely story. Verifying the integrity of game files compares your folder against the official version and repairs differences, which can remove parts of the fix. This is also why verifying is a good reset button when things are truly tangled: it restores a clean vanilla state. Either way, the remedy is the same: reinstall MGSHDFix into the verified game folder, run the Config Tool, and you are back.
And if all else fails, the nuclear option works because of how simple the fix is: remove the MGSHDFix files, verify game files in Steam for a guaranteed clean base, then install the latest release fresh, one step at a time, testing as you go.
Problem 10: The game crashes after installing the fix
A crash that appears right after installing usually means the game is loading a mixture of old and new fix files, or files meant for a different game in the collection. Work backwards cleanly: remove the MGSHDFix files from the game folder, launch the game and confirm the vanilla version runs, then install the latest release again slowly, making sure the zip contents go into this game’s folder and that you deleted any previous d3d11.dll. Test after each stage rather than all at once. Ironically, a properly installed MGSHDFix removes several vanilla crashes rather than causing them, so if a crash survives a clean reinstall of the fix, note exactly where it happens and check the project’s GitHub issues, where real solutions from other players accumulate.
Conclusion
MGSHDFix problems almost always trace back to one of a few small things: files extracted to the wrong folder, an old d3d11.dll surviving an update, launcher resolution settings fighting the fix, a Config Tool that was never run, or a missing launch option on Steam Deck and Linux. Work through the problems in order, change one thing at a time, and you will find your cause. The fix rewards a careful install with years of better Metal Gear, so the five minutes of detective work are well spent.
Read next: