You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I understood the source correctly, the tool replaces the 0x55 0x55 0x15 0x40 sequence by the one matching the desired resolution.
However I would like to know (and maybe it's good to document) the significance of 0x55 0x55 0x15 0x40 or how or where you found it.
I'm wondering in particular because the page I linked suggests replacing a sequence in the Witcher 3 executable file too using a hex editor, but suggests replacing the sequence 0x39 0x8E 0xE3 0x3F. So it's a bit curious to me why both would seem to work...
The text was updated successfully, but these errors were encountered:
I found some similar guide to do the hexedit stuff back in the day. After redoing (and re-googling) it 5 times I decided to do this little script for it, to save time for myself and others. I didn't find the original source of the patch, or any explanation on why it works.
Good idea to document it. If anyone can find some place with an explanation, please tell. Bit shocked they don't have native support yet. Maybe in the next-gen version...
I was looking how to get The Witcher 3 to show properly use my ultrawide resolution in cinematics. I found both your tool and this page: https://vulkk.com/2021/06/27/how-to-fix-witcher-3-ultrawide-cutscenes-no-black-bars/
If I understood the source correctly, the tool replaces the
0x55 0x55 0x15 0x40
sequence by the one matching the desired resolution.However I would like to know (and maybe it's good to document) the significance of
0x55 0x55 0x15 0x40
or how or where you found it.I'm wondering in particular because the page I linked suggests replacing a sequence in the Witcher 3 executable file too using a hex editor, but suggests replacing the sequence
0x39 0x8E 0xE3 0x3F
. So it's a bit curious to me why both would seem to work...The text was updated successfully, but these errors were encountered: