PCSX2 - Widescreen Game Patches

[pentel]

True, but maybe he wants proper "hor+" widescreen modes. Unfortunately the GoW games are "vert-", at least the first one. The second one is something between hor+ and vert- I think...

Yeah, that's right, to cover those horizontal black bars, GoW 1 only has vertical WS support.

[strider3871]

Hi Guys,

is MGS3: Subsistence (PAL-E) patchable into 16:9 mode?

I tried to look for the patch but nobody seems to have it. Could anyone help?

[No.47]

Hi Guys,

is MGS3: Subsistence (PAL-E) patchable into 16:9 mode?

I tried to look for the patch but nobody seems to have it. Could anyone help?

It certainly is patchable. You can find the patches for MGS3 - Snake Eater (NTSC-J) and MGS3 - Subsistence (NTSC-U) in this thread, so porting over to the PAL version should be very easy.

Hint: Just search for the value 3F800000 around 202xxxxx. You will find the variables to change the horizontal FOV and the vertical FOV. Override the first one with 3F400000 and it's done.
(If you don't find them simply search a wider area.)

EDIT: Don't forget to post the values here afterwards

[strider3871]

It certainly is patchable. You can find the patches for MGS3 - Snake Eater (NTSC-J) and MGS3 - Subsistence (NTSC-U) in this thread, so porting over to the PAL version should be very easy.

Hint: Just search for the value 3F800000 around 202xxxxx. You will find the variables to change the horizontal FOV and the vertical FOV. Override the first one with 3F400000 and it's done.
(If you don't find them simply search a wider area.)

EDIT: Don't forget to post the values here afterwards

Thanks for the quick reply btw
Could you be a bit more step by step? I am a bit lost. I read Hyakki's post on WSH and the way I see it (after trying to run the program) is that the program scans automatically, so I am kinda confused on how to set it to look for specific range of values? I know that there are fields that you can change (e.g.: search for and replace), but when I tried to key in the number that you mentioned, the screen just turned opaque green

[No.47]

Thanks for the quick reply btw
Could you be a bit more step by step? I am a bit lost. I read Hyakki's post on WSH and the way I see it (after trying to run the program) is that the program scans automatically, so I am kinda confused on how to set it to look for specific range of values? I know that there are fields that you can change (e.g.: search for and replace), but when I tried to key in the number that you mentioned, the screen just turned opaque green

If you click on your memory range selection ("2xxx" written in blue color) you can set which range you want to search exactly. Choose "Find 3f800000" and "Replace 3f400000". You should now see that the FOV in the game changes. In the Log window you see all adresses that are possible candidates. Cut down the scanned range to find the right one, alternatively copy the whole list into a pnach patch file and use that (you need to choose "enable cheats" in PCSX2 then) to sort out the useless adresses.

You can also use Cheat Engine instead of the Widescreen Helper. See the great guide written by synce here. But you don't need to, in case of MGS3 the Widescreen Helper gets the job done easily.

[strider3871]

If you click on your memory range selection ("2xxx" written in blue color) you can set which range you want to search exactly. Choose "Find 3f800000" and "Replace 3f400000". You should now see that the FOV in the game changes. In the Log window you see all adresses that are possible candidates. Cut down the scanned range to find the right one, alternatively copy the whole list into a pnach patch file and use that (you need to choose "enable cheats" in PCSX2 then) to sort out the useless adresses.

You can also use Cheat Engine instead of the Widescreen Helper. See the great guide written by synce here. But you don't need to, in case of MGS3 the Widescreen Helper gets the job done easily.

LOL your info gave me something new at least I had no idea that 2xxx (in blue colour) can be set to specific range of values
Anyway... I tried your suggestion and this happened: the screen zoomed in to the character and then immediately turned green (the whole screen). Now the way I understand it, the most common val to store screen ratio is either 3F800000 or 3F400000 (so either one of those has to be keyed into the "search" field, correct?) But how do you know the what value to key in the "replace"?

[No.47]

As I wrote: Choose "Find 3f800000" and "Replace 3f400000".
3f800000 = 1 needs to be replaced with 3f400000 = 0.75 to get a proper widescreen ratio (0.75 = 1 x 0.75) in case of MGS3.

If the screen turns green or freezes or whatever you need to sort out the responsible adresses first. Otherwise you won't find the adress responsible for the horizontal FOV.

For MGS3 - Subsistence (NTSC-U) the correct adress is 202050AC, so you could also try this first. I suppose it's not exactly the same for the PAL version but somewhere near.

[strider3871]

As I wrote: Choose "Find 3f800000" and "Replace 3f400000".
3f800000 = 1 needs to be replaced with 3f400000 = 0.75 to get a proper widescreen ratio (0.75 = 1 x 0.75) in case of MGS3.

If the screen turns green or freezes or whatever you need to sort out the responsible adresses first. Otherwise you won't find the adress responsible for the horizontal FOV.

For MGS3 - Subsistence (NTSC-U) the correct adress is 202050AC, so you could also try this first. I suppose it's not exactly the same for the PAL version but somewhere near.

OK, got a chunk of values on my list here Looks like I'm gonna have to try one by one to narrow it down to the correct value. Thanks for your suggestion, wish me luck I'll post the result if I get a good result

[No.47]

Don't try them one by one, use interval bisection.
Override all addresses in the first half of your list of candidates and check if the FOV has changed. If it has you know the address responsible for the FOV lies in the first half and the second can be scrapped, if not it lies in the second half and the first can be scrapped. Continue by examining one half of the remaining addresses and scrapping the useless one, until you find the address/es (only one in case of MGS3) responsible for the horizontal FOV.
By using this method you should find the address pretty quickly.

[strider3871]

Don't try them one by one, use interval bisection.
Override all addresses in the first half of your list of candidates and check if the FOV has changed. If it has you know the address responsible for the FOV lies in the first half and the second can be scrapped, if not it lies in the second half and the first can be scrapped. Continue by examining one half of the remaining addresses and scrapping the useless one, until you find the address/es (only one in case of MGS3) responsible for the horizontal FOV.
By using this method you should find the address pretty quickly.

ok... here's what happened: (during running WSH)
1) The screen zoomed in very close to the char
2) a few sec later the screen zoomed out to the grass surrounding the char
3) The Screen finally went green (waited a few sec after and still green)
4) Did not see the screen went 16:9 at all, so stopped WSH
5) I figured out the garbage caused by the 2nd half of the list, discarded everything on the 2nd half
6) On the first half narrowed it down to some values and finally down to this:
patch=1,EE,202055F4,extended,3F400000 // 3F800000

7) Still no change to 16:9 , did I do something wrong?

Sorry to disappoint will read how to use the other program that you mentioned