Talk:Dishonored 2

Any reason the page is still marked as a "stub" - it's released, we have some fixes... right?

I wouldn't quite call it a "stub" any more, but I believe the stuff in the Availability section (at the top) is usually filled out, but nobody got around to do it for this one yet. I think then it would be time to remove the Stub header.

I'm sorry that I didn't think of this earlier, it's the first time that I encounter such a situation, so I just made the counter-edit that I regarded right. Additionally, the other guy's edit was an improvement (no YouTube video instructions required), but so was my counter-edit, because it contains the instructions in text now. So it's not entirely a back-and-forth. Here are the edits in question, so let's talk about this if necessary:

19:18, 14 November 2016‎ God - owner of the Universe . . (8,344 bytes) (+91)‎ . . (→‎Video settings: Figured out how to use the damn FOV camera DLL. Just spit a HowTo YouTube URL in there for now.)

22:43, 14 November 2016‎ ..........

18:55, 15 November 2016‎ 24.67.29.101 . . (8,024 bytes) (-58)‎ . . (→‎Video settings: assuming this is a bit easier)

04:10, 16 November 2016‎ ..........

04:12, 16 November 2016‎ ..........

05:34, 16 November 2016‎ God - owner of the Universe . . (9,014 bytes) (+186)‎ . . (→‎Video settings: I reject unknown person 24.67.29.101's assumption that EI "is a bit easier". 17/56 vs 13/57 VirusTotal hits = more user issues on average (?ban probability?). Also, Swiss army knife "CE" should be known&had, why spam users with tools?)

.................

Actually, in the heat of the moment, I checked an old version of the Cheat Engine setup (CheatEngine651.exe), not the current one (CheatEngine66.exe) which has been out since October 6th and has only 8/56 VirusTotal hits. The Extreme Injector version I checked was the current one (v3.6), though. No idea when it was released.

.................

Since there hasn't been a reaction in a week, I consider the matter closed and will continue editing that part of the article.

I accidentally started this discussion via a discussion page header edit and now moved that whole text (effectively 3 comments) into this one comment.

.............................................

The logo movies can't be skipped or aborted, and they can not be renamed to make the game just skip past them like many games (e.g. Dishonored 1) did it. They are here:

[STEAMPATH]\steamapps\common\Dishonored2\base\video

These are the videos:

arkbeth.bk2

legal.bk2

warning.bk2

void.bk2

"void" is the shortest movie, and it does work to replace the other clips with this one. (Keep backups, of course.) But the improvement is marginal, and hearing/seeing the same clip 4 times is a downside by itself, so basically no change here is the best course. (matter of taste decision)

Maybe it is possible to alter the movie files themselves, but I had no luck so far: Cut off void.bk2 starting 0x2000, but the game did the same it did when the file was renamed: Black screen, frozen.

I've replaces the video files with a .5 second black video, this works perfectly. here is a link
Feel free to use these files for other purposes and make them available on the main page.
EDIT: Seems like someone else had the same idea as me. disregard this post.
--Arnex02 (talk) 09:15, 11 November 2016 (UTC)

Thanks, Arnex02, I've tried the videos. They are a second each (even according to Radtools),
so there's 4 seconds of blackness, kinda the same thing we get when renaming the videos and DH2
just freezes - except it doesn't and eventually moves on. I'm saying that while a bit of blackness
sounds like the right choice, in practice it doesn't seem to be ideal. I've tried to reduce your
blackness video to just a few frames, but oddly, the game still stays in blackness for a long time
(yep, with all 4 videos replaced with one that doesn't take 1/10th of a second). Then I looked at
my "Arkane Studios" replacement variant again and realized that when the video is played for the
4th (=last) time, it lasts longer: Apparently the game takes some time, anyway (probably being active
in the background). Therefore, I think that the current "Arkane Studios" solution is best: Even the
short blockiness of the first frames is good, because then the user can see that all 4 videos are played.
--God - owner of the Universe (talk) 09:15, 12 November 2016 (UTC)

.............................................

Editing the FOV (or any of those settings, really) doesn't appear to work because there's rudimentary version checking done with the default.cfg file located in the Dishonored 2 game directory that seems to be explicitly trying to prevent the INI/cfg hacking possible in Dishonored 1.

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.

Gotcha. Good theory on the sanitizing/normalizing of values.

I've got no experience with CE.

FOV-question is kind of solved.

http://pcgamingwiki.com/wiki/Dishonored_2#Video_settings

Downsides: 1) Have to inject the DLL on every start. 2) Have to adjust the FOV again after every savegame load.