I am so confused as to how someone managed to get the widescreen stuff working for Hitman 2, it's so frustrating.
Topic on Talk:Hitman 2: Silent Assassin
Wasn't there even another solution?
I honestly don't know.
What is the issue exactly?
Sidenote: I've written a simple program that allows for easy byte replacement (basically same rule as UniWS). Hopefully if I can figure out the whole deal with Hitman 2, I'd publish it.
I have no idea what this guy did. http://archive.hitmanforum.com/index.php/topic/59059-true-hitman-full-hd-quadrilogy-for-pc/
As in, what does this achieve? http://i.imgur.com/9lex85F.png http://i.imgur.com/gZysR1W.png
Actually maybe I should just keep fiddling around for a while longer, I just realized that in order to find the adress I wanted to I simply had to use Go To instead of Find... duh...
-Actually I knew this-
Adjusting RenderD3D.dll, hitman2.exe, config.exe for resolution is pretty straightforward once you have this table
What I still miss is how the change D8F189411CC7412C0000803F8941308941348941
to D8F189411CC7412CAAAABA3F8941308941348941
would represent a FoV of 91°. Not to mention the other two tweaks.
I already knew that's the FOV, but I don't know how to translate it into Decimal.
D8F189411CC7412C0000803F894130894134894
It's actually a float value representing 1.0. Here: http://www.h-schmidt.net/FloatConverter/IEEE754.html
You get: 0x3f800000. Reverse the order to get Little Endian - > 0x0000803F.
So it's probably some multiplier that affects the FOV. The guy changed it to 1.4583333 ;)
Question is how to find it in GOG file.
Ah, 8 bits. I didn't realize that's what I had to look for.
Assuming there weren't any upgrades since GOG version was uploaded to TPB -> address: 00001779 (no, I'm not going to buy like a 3rd copy of H2SA, thank you very much).
Still, causes pretty major graphical glitches :/
-- EDIT -- OK, so I seem to somewhat be able to fix the issues, but that's using CheatEngine. It'd be nice to be able to do that using hex editing.
Mhh, I don't know if you noticed GOG executable is packed.
See the other discussion in this talk page
I missed that, but it doesn't matter much, as it doesn't seem to be related to FOV values.
I honestly don't know.