Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Since game will usually look for the libraries on the folder your .EXE is located, THEN search for them on the locations you've added to your PATH variable, copying the correct ones on your MGSV folder will usually fix the issue.
As long as you have installed the requirements from the game (if you're using Steam, it will usually autodownload and install the required redistributables for a game the first time you try to run it, several other game installers tend to do the same, and in many other cases, you can find the required redistributables on a subfolder called .\REDIST\ of the installation media if you happen to have a physical copy) you can usually find those DLL's in your .\<Windows folder>\System\ (if you OS is x64, this is the x64 version) or <Windows folder>\System32\ (x86 version) locations. You can copy the required library from there.
Most applications initially search for a specific library in the same folder they're running from (same folder where the .exe files are located), and if they don't find it there they'll check your PATH environment variable for another locations to load it from (Those .\system and .\system32 folders are found in the PATH environment variable), this way you can "force" an application to load a specific library it requires if you copy it to the same folder you can find the game's .exe files.
Some games may have different executables depending on your OS, so you can run either the 32bit(x86) or the 64bit(x64) version. The issue with the PATH variable is that folders contained are checked sequentially, and will stick with the first match it finds. So let's say you're trying to run an x64 game, but in your PATH variable the .\system32\ (x86 version) folder path is found before the .\system\ (x64 version) folder path. If you have both versions of the same library installed (x86 and x64), the game checks your path for msvcp110.dll and it will find it on the .\system32\ folder, so it will try to load an x86 library when your game requires to load the x64 version.
But when I pay premium price, for a AAA game, it is my realistic nature to assume, the ♥♥♥♥♥♥♥♥ game will work once I've downloaded it. The fact that you then have to research a literal ♥♥♥♥ ton of "fixes", finding this line or that line, copy paste it to here or there, turn this or that off, is pretty ♥♥♥♥♥♥♥ infuriating. And all that just to get the product, the $30-60 dollar game, you paid premium dollar for, to work.
Here's a quick fix, refund the ♥♥♥♥♥♥♥♥ game, watch videos of said AAA game on youtube, buy a game you can play out of the box.
I had same problem, tried all these didnt work.
BUT
If youre using Nvidia card and have shadowplay aka Nvidia share on, go to GeForce Experience and disable it. Worked instantly for me
Same issue. Same solution. Thanks a bunch!