Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.


Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

Topic on Talk:Dishonored 2

I don't think it's version checking, because I had some weird problem due to my 4K desktop (but DH2 at 1920x1080) - I could not switch back from WindowedFullscreen to Fullscreen, the game would not be visible, instead I'd see the desktop, and even playing around with the keyboard didn't help confirm the choice. Anyway: I then just changed the fullscreen mode in dishonored2Config.cfg (with the game closed, of course) and that worked just as expected.


What's going on, I believe, is that the values (At least some, among which ark_fieldOfView.) are sanitized when read into the program. This is the part that really sucks, because it's kinda ok when developers restrict their testing (e.g. see-through-walls, which is a possible glitch with high FOV) to a certain FOV range, but they should at least leave the backdoor open. They didn't do that here. Oddly, in DX:MD they also didn't - both games have Denuvo. I wonder if it's a coincidence.


Through "Which value did('nt) change?" searching with Cheat Engine, I found some addresses relating to FOV. E.g. when I changed one of them, the FOV in the game would fade higher and higher and then stop at like 170° (but it's not a proper value address, rather code, so no luck). In DX:MD, FOV change via Cheat Engine is possible, I did it from day one through all patches with the same CE script (Not mine. Found on PCGW.), and I'm convinced it's possible in DH2, too. We just need to get the CE-capable guys working on this. K-putt on Steam doesn't have DH2 or I'd have asked him already.