Metal Gear Solid V: The Phantom Pain PC performance thread

So does it actually play better with KB+M? I've never even thought of trying that.

I won't call KB/M superior in this, controller is way more intuitive when controlling Snake's detailed move sets and you really need those analog sticks to control your movement speed.
 
Ahh, Ctrl. Makes sense, thanks.
It's still dreadfully slow. I wish they would have bound the speed to the upper limit of the sneak speed like you can get with a controller. It's the biggest issue I have with the kb/m. Hopefully someone smarter than I can find out what file the speed is bound to and let us make the necessary adjustments.
I prefer it, others prefer controller. Try and see!
I prefer the kb/m too. Feels so bad ass to pop out of cover and easily headshot a small group of 5 guys and have them all fall essentially at the same time. Really makes Snake feel like a boss.


Also. Is anyone getting extreme amounts of judder when trying to pan the mouse around during cutscenes? It's terrible. As a result, I'll tend to not look around during these moments and that's kind of a bummer.
 
I read that the physics are based on frame rate so going above 60 causes chaos. I think rock, paper, shotgun ran the article.

I'm sure there's some way to get above 60 though.
In GZ it caused throwables to get stuck in the air, so I assume it will be the same for TPP. So it's not really chaos but still probably not recommended. Bit of a letdown as a lot of people could push the game past 60 easily but whatever :)
 
This game looks fucking incredible, hot damn! I have most things on Extra High and I am yet to have a dip from 60fps. I have only just started in Afghanistan but so far so good.
 
Running a solid 60fps except when certain cutscenes kick in. I drop to like 17 in those cases. Need to investigate where the bug is occurring.
 
Anybody with a 290/290x have impressions? I saw one, but I'd like to hear more of what to expect when I head home. Was really hoping you'd max it like GZ at 1080p.
 
I noticed on the NVIDIA comparison screens that the default post processing stuff makes stuff look pretty damn blurry.

What's the best thing to do? Have it on low?

Is there an alternate AA solution I should use?
 
So yeah, quick update.

Native 4K
All in game settings maxed

3770k
SLI 970 FTWs
16GB
W10


Getting 57-60fps around mother base, and what feels like the same framerate in Afghanistan. Eating breakfast and will test out how the numbers hold up on mission.

Very pleased I bought this on steam, even though my PS4 CE arrives today.


So yeah, did a few missions. Get between 46-60 FPS at those settings with explosions and gunfights galore.

More than worth it for the boost in quality 4K gives. Game looks stunning at times. Definitely the best looking cross gen game ever. And hopefully the last I ever buy. (This gen obviously)
 
i7 4770k
16GB RAM
eVGA GTX 980ti SC ACX
Windows 10

Everything max @4K: 50-53 FPS
Everything max @1440p: Solid 60FPS

It really doesn't look all that different to me in 4K, so I'm sticking with 1440p. Oh and I haven't installed the new GeForce drivers yet.
 
Don't know if it was posted before, but widescreen has been fixed!

both 2560 x 1080 and 3440 x 1440!!!!


http://www.wsgf.org/forums/viewtopic.php?f=95&t=30223


file.php
 
I have always disabled 'Depth of Field' in every game I've played, yet the Nvidia guide suggests enabling it here, at the expense of other settings, if necessary. Is there a reason for this advice?
 
So yeah, did a few missions. Get between 46-60 FPS at those settings with explosions and gunfights galore.

More than worth it for the boost in quality 4K gives. Game looks stunning at times. Definitely the best looking cross gen game ever. And hopefully the last I ever buy. (This gen obviously)

Good to know. Won't get to start for another day or two, but it sounds as scalable as GZ.
 
I have always disabled 'Depth of Field' in every game I've played, yet the Nvidia guide suggests enabling it here, at the expense of other settings, if necessary. Is there a reason for this advice?

No. I play entirely without it.

DOF is still active in cutscenes regardless of your settings, so it's a win win for everyone if you have it off.
 
So.

i7 5820k oc 4.0ghz
GTX 980
16gb Ram
2560x1440

Getting a mostly solid 60 fps at 1440p with a single 980 which is impressive, only drops seem to happen with heavy effects or alot of light sources.

The dust that comes off the horse can drop fps to the 50s under certain situations and multiple light sources can effects fps by about 2-5 fps

Overall very happy though runs fantastic :D
 
My rig is going on 4 years old at this point:

i5 2500k @ stock speed.
Radeon 6870 1Gb Vram.
8 gigs ram.

Running medium-high 1080p and its been 60fps 99% of the time. Really amazed at how well this performs considering the eye candy. Haven't played a game this optimised since Max payne 3, and it's even more impressive considering it's open world.
 
I have always disabled 'Depth of Field' in every game I've played, yet the Nvidia guide suggests enabling it here, at the expense of other settings, if necessary. Is there a reason for this advice?
it's entirely personal preference, they recommend it because it's a more noticeable effect than other settings. whether that's what you prefer is up to you.
 
Just wanted to say that the DS4 is supported natively, but you need to have it turned on before you start the game up.
I've been using it without DSwindows or anything like that.
 
Sick! Does replacing the .exe have any issues with steam? Like do game updates override it or steam achievements stop working?
According to the forum posts achievements work fine but any update will overwrite the executable so this approach is far from ideal. But I expect there'll be a universal approach soon. Jelly of everybody who can enjoy the game at 21:9 :D
 
I read that the physics are based on frame rate so going above 60 causes chaos. I think rock, paper, shotgun ran the article.

I'm sure there's some way to get above 60 though.

Ah so maybe that's it. It sucks that I can't use my monitor to it's full potential but a locked 60 still isn't bad.
 
Just wanted to say that the DS4 is supported natively, but you need to have it turned on before you start the game up.
I've been using it without DSwindows or anything like that.

Shame game doesn't give you DS4 prompts natively too. Always mindfuck to see e.g. Y on screen when it's triangle on DS4.
 
I tried using the optimized GeForce Experience DSR setting and the game opens in a tiny window even though the game is in fullscreen. How can I fix this?
 
i7 920 @3.7ghz, 760 GTX, 16GB of RAM, Windows 10, and the prologue played flawlessly at 1080p with zero perceptible slowdown. I can't believe I almost upgraded for this game. Guess I'll have to wait for Star Wars: Battlefront before it's worth it.

Also used a DS4 with ds4windows, worked great.
 
Is it normal that ground textures in the distance stay the same (i.e. a blurry mess) when you look through your binoculars? Shouldn't it load better textures? I have everything set to max.
 
Oh man, it's so painful to be at work while MGSV waits for me at home. I barely played after the prologue yesterday and today's morning and boy am I fucking craving for more. 10pm can't come soon enough.

EDIT: And wrong MGSV thread. lol
 
Guys, I probably missed it in this thread, but can anyone confirm that the fucking mouse cursor is gone while playing with a gamepad?
 
So this game still does not support my bind look (v) to a mouse button. How would I get around doing that?

I'm going to use the utility that comes with my mouse that should let me map a key press to the extra mouse button presses. Hopefully, it has per-application profiles so it's something I can set and forget for just this one game.
 
I am amazed at how well this game runs. I had to turn down a few settings for GZ and it would still drop a few fps quite a but of the time. But here in TPP I can't recall it dropping below 60fps once with the same settings. This runs a lot better than GZ does and that was already a great port. Bravo to the PC team!
 
Top Bottom