Thread Rating:
  • 34 Vote(s) - 4.65 Average
  • 1
  • 2
  • 3
  • 4
  • 5
PCSX2 - Widescreen Game Patches
Global Defense Force (PAL)

[Image: th_pcsx2_2012_05_14_22_56_00_017.png]

[Image: th_pcsx2_2012_05_14_22_55_33_309.png]

[Image: th_pcsx2_2012_05_15_00_12_01_752.png]
Works in splitscreen as well.

I <3 this thread.
Was surprised how easy this was to do when i just followed the tutorials. Widescreen Helper made it even quicker.
This a 16:9 patch and it needs to be applied after you are in game as it will lead to a corrupt menu if you don't.


Attached Files
.pnach   DD35AC9F.pnach (Size: 284 bytes / Downloads: 815)
Reply

Sponsored links

Is it possible to do one for MGS2&3 by chance?

I'm just curious because this picture I put together of the game emulated at 4:3 vs 16:9 with the HDC shows that they don't look that different
http://i.minus.com/ibzbLoW4QB1p6G.png

It would help to maybe show that all the flaunting of "Redone textures" Bluepoint did was a bunch of *****.
*Shrug*
Reply
No.47's widescreen patches - Part II

This post is only used to store patches. For a list of all my patches and info take a look at the => main post <=.


Attached Files Thumbnail(s)
               

.pnach   07608CA2.pnach (Size: 110 bytes / Downloads: 714)
.pnach   D0B9C45F.pnach (Size: 151 bytes / Downloads: 565)
.pnach   3E2A42FA.pnach (Size: 160 bytes / Downloads: 434)
.pnach   81D233DC.pnach (Size: 124 bytes / Downloads: 673)
.pnach   FCD97245.pnach (Size: 98 bytes / Downloads: 624)
.pnach   38996035.pnach (Size: 161 bytes / Downloads: 711)
.pnach   0958556B.pnach (Size: 153 bytes / Downloads: 668)
.pnach   327053E8.pnach (Size: 138 bytes / Downloads: 656)
.pnach   12532F1C.pnach (Size: 214 bytes / Downloads: 650)
.pnach   45FE0CC4.pnach (Size: 166 bytes / Downloads: 692)
.pnach   9C71B59E.pnach (Size: 127 bytes / Downloads: 558)
.pnach   9BFBCD42.pnach (Size: 149 bytes / Downloads: 646)
.pnach   8CF7CBC0.pnach (Size: 150 bytes / Downloads: 612)
.pnach   0EF2C216.pnach (Size: 129 bytes / Downloads: 572)
.pnach   16E3BE78.pnach (Size: 141 bytes / Downloads: 570)
.pnach   CE4933D0.pnach (Size: 261 bytes / Downloads: 768)
.pnach   F00293CA.pnach (Size: 104 bytes / Downloads: 601)
Reply
Kind of offtopic but it looks like you can also mess with PS2's GS vmode to force a game being rendered nativelly in a desired video mode/resolution.
I was looking at SetGsCrt syscall and it looks like you can force your game being rendered (i'll repeat rendered, not a trick of line doubling and scalling) at a desired video mode:

0x02 = 480i
0x03 = 576i
0x50 = 480p
0x51 = 1080i
0x52 = 720p

I was messing with Tekken 4 that has a progressive scan mode so I could spot the value easier on memmory and when I forced it to 0x52 I saw up on the place PCSX2 shows the native resolution 1280x720! Doing that also made the game look less blurry than setting from GSdX at 1280x720! Also with that setting you don't need to set a deinterlace mode! Another experiment I did was I loaded SMS (It's a media player for PS2 for those who don't know) on PCSX2 via ELF loading and went on settings and startd to change video modes/resolutions and see what happens on the memmory. You should definitely take a look at this, it looks like if we understand how this works we could force 480p (or even 720p/1080i for less resource demanding games) on PS2 games without any trick like line doubling and magnification/scalling!
Reply
It is possible on real hardware for a long time. GSM (GS Mode Selector) is the homebrew that enables this. Google it for more info on the subject.

It is done via SetGsCrt as you said.

As you have already pointed out, it doesn't resize, it just line doubles the original resolution so it makes the picture blurry. The real usage lies in 480p mode. It makes GS omit the interlacing stage, so you get progressive picture plus 1 frame less delay on video.

It doesn't work with all games though.
Reply
(05-17-2012, 03:00 PM)reprep Wrote: It is possible on real hardware for a long time. GSM (GS Mode Selector) is the homebrew that enables this. Google it for more info on the subject.

It is done via SetGsCrt as you said.

As you have already pointed out, it doesn't resize, it just line doubles the original resolution so it makes the picture blurry. The real usage lies in 480p mode. It makes GS omit the interlacing stage, so you get progressive picture plus 1 frame less delay on video.

It doesn't work with all games though.
I am aware of GSMode but I think you didn't read what I said above correctly. You can force a rendering mode, no magnification, no line doubling, no blurryness, they are the modes that SMS homebrew uses that are on GS mostly for Linux.

EDIT:The bad thing that I understand is that it's not game universal, like the widescreen patches... :/
Reply
I think that's the same thing I used to get some info for the window title...
I used this as reference: http://users.neoscientists.org/~blue/ps2videomodes.txt
[Image: nbKSK.jpg]
Reply
I read it correctly. You are not forcing the game to render at a higher resolution. At least SetGsCrt doesn't do that. Feel free to prove me wrong.

Also here is a bonus mode from me 0x53 = 576p. It is only possible for BIOS versions above 2.20

Those linux modes you say SMS use are the same modes GSM use. Both are done by SetGsCrt.
Reply
(05-17-2012, 03:36 PM)reprep Wrote: I read it correctly. You are not forcing the game to render at a higher resolution. At least SetGsCrt doesn't do that. Feel free to prove me wrong.

Also here is a bonus mode from me 0x53 = 576p. It is only possible for BIOS versions above 2.20
I don't try to prove you wrong or something. Till today I thought the same about forcing a resolution on PS2, it results into what GSMode does but it looks like there is something else which is game depended that could force a game render at the desired resolution. I had checked the native resolution on GSdX on Tekken 4 which is 640x448 and then forced a 0x52 video mode on PCSX2. This resulted into PCSX2 showing 1280x720 on the resolution space in the window while I still had checked the native resolution on GSdX. I went on and took some screen caps to make a comparison of 640x448i vs 640x448p vs 1280x720p (using the 0x52 hack) vs 1280x720p (by chosing that resolution on GSdX window). The results were intresting, 640x448p looked better than 640x448i. Now, 640x448p vs 1280x720p (using the 0x52 hack) looked worse so the hack really did something more than line doubling+magnification on the game so I had to check using the next test. Finally, both 720p snaps with and without the hack looked identical or atleast 95% identical. I tried to do exactly the same on SMS media player and it rendered instead a native 1216x676 on 0x52 mode. This was no way a 480i image magnified to 720p, you can test it your own. So my point is that there is something (undocumented?) that sets the behaviour of GS on how to handle vmodes that by default are set on line doubling+magnification when is done using the SetGsCrt syscall but when are used by RAM hacking they use the settings of the last used rendering resolution.
Reply
I think i see your point. It should of course be possible to force the game render the graphics with a higher resolution. All i am saying is SetGsCrt doesn't do that. But it might be possible via RAM hacking as you say..

You are playing a video with resolution below 640 x 480p on SMS right? Because SMS can play videos up to 720p and they will of course look better if you set the VMODE to 720p via a SetGsCrt syscall.

About the hack you say, any chance of giving raw memory addresses for a specific game? I will try on both PCSX2 and original PS2 for comparison.
Reply




Users browsing this thread: 14 Guest(s)