• Hey Guest. Check out your NeoGAF Wrapped 2025 results here!

Dishonored 2 PC performance thread

You do realize that's 2.5 times the pixels you have to push at 1080p right? People are getting some drops at 1080p with gpus like the 1070, which are a bit faster than a single 980Ti.

I realize that. I'm just trying to figure out where my drops are coming from. Seems to be very high VRAM usage in some problem areas, and that motion blur. Other than that, my experience has vastly improved with this last patch. SLI is doing it's job and I get a rock solid 60 FPS. TXAA isn't SO much of an eyesore with a ton of sharpening added in.
 
I realize that. I'm just trying to figure out where my drops are coming from. Seems to be very high VRAM usage in some problem areas, and that motion blur. Other than that, my experience has vastly improved with this last patch. SLI is doing it's job and I get a rock solid 60 FPS. TXAA isn't SO much of an eyesore with a ton of sharpening added in.

The weird thing is that on my end ( 2gb ) it doesnt stutter at all, its constant but very often goes below 40 ( even on ultra) which considering how fucked the game is should have killed my fps

There is room for improvement, so far they did a great job
 
It appears so.

And yes, you don't want to enable any form of V-Sync and/or triple buffering via any game with G-Sync enabled.

What about normal non Gsync display? I hate uneven frame pacing and tearing but I am tolerant to input lag (I play with xbox controller) and motion blur - so I asume it's ok to limit framerate to 60fps with RTSS and enable vsync (either in game or force through nvidia control panel) and triple buffering in game? Or is that not optimal setup?
 
What about normal non Gsync display? I hate uneven frame pacing and tearing but I am tolerant to input lag (I play with xbox controller) and motion blur - so I asume it's ok to limit framerate to 60fps with RTSS and enable vsync (either in game or force through nvidia control panel) and triple buffering in game? Or is that not optimal setup?

Frankly, I often play with mouse and keyboard and don't notice any increased input lag with triple buffering on. I guess it depends on your sensitivity to it.
 
What about normal non Gsync display? I hate uneven frame pacing and tearing but I am tolerant to input lag (I play with xbox controller) and motion blur - so I asume it's ok to limit framerate to 60fps with RTSS and enable vsync (either in game or force through nvidia control panel) and triple buffering in game? Or is that not optimal setup?

Latency-wise, if you're only averaging 45 frames on a 60 Hz display, (DX11) triple buffer v-sync actually has the least input lag. It also prevents the lock to 30 fps when you're below 60 fps with double buffer. However, if you're exceeding 60 fps at all times, triple buffer v-sync has more input latency over double buffer v-sync. This is because when your fps exceeds the refresh rate of your display, the buffers begin over-queuing frames, thus delaying their appearance on-screen. Triple buffer v-sync is worse than double buffer in this instance, because it has an extra buffer to queue with. It really depends on the situation, but double buffer v-sync has about 2 frames of input lag, and triple buffer v-sync (DX11) has about 3 frames.

As for an RTSS limit of 60 fps, that really only matters if you can sustain 60 fps or more 99% of the time, otherwise, it doesn't engage below 60 anyway. That, and believe it or not, if RTSS is the limiting factor, it actually adds 1 frame of latency itself whether or not you have v-sync enabled. So that's something to consider. I could go on, but my post would turn into an article.

Bottom line, if you can sustain 60+ fps 99% of the time, double buffer, if you can't, triple buffer.
 
Why does the game look so bad?

dCCFiWv.jpg

1900x1200 @ medium on everything. No adaptive res. Runs at 30fps. Is there a particular setting that makes it look blurry and ugly? (Geforce 770 so pretty old)
 
Why does the game look so bad?



1900x1200 @ medium on everything. No adaptive res. Runs at 30fps. Is there a particular setting that makes it look blurry and ugly? (Geforce 770 so pretty old)

Are you using TXAA? Medium textures are probably also a contributing factor. What I'm wondering is why it's so friggin dark in your screenshot. Crushed blacks everywhere.
 
Finally got some time to give it a quick test, and performance has greatly improved. Still could be better, but its playable with a mouse now and reasonably steady.

I won't be refunding it now, and am look forward to the weekend :]
 
Why does the game look so bad?



1900x1200 @ medium on everything. No adaptive res. Runs at 30fps. Is there a particular setting that makes it look blurry and ugly? (Geforce 770 so pretty old)

Does your game really look that dark? I think it's steam. I just took several screens and they all appeared darker than what I'm playing.

Is 1.2 the last patch we're receiving?

BYfc.jpg
 
Does your game really look that dark? I think it's steam. I just took several screens and they all appeared darker than what I'm playing.

Is 1.2 the last patch we're receiving?

We're due at least one more performance patch as well as a content patch (new game plus). I figure they'll be making performance updates for the next few weeks at least.
 
Does your game really look that dark? I think it's steam. I just took several screens and they all appeared darker than what I'm playing.

Is 1.2 the last patch we're receiving?

BYfc.jpg

1.2 proper is still some days away, though since Bethesda has recently been advertising the betapatch build as 1.2 now that it's been pushed through to the public branch, "patch2" may end up being 1.3.
 
I gave FXAA High a go and man does it suck with aliasing. Only positive is, it wasn't as blurry as TXAA, but jaggies/shimmering were too much.
 
I gave FXAA High a go and man does it suck with aliasing. Only positive is, it wasn't as blurry as TXAA, but jaggies/shimmering were too much.

Yeah, the FXAA implementation is rather terrible. It's almost completely ineffective and the visible texture "seams" are immensely distracting.
 
So with the deals going around I figure I better check in here. Not looking so good. How bad would it be on my 1080? Should I be looking at the PS4 version instead?
 
So with the deals going around I figure I better check in here. Not looking so good. How bad would it be on my 1080? Should I be looking at the PS4 version instead?

If you also have a high-end CPU, you should be golden, occasional stuttering aside; and even if maintaining 60fps is an issue, you can now cap the game to 30fps without a dramatic increase in load times.


Sure, I could have linked to them directly, but reinforcing the idea of reading the OP is important in threads like these.
 
How does it feel to play with mouse when locked at 30 fps? For comparison, I thought it was fine in Deus Ex, but it feels like shit in some games.
 
How does it feel to play with mouse when locked at 30 fps? For comparison, I thought it was fine in Deus Ex, but it feels like shit in some games.

Tried it last night, and as I was playing this fantastic "cinematic" experience, my playthrough was shattered by what appeared to be a constant dip to 20s in specific areas, there are detailed zones that run at 60 and some fairly simple ones that drop your fps to 20s, its ridiculous

I see some movement on steamdb, some patch 2 stuff added 24h ago
 
Latency-wise, if you're only averaging 45 frames on a 60 Hz display, (DX11) triple buffer v-sync actually has the least input lag. It also prevents the lock to 30 fps when you're below 60 fps with double buffer. However, if you're exceeding 60 fps at all times, triple buffer v-sync has more input latency over double buffer v-sync. This is because when your fps exceeds the refresh rate of your display, the buffers begin over-queuing frames, thus delaying their appearance on-screen. Triple buffer v-sync is worse than double buffer in this instance, because it has an extra buffer to queue with. It really depends on the situation, but double buffer v-sync has about 2 frames of input lag, and triple buffer v-sync (DX11) has about 3 frames.

As for an RTSS limit of 60 fps, that really only matters if you can sustain 60 fps or more 99% of the time, otherwise, it doesn't engage below 60 anyway. That, and believe it or not, if RTSS is the limiting factor, it actually adds 1 frame of latency itself whether or not you have v-sync enabled. So that's something to consider. I could go on, but my post would turn into an article.

Bottom line, if you can sustain 60+ fps 99% of the time, double buffer, if you can't, triple buffer.

Thanks for a detailed response. I bought1080 precisely to sustain 60+ as often as possible, but realistically even the best optimized games can momentarily drop below 60 and then double buffered vsync would mean that the framerate halves, which I hate.
Also, I am using RTSS to limit to 60 because I monitor frametime using Afterburner overlay and I noticed in multiple games that when I use just vsync and have stable 60fps, the frametime is not a stable 16.6ms, it "wobbles" slightly (like 16.4, 16.8, 17) which may cause stutter. But when I use RTSS lock to 60 then frametime is stable at 16.6.
 
I sure hope so. I just tinkered around with settings and what not and the performance at different settings just baffles me.

I really want to enjoy this game.

Yep, I too want to enjoy it but even if I struggle to like it, I cant because of the damn performance
 
"MOVEMENT"

usually means soon

To be clear, my post was an answer to your question, not a knee-jerk response to your citing of SteamDB. Bear in mind that if Bethesda hadn't made a password-free beta branch for 1.2 we'd still be waiting for the first patch after two weeks (more or less) and counting, and even disregarding that, the patch2 branch has been updated a few times over as many days, since the betapatch branch was made available -- there's nothing special about the update the patch2 branch received now that points to 1.2 proper (or 1.3 as Bethesda may end up labelling it) being around the corner. For all we know it was updated because QA found a bunch of issues and now the new build has to go through testing, which is to say that there's really no telling whether the next update for players is an hour away or another week out.
 
To be clear, my post was an answer to your question, not a knee-jerk response to your citing of SteamDB. Bear in mind that if Bethesda hadn't made a password-free beta branch for 1.2 we'd still be waiting for the first patch after two weeks (more or less) and counting, and even disregarding that, the patch2 branch has been updated a few times over as many days, since the betapatch branch was made available -- there's nothing special about the update the patch2 branch received now that points to 1.2 proper (or 1.3 as Bethesda may end up labelling it) being around the corner. For all we know it was updated because QA found a bunch of issues and now the new build has to go through testing, which is to say that there's really no telling whether the next update for players is an hour away or another week out.

I agree, all we can do is wait or play the game with adaptive rez set to Performance which makes it look like its 640x480 but hey, 60fps
 
Top Bottom