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

Dishonored 2 PC performance thread

Well, I have a 1070 (a freaking 1070!), 16 gb of ram, an ssd, a modern i5, and it runs like crap when getting to the first main city. This is unacceptable. I feel ripped off frankly.
 
Well, I have a 1070 (a freaking 1070!), 16 gb of ram, an ssd, a modern i5, and it runs like crap when getting to the first main city. This is unacceptable. I feel ripped off frankly.

Same here. Got a 1060, 16gb, 6600k. After the first two hours I thought it was fine. Not good, but fine. Now I could take a look at a more crowded scene. 28 fps. That's unbearable. Got framedrops of over 70 fps. WTF...

Game is great so far, however. Atmosphere is as good as in D1. Cannot wait for a patch.
 
Anyone tested the new NVIDIA drivers that came out a few hours ago?

375.86

Nothing in the changelog/mentions about Dishonored II (other than an Ansel UI bug with SLI) but maybe it made some sort of improvement.

Hoping the new drivers get DSR working properly. The texture work in this game blows my mind and all the AA options just seem to blur the overall image. I would love to downsample instead.
 
Hoping the new drivers get DSR working properly. The texture work in this game blows my mind and all the AA options just seem to blur the overall image. I would love to downsample instead.

Have you tried Reshade with Lumasharpen?

Sorry for the insistence on this, I swear I'm not being paid, but the results are great.
 
Anyone tested the new NVIDIA drivers that came out a few hours ago?

375.86

Nothing in the changelog/mentions about Dishonored II (other than an Ansel UI bug with SLI) but maybe it made some sort of improvement.

A bit of warning for GTX1080 owners - there seems to be a memory clocking bug in this driver which prevents the cards to push VRAM clocks above 810MHz. Maxwell and - probably - other Pascal cards owners should be ok.

Edit: GTX1060s seems to affected as well according to Reddit reports.
 
A bit of warning for GTX1080 owners - there seems to be a memory clocking bug in this driver which prevents the cards to push VRAM clocks above 810MHz. Maxwell and - probably - other Pascal cards owners should be ok.

Edit: GTX1060s seems to affected as well according to Reddit reports.
My GTX 1070 doesn't seem to be affected, on Windows 7 at least.
 
Might be specific brands? Perhaps memory brand related even (Samsung/ Micron)? Having no memory issues on my EVGA 1080 after driver upgrade.
 
A bit of warning for GTX1080 owners - there seems to be a memory clocking bug in this driver which prevents the cards to push VRAM clocks above 810MHz. Maxwell and - probably - other Pascal cards owners should be ok.

Edit: GTX1060s seems to affected as well according to Reddit reports.

I just checked, my 980 Ti on Win 10 is indeed not affected by the issue.
 
Might be specific brands? Perhaps memory brand related even (Samsung/ Micron)? Having no memory issues on my EVGA 1080 after driver upgrade.

So far I'd say that all Pascal cards running under Win10 are affected by this issue. So if you have GeForce 10x0 and using Win10 - avoid 375.86 driver. I'm sure there will be a hotfix in a day or two.
 
I thought my performance problem resolved itself (sometimes this does happen, actually). I got stable 60fps in areas I had like 35 or 40 before. But just after proceeding for like five minutes the fps drop almost constantly over time to mid 30's and stay there. Lowering graphics settings doesn't help.

It really is a shame. Normally I'd would ask myself now why I keep pre-ordering broken stuff like this. But then again I got 20% off that seems like a nice deal. I hope we don't have to wait weeks for this being fixed!
 
I thought my performance problem resolved itself (sometimes this does happen, actually). I got stable 60fps in areas I had like 35 or 40 before. But just after proceeding for like five minutes the fps drop almost constantly over time to mid 30's and stay there. Lowering graphics settings doesn't help.

It really is a shame. Normally I'd would ask myself now why I keep pre-ordering broken stuff like this. But then again I got 20% off that seems like a nice deal. I hope we don't have to wait weeks for this being fixed!

Maybe this is a result of the game also processing AI behaviors? Didn't Hitman have a similar problem?
 
Tuesday night and still no sign of a patch? Yeah please go ahead guys I don't have to play the game that I have pre-ordered because I have trusted and loved you guys. Yeah just go ahead and fuck me right up in the ass and make sure that I'll will not be buying any of your games anymore good stuff.
 
Tuesday night and still no sign of a patch? Yeah please go ahead guys I don't have to play the game that I have pre-ordered because I have trusted and loved you guys. Yeah just go ahead and fuck me right up in the ass and make sure that I'll will not be buying any of your games anymore good stuff.

Always expected later in the week.
 
In Dishonored 2 it does nothing. At least I couldn't get it trigger no matter what.

Wouldn't be surprised if it turns out that since it defaults to 75 it always stays there no matter what you set it to and that's why it's rather blurry all the time (w/o TXAA).
 
Wouldn't be surprised if it turns out that since it defaults to 75 it always stays there no matter what you set it to and that's why it's rather blurry all the time (w/o TXAA).

In games config file it's set to "0" state aka disabled. Makes few of us think whole thing is broken all to hell and not even enabled by devs.
 
Anyone got controller settings recommendations for PC?

Just doesn't feel right at default but then again there's something up with them, mostly likely bugged. Need that patch asap.

It feels so awkward moving about and then you've got that constant stuttering/framedrops eveytime you turn around.

If only it ran as good as the original. I could play that on my old rig with super sampling.
 
Reshade Lumasharpen effects with a pretty strong sharpening setting.

Before:

30972357386_11976418f7_o.jpg


After:

31007623745_feb2cfbff4_o.jpg


--

Before:

30706087780_5607b8b0fc_o.jpg


After:

25371860169_7d2dff12c1_o.jpg


The worst part of all this fucking about is that the first scene has completely lost its impact for me, which is a shame.
 
Disappointing launch, especially with how well the first game ran. Pretty sure I played that on a 560 or something.. This was (is) my most anticipated game of the year. I was always planning on waiting until Dec. to buy it while I finish some other stuff, but I really hope I can run it on my 970 by then.
 
Took some days off to play this game. Doesnt look like we'll be getting a patch this week and even if we do my guts are telling me it wont improve much in the performance department. Damn it.
 
Disappointing launch, especially with how well the first game ran. Pretty sure I played that on a 560 or something.. This was (is) my most anticipated game of the year. I was always planning on waiting until Dec. to buy it while I finish some other stuff, but I really hope I can run it on my 970 by then.

Can't remember what hardware I had when D1 released but I remember it was the first game that I could downsample on release and still get 60+ fps.
 
how much of a price drop will the gtx1080 get in 6 months, by march or next summer?

The release of the 780 Ti and 980 Ti slightly pushed down the price of the 780 and 980 (and 770/970), respectively, but at this juncture AMD has no answer to Nvidia's offerings above the 1060. This time around, I don't think the release of the 1080 Ti will result in a price drop on the 1080/70 unless AMD first releases its high-end Vega cards at competitive price points; conversely, if Vega releases later, I'd say the only hope of a price drop on the 1080 rests with AMD eating some of Nvidia's lunch. Essentially, where AMD manages to slot in Vega will determine whether Nvidia is proactive or reactive.

Took some days off to play this game. Doesnt look like we'll be getting a patch this week and even if we do my guts are telling me it wont improve much in the performance department. Damn it.

The performance issues are due -- chiefly, at least -- to the game flip-flopping between Low and Normal CPU priority. I imagine that'd be a relatively easy thing to fix and thus should be addressed in this week's patch.
 
The performance issues are due -- chiefly, at least -- to the game flip-flopping between Low and Normal CPU priority. I imagine that'd be a relatively easy thing to fix and thus should be addressed in this week's patch.

Are we sure about this? Using Process Lasso didn't really fix much for me.
 
The performance issues are due -- chiefly, at least -- to the game flip-flopping between Low and Normal CPU priority.

I haven't seen any quantifiable, non-anecdotal evidence to support that. This may be an issue on lower end systems, but on 970/1060 and up forcing priority to normal/high made no difference on my test machines or in other reports that I've read. People expecting a quick fix on performance might be disappointed; it seems likely (based on the quantifiable performance analysis reports that have surfaced) that there are at least a few fundamental problems in the graphics/engine architecture of Dishonored 2 that would be difficult to fix in half a week. I would recommend preparing yourself for something in between Horizon 3 and Arkham Knight in terms of fix potential/complexity if you don't want to sit at your PC refreshing gaf angrily ever half-hour.

Edit: To be fair, the Dishonored 2 team should have access to collaborate with the original engine designers (id) which might help speed things along if they've made some low-hanging-fruit mistakes/oversights that could be quickly identified. id has certainly demonstrated that they know how to take the core of that engine and optimize it very well, so that knowledge might help the turnaround time on fixes be shorter than Horizon 3 / Arkham Knight. Hopefully I'm wrong about the problem complexity and they just need to tweak some input parameters and swap a flag or two.
 
Are we sure about this? Using Process Lasso didn't really fix much for me.

I've not experimented with that fix myself, however someone reported earlier in the thread that the game still changed to Low priority despite forcing it to Normal with Lasso or some other similar program, which is why I didn't put in the OP.

Edit: Oh, apparently we're not sure.
 
Hoping the new drivers get DSR working properly. The texture work in this game blows my mind and all the AA options just seem to blur the overall image. I would love to downsample instead.

Downsampling works if you run the game in borderless windowed mode. I am personally using DSR 3840*1620->2560*1080, vsync disabled (gsync display) and everything else maxed. The downsampling does wonders to the game, especially how it fixes the ugly aliased gates and fences that are everywhere.

specs: 5820k@4.3, 16gb RAM, Titan X Pascal, installed on an ssd, win10
 
Yeah, Bethesda needs to get id's tech team over to Arkane to get that DOOM performance.

I know it's not that easy, but surely they can help to some extent.
 
Yeah, Bethesda needs to get id's tech team over to Arkane to get that DOOM performance.

I know it's not that easy, but surely they can help to some extent.

I'm not very technical so I might be wrong, but I read somewhere that Doom was made with the new idTech 6 whereas Dishonored was made with the somewhat older idTech 5 (which was modified into Void Engine). And from what I've heard, 5 and 6 are pretty different from each other in the sense that simply porting it over isn't easy (?).

Not sure if it's engine related or that id Software are just wizards, but seeing as how well Doom performed on PC I can't help but wonder how different Dishonored 2's launch could have been if it used idTech 6.
 
Really hate that it takes 3-4 minutes from launching the game to get to the main menu. That initial load (that I don't think I've ever seen a PC game do in a long long time) paired with the usual unskippable Bethesda logos is really stupid. I guess it's better than the 10 minutes it took when I first launched the game after it unlocked.
 
Really hate that it takes 3-4 minutes from launching the game to get to the main menu. That initial load (that I don't think I've ever seen a PC game do in a long long time) paired with the usual unskippable Bethesda logos is really stupid. I guess it's better than the 10 minutes it took when I first launched the game after it unlocked.

Game loads instantly for me (except for logos of course).

But I get exactly what you describe with Titanfall 2- takes minutes for the game to launch. I searched online and couldn't find anyone else with a similar issue.

No clue what causes it.
 
Game loads instantly for me (except for logos of course).

But I get exactly what you describe with Titanfall 2- takes minutes for the game to launch. I searched online and couldn't find anyone else with a similar issue.

No clue what causes it.

Do you not get a loading screen as soon as the game launches? It happens every time I launch the game. I thought it was installing something the first time it happened but it happens with every launch.
 
Really hate that it takes 3-4 minutes from launching the game to get to the main menuThat initial load (that I don't think I've ever seen a PC game do in a long long time) paired with the usual unskippable Bethesda logos is really stupid. I guess it's better than the 10 minutes it took when I first launched the game after it unlocked.

This happens to me every now and then. Sometimes it will load quick while other times it takes forever.
 
Do you not get a loading screen as soon as the game launches? It happens every time I launch the game. I thought it was installing something the first time it happened but it happens with every launch.

Ohhh, you are talking about the screen with Emily/Corvo and the progress bar?

I only get a long one on rare occasions- initial install and when I changed drivers. Every other time it takes about 3 seconds.
 
Top Bottom