Update (2023-10-19) by masterotaku
- geo-11 fix added.
- Fixed radial blur.
- Dynamic HUD depth for crosshairs, mission icons and similar relevant things. And fixed crashes related to this.
- Fixed water at any graphics setting.
- Correctly fixed underwater shadows and volumetric lighting.
- Fixed temporal antialiasing.
- Fixed motion blur.
- Fixed lighting clipping.
- And more things.
Update 02-03 ** THANKS TO masterotaku:
- Update fix due game update
- Fixed blood (99% perfect).
- Improved bloom lens flares (when bloom is enabled).
- Fixed lots of minor haloing problems.
- Fixed lots of things that needed to be stereoized.
- Much better fix for lighting clipping. If there is some of it left, it will be rare and minor.
- clouds and moon lighting
I want to says THANKS to bo3b, for putting a lot of hours in refactoring 3Dmigoto so this game and others can load 3Dmigoto so a fix was possible, many many thanks!
Fix:
- Shadows
- Lights
- Reflections
- Volumetric Lights (aprox. looks OK most of the time)
- Decals
- Lights Shaft and godrays
- HUD and Crosshair
TB and SBS Mode:
- The game support SBS/TB Mode using 3Dmigoto. Remove the ";" in the ;run = CustomShader3DVision2SBS in the [Present] section of the d3dx.ini. Default TB Mode. F11 to cycle.
Know Issues:
- In one particular lights there are still some culling. Is minor.
- Some clouds/myst during night is in 2D...i can fix it, but introduce a mayor haloing in the entire screen. I can't separate the texture and also texture overrides don't work. Is minor.
- One texture of the blood decal is cutted. The rest of the texture of the blood and all decals are OK.
- When you load in to the main screen for the first time, there is a black texture that is in 2D...if you load a savegame and then return to the main menu is fixed..LOL.. don't know what the hell happens here.
Settings:
- Use WATER QUALITY = LOW
- Disable DOF and Motion Blur
- Don't use Temporal AA
Important: avoid dynamic resolution. It messes up the dynamic crosshair depth.
Presets:
- "L" key to cycle Crosshair and HUD depth
- "K" key to toggle between gameplay and cinematic convergence
- "Xbox Left thumb + Right thumb" toggle between gameplay and cinematic convergence
Instructions:
- Extract where Dishonored2.exe is located (\Dishonored2)
- Start the game, when "Rundll32" prompt appear, press "Yes" (in Win10 this don't appear). This is for the Profile Override needed for this game. In Nvidia overlay you will see "3Dfix by DHR".
Download (geo-11 Fix by masterotaku)
Download (Old 3D Vision Fix by masterotaku)
Download Old fix
Screenshots
** Do you like the fix? **
If you like the fix, you can donate to this PAYPAL account: dhr.donation@gmail.com
Thanks!
- Update fix due game update
- Fixed blood (99% perfect).
- Improved bloom lens flares (when bloom is enabled).
- Fixed lots of minor haloing problems.
- Fixed lots of things that needed to be stereoized.
- Much better fix for lighting clipping. If there is some of it left, it will be rare and minor.
- clouds and moon lighting
- F1: convergence presets. By default the game profile uses 0.32.
- F2 (not in the geo-11 fix): HUD depth presets. By default screen depth. I prefer the fifth one, 0.92.
- F3: HUD toggle.
- F4: image sharpening toggle. Disabled by default in the geo-11 fix, and enabled in the old 3D Vision fix.
- F6: vignette toggle. Normal one disabled by default. Press once to disable crouching vignette. Press twice to reenable vignette. Three times to disable the main vignette again.
- F7: dirty screen effect toggle. Disabled by default.
I want to says THANKS to bo3b, for putting a lot of hours in refactoring 3Dmigoto so this game and others can load 3Dmigoto so a fix was possible, many many thanks!
Fix:
- Shadows
- Lights
- Reflections
- Volumetric Lights (aprox. looks OK most of the time)
- Decals
- Lights Shaft and godrays
- HUD and Crosshair
TB and SBS Mode:
- The game support SBS/TB Mode using 3Dmigoto. Remove the ";" in the ;run = CustomShader3DVision2SBS in the [Present] section of the d3dx.ini. Default TB Mode. F11 to cycle.
Know Issues:
- In one particular lights there are still some culling. Is minor.
- Some clouds/myst during night is in 2D...i can fix it, but introduce a mayor haloing in the entire screen. I can't separate the texture and also texture overrides don't work. Is minor.
- One texture of the blood decal is cutted. The rest of the texture of the blood and all decals are OK.
- When you load in to the main screen for the first time, there is a black texture that is in 2D...if you load a savegame and then return to the main menu is fixed..LOL.. don't know what the hell happens here.
Settings:
- Disable DOF and Motion Blur
- Don't use Temporal AA
Important: avoid dynamic resolution. It messes up the dynamic crosshair depth.
Presets:
- "L" key to cycle Crosshair and HUD depth
- "K" key to toggle between gameplay and cinematic convergence
- "Xbox Left thumb + Right thumb" toggle between gameplay and cinematic convergence
Instructions:
- Extract where Dishonored2.exe is located (\Dishonored2)
- Start the game, when "Rundll32" prompt appear, press "Yes" (in Win10 this don't appear). This is for the Profile Override needed for this game. In Nvidia overlay you will see "3Dfix by DHR".
Download (geo-11 Fix by masterotaku)
Download (Old 3D Vision Fix by masterotaku)
Download Old fix
Screenshots
** Do you like the fix? **
If you like the fix, you can donate to this PAYPAL account: dhr.donation@gmail.com
Thanks!
Thank you. I will donate.
ReplyDeleteLooks great, so happy to see all the work that went into this fix has paid off!
ReplyDeleteThanks a million DHR, working fine ! Worth waiting to play. Hoping the same for Mafia 3 ;-)
ReplyDeletethanks a lot. great fix. wow this game really needs some cpu and gpu power in 3d ;D time to upgrade.
ReplyDeleteOMG! Thanks a LOT!!! 🤓
ReplyDeleteWell sadly uninstalling dishonored 2, but keep the donation. I'll not play it due to the fact it forces me to update my windows 7, and with spectre meltdown measure system slowdown, I will not, thank you.
ReplyDeleteKeep creating fixes by all means, and I will support good games by donating to you for good measure, to support the cause of 3D vision and my entertainment. Thank you.
No, this will work on Win7, most of my time spent working on 3Dmigoto was for Win7 support. The only piece that is required is the PlatformUpdate, which is an optional Win7 update. Sometimes known as the 'evil update', although at this point it's no longer evil. It is required by the game, not by 3Dmigoto.
DeleteNo need to switch to Win10, and the PlatformUpdate is completely unrelated to that spectre stuff. You don't need spectre update for PlatformUpdate.
Its pretty easy to uninstall windows updates.
DeleteJust play game and then uninstall it.
https://www.ghacks.net/2014/12/11/how-to-remove-installed-windows-updates-and-block-them-afterwards/
I think you could even system restore.
I get a really dark image when switching to sbs. Any idea why please. Have had this with a couple of fixes lately! Thanks
Delete@Darren: Post a screenshot on 3dvisionlive.com for us to see. If the screenshot looks OK, that will determine if it's game/fix related, or something about your system.
DeleteNo known problems here.
Thank you, thank you and thank you for a 3D fix on this title! After a while I ventured into it and now I'm in owe of how beautiful this sequel of one of my favourite games is in 3D vision. God Bless you DHR, Bo3b and all donators.
DeleteThanks for your response Bo3b. Really appreciate what you guys are doing, in particular getting SBS working as an option now. Nothing quite like proper 3d Gaming. I was playing around last night and found a solution myself. If I Disable Full Screen Optimisations in the Shortcut under Compatibility settings it fixes the problem. Might help others experiencing the same issue. Im on Win10 64bit latest anniversary using a GTX970 with latest drivers. (I have experienced this with a few later driver revisions as well.) Basically, as I said, the problem was that the game just goes really dark when enabling 3d. With this fix its normal brightness. Weird I know.
ReplyDeleteVery helpful tip about the full screen optimisations, thank you.
DeleteHey bo3b I could use some slight assistance. I'm running sli 1080's and with the fix I get a stuttering mess. every time I just move. the GPU usage will also just drop to 0. I have been troubleshooting for an hour or so.
ReplyDeleteWith the wrapper uninstalled and all the settings setup it's completely fine. Run around pan fast no drops constant 60 FPS. reinstall the fix choppy cant play. Has me baffled. It's exactly the same with Death of the outsider.
One of the problems we saw for SLI setups is copying of textures across the SLI bus can become a bottleneck. The solution involves a complicated 3Dmigoto feature that downscales some textures and things like shadow depth maps to avoid the bottleneck.
DeleteAs a start, try setting the resolution lower, which will typically force the game to use smaller textures to start. See if that solves the choppy display. (may not be the texture problem.)
Sorry mate I have had no monitor it was a first gen 3D vision 2 sadly died.
ReplyDeleteReally?. Dont think I could hit 60 fps in 3D on one card.
I just tried it again I downsized the resolution from 1920x1080 to 1600x900 and it didn't do much.
Auto detect settings had everything on max I lowered just about everything. Only getting a max of high %60 GPU usage on lower settings also. I have uploaded a clip of just starting a game running around for a minute as you can see my framerates are dropping well under 120fps in 2d. when 3D is enabled with the fix I literally cant do anything as soon as I move my GPU usage will drop to like 0 and framerates go like 10 then back up to 60 then it repeats. I messed with just about every setting in NVidia control panel Vsync etc. the in game vsync tried all them options on/off. First game I have seen with these new features.
The video link I just put on my YouTube account. All stats on Riva tuner no bottlenecks going on.
¯\_(ツ)_/¯
https://youtu.be/2VuiPJxHieo
Thanks a lot.
Unfortunately when i use the mod with my 1060 'll get framedrops, the GPU load goes down to 0% and i got lags when i move around :( but the mod looks fantastic !
ReplyDeleteAre there any tips around what to do ? i have changed almost everything to "low" or "off" except for the full hd resolution. no change at all....
I run the game, I see the 3D Vision transmitter flash green, then it goes dim again and game exits. No messages no nothing, any idea?
ReplyDeleteJust tested this again, and it was working fine here. 3D is working without problems. I used 3D Fix Manager to install and launch the fix. Win10 1803, Driver 419.67.
DeleteIf game is crashing at launch, you will want to use uninstall.bat and remove the fix, then launch game to be sure it works, then reinstall fix. Or use 3DFM to uninstall, test 2D, then reinstall.
Hello Shackers!
ReplyDeleteWith this game I'm having an issue where 3D Vision hotkeys aren't working. Hotkeys for the fix are not recognized either (F1-F4, etc.).
If it is a driver issue or conflict, that's a bummer (I recently have been letting Fix Mgr handle the updating; I'm on Nvidia Graphics Driver 431.60). I'd rather not roll back for a handful of games, but for Dishonored 2 it may be worth doing.
I've had this 'no keys' thing happen to other games/fixes over the years, too. Is there a common solution for this? Otherwise, I'll roll back to 419.67 or 425.31 and report my results.
My pc is single GPU 1660Ti, with Ryzen 7 2700x, 16gb RAM, Win 10 Home.
How about that? I fired up 3D Fix Manager and it informed of a fix update for this game (I believe Fix Manager has benevolent druidic spirits living in the code ;-) ). At any rate, the update appears to have solved the 3D Vision hotkeys issue, but still no fix hotkeys for convergence (F1), etc. (I'll try rolling back the driver later and see).
DeleteI wonder too if there's something odd with this iteration of the game itself. It keeps losing my graphics settings, such as Water = LOW, rat shadows, etc. AND it won't keep y-look inverted.
Weird
I don't think the key settings not working is a driver problem, but maybe. Those are defined in the d3dx.ini. You might try changing them there. Could be conflicting with other software you've got running.
DeleteThe game itself has that stupid bug with losing settings at every launch. Blows my mind that they don't fix stuff like that, but if you google for it, you'll see a lot of people have the problem.
This comment has been removed by the author.
DeleteAs for losing settings, I've read this is a poor port, but seriously??
DeleteHey again 3 boobs ;-) tee hee....
DeleteWell, I believe the issue with 3D not starting was oversight on my part (which is usually the case). I'd just installed a new graphics driver via Fix Mgr. and after setting up 3D by the wizard, I thought I was good to go. However, depth was set to zero in Nvidia settings (nevermind why that my depth hot keys weren't functioning - I have those keys set to Alt+Shift+F4/F3). ALSO, I'd been trying to get the fix for "INSIDE" to work --> that fix is unusual in that it sets initial depth to zero. Regardless, once depth was upped, 3D is back. Go figure. Now if I can just get INSIDE to work O-<
Hi guys, I am stumped by the game crashing as soon as I get into the first bit of the tutorial, as soon as the text describing the mission on screen disappears. The game runs fine without the fix installed, but this crash happens if the fix is installed in both 3D and 2D(Ctrl+T). I've tried removing all system overclocks to test stability, but this had no effect on the crash. I've tried dropping the quality settings across the board, and of course keeping water detail at Low or Very Low. No help either.
ReplyDeleteAny help here would be appreciated, as I'm dying to play this game since loving the first one some years ago. Thanks
Just tested this again, and it was working fine here with Win10 1903, Driver 425.31.
DeleteTry uninstalling the fix, then launch the game and set resolution and game settings as you like, then install the fix. If that doesn't seem to work, do the usual stuff of verifying all game files, and maybe reinstall your driver.
I did get one game crash before reinstalling the fix, but I think that happened because of an out of date 3Dmigoto in my case.
Hi bo3b, thanks for your reply. I've done as you suggested and verified the files. No problem there. The game rungs without a hitch when running the game in 3D mode, without the fix. With the fix installed, both old and new, I get "micro stutter" as I run along and frames drop from 60 down to 30ish for a second or two, then back up to 60. This doesn't happen without the fix installed. Runs buttery smooth without the fix unfortunately, but it's visually unplayable.
DeleteI believe it's this micro stutter that is causing the crashes, which is caused by the fix being installed.
Just took a look and I'm not seeing nay frame rate problems. Something is different about your system. If you haven't done a DDU reinstall, you probably should. You haven't provided any details on your system or driver, so I'm not sure what else to suggest.
DeleteHi bo3b, I've now done a DDU reinstall, back to 4.25. Same crash, same place. I was originally on the latest driver which I use 3DFM to keep up-to-date with 3D vision installed.
DeleteMy system is as follows:
i5 8600K (5.1Ghz OC - stable)
2 x 1080 TI SLI (slight OC - stable)
Windows 10 1809
4K LG TV with Acer 3D vision(passive) EDID override.
This is super sad as I bought this game and the DLC and have been very excited to play it over the December holiday period.
Unfortunately it's definitely the fix causing the crashes as if I uninstall the fix, and play in 3D, I get no crashes and no stutter, but a very broken 3D game :(
OK, that combo should be good for sure. Maybe try doing a full uninstall of the game itself, delete the folder it was in, then reinstall from scratch. On rare occasions I've had broken games fixed by this.
DeleteAnother thing to try to narrow it down is to do the uninstall.bat of the full fix, then install just the 3Dmigoto 1.3.16 files, with no fix. That will tell us whether it's something with 3Dmigoto, or something with the fix itself.
Also be certain to delete every cached shaderfixes folder. There's one from steam, one from nvidia, and maybe one from 3Dmigoto. All those stale shaders can cause problems.
Be sure to not run *any* overlays. No Steam, no Afterburner, no Reshade, no other mods. These things are mostly OK nowadays, but have a lot of programming errors.
Since it's working fine in my case, it's likely we can narrow down something that will fix it for you.
I've narrowed the problem down to something in the d3dx.ini file. I started with the old fix which was working fine. Then I started adding all the files from the new fix into the relevant folders. Last file I added was d3dx.ini from new fix, and the crash happened again. Unfortunately, without the new d3dx.ini, some 3D is still broken, and I get some artefacts.
DeleteOK, good, what version of 3Dmigoto? I'm using 3D Fix Manager/HelixVision to install, and I let it update to latest 3Dmigoto of 1.3.16.
DeleteWith that in mind, I can experiment a bit and see if we can narrow it down. Would be worth commenting out some of the stuff in d3dx.ini to narrow it down. You can do a binary search (half in, half out) to make it faster.
BTW, would be worth doing an underclock of your system. Stable overclock doesn't really mean anything, because different games push the hardware different ways. When playing Deus Ex for example, I had to *underclock* my stock clock GPU, because it would crash in the same spot every time. Tickled some latent problem with the hardware that nothing else showed.
I've managed to find what is causing the crash. If I remove the below from the INI file, the game doesn't crash, but I lose the dynamic crosshair. Any ideas on how to try solve this dynamic crosshair problem?
Delete; ************** HUD CROSSHAIR ************************************
[ResourceDepthBuffer]
max_copies_per_frame=1
[ShaderOverride_HUD1]
Hash=89cf6c4deb412df4
vs-t110=ResourceDepthBuffer
disable_scissor=1
[ShaderOverride_HUD2]
Hash=9fcae2f032869439
vs-t110=ResourceDepthBuffer
disable_scissor=1
[ShaderOverride_HUD3]
Hash=cb8d27ccfc4c675b
vs-t110=ResourceDepthBuffer
disable_scissor=1
[ShaderOverrideMenu1]
Hash=ecbfae1499262fee
preset=Menu
[ShaderOverrideMenu2]
Hash=d6e73ff25189333d
preset=Menu
I've also just noticed that when I disable the dynamic HUD in the INI file using
Delete; Dynamic HUD. 0=disabled. 1=centered. 2=per vertex.
x3=0
- the micro stutter I mentioned also completely goes away, and also seems to stop the crash.
This comment has been removed by the author.
DeleteGreat work on narrowing it down. Thanks for posting back to let us know what worked for you.
DeleteThanks djgrege, I had the same problem and it starts on the boat when player starts to use HUD menus after taking runes and amulets
DeleteYeah I'm having issues like this, with the new fix the game crashes early on even in the tutorial when I reach the stealth part, also disabling DOF makes the game menus unreadable and I get stutters. Using the old fix makes the game fully playable with none of those issues and just reached Karnaka, so for now I'm sticking to the old fix.
ReplyDeleteAre you running an SLI setup by any chance?
DeleteSame here, old fix is working but new crashes almost immediately. Still trying to fix stuttering.
ReplyDeleteborderless fullscreen fixed stuttering.
DeleteAre you running an SLI setup by any chance?
DeleteI forgot to mention over here (I did in Discord) that I updated the fixes of this game and the expansion on 2020-02-13, with fully fixed volumetric lighting and a better handling of dynamic HUD to not distort menus and texts.
ReplyDeleteIf you experience crashes, it's because of the dynamic HUD. Something about getting the depth buffer from another shader makes it unstable for some people or some situations.
To fix that, comment or delete all lines in "d3dx.ini" that contain "ResourceDepthBuffer" (you'll find them in regex and Shaderoverride Blocks), and also the "max_copies_per_frame=1". The HUD will have static depth, however.
Hi, thanks for this awful fix!
ReplyDeleteI played the game about two years ago with the old fix (which I installed manually) and no problems. Now on my new playthrough I installed 3D Fix Manager and let that great tool do the needful and install the new fix. It then told me that the version of 3D Migoto was outdated and if I wanted it to upgrade to the latest version (it gave me some version numbers which I do not recall but I can try again this evening).
This is where the trouble began. Game was crashing every two minutes, just like before 3D Migoto had been refactured all those months ago. I tried this and that and re-installed everything, until I finally installed the old fix manually, launched the game via 3D Fix Manager, this time *not* upgrading the outdated 3D Migoto. And the crashes are gone!
I am not quite sure if this is the same with the new fix if I do not upgrade 3D Migoto. Will test this evening. Whatever, it seems that at some time, 3D Migoto new versions lost compatibility again with Dishonored 2.
OK, never mind and sorry for the confusion. It now seems to work using the 3D Fix Manager patch. Hope it stays so, otherwise I will come back ;)
DeleteThanks again for the fix!
Geo-11 bug report: Geo-11 0.6.6 works fine, however when I copied over 0.6.56 and set output to interlaced, it seems like the fix does not work. Lot's of halos and shadow issues.
ReplyDeleteUnlikely. Most likely- you overwrote the game fix d3dx.ini file, which will break the fix.
DeleteHi bo3b, I made sure not to overwrite the d3dx.ini file. Only made the change for "force_stereo=2"
DeleteHi again, sorry, I've just done a complete fix re-installed and copied over 0.6.56 and now it is working OK in interlaced. Not sure what happened earlier.
DeleteIt was a reshade filter *facepalm"
Deleteworks great with latest geo-11 combo
ReplyDeleteI had this same issue - the game would crash after a few seconds. This was actually related to the auto-crosshair. I had to disable it to remove the crashes. It only happened on my old hardware so it was a combo of certain hardware that caused the crashes. Check my comments further up in this post for how I worked around the crash. I believe I commented out any line in d3dx.ini that contained "=ResourceDepthBuffer"
ReplyDeleteNoticed an odd issue with the latest fix. The shadows on the weapons seems to be showing different in each eye on any convergence other than the default. However sometimes if I cycle through all the convergences then it is fixed, but not always.
ReplyDeleteActually it is on any convergence other than 0. Seems to be when the hand model is on the edge of a shadow projected onto the character hands that one eye shows the shadow and the other eye acts like the hand is out of shadows.
Delete