The above video goes away if you are a member and logged in, so log in now!
PAL to NTSC w/ 72 Offset
PAL to NTSC w/ 72 Offset –
Hello. I need to offset a particular game's y-fix to 72, but the PAL to NTSC program only goes up to 64. Does anyone have an idea how I can get it up to 72? Thanks.
136 installs , last on 16-NOV-2013
PS2 50002 PAL Silver
+ Network Adaptor + 500 Gig
Hitachi IDE + FMCB 1.8b
PS2 79002 PAL
Slim Unmodded FMCB 1.8b
black CFW 6.60 B10 PhotoFast 5400 with 2 x 8 Gig micro SDHC
If I read it correctly, that's an additional program to run before getting into HD Loader. So there's nothing that will edit the iso completely without the need for GSM each time?
Edit: I realized that I could compare the files in a hex editor to determine what values I should change for 72. I figured out the pattern by looking at the game with 32, 40, 48, 56, and 64 offsets. Unfortunately, while the game still booted, the screen positioning wasn't any different from an offset of 64.
PS2 NTSC mode allows 448 scanlines of video data to be visible, whereas PS2 PAL mode allows 512 scanlines of video data to be visible. So any Y-fix routine which simply selects which range of 448 scanlines from the PAL screen to make visible within the 448 physical scanlines of the active NTSC video mode can vary that choice only to 64 different settings. For this kind of method that is both the theoretical and practical limit.
Originally Posted by fshea31
And for all possible settings, some of the pixels of a PAL screen may always be lost from visibility, since it is impossible for NTSC mode to display the same number of scanlines which is the standard for PAL mode. The main reason why it still works well for many PAL games is simply that many of them do not use the full PAL range of scanlines, since they were designed for export to NTSC regions.
But when a PAL game does use the full 512 scanline screen height, then the display of that game in NTSC mode will always have to be a compromize, choosing which 64 scanlines should be lost from view. And this is inevitable, regardless of what tool you use for enforcing NTSC mode.
Best regards: dlanor
Thanks for the explanation, dlanor.
I just couldn't figure out why I couldn't shift it up any further. But now it makes sense. And as I mentioned in my GSM post, it was actually an offset of 96 that I needed, so it's really not feasible trying to play the game on an NTSC TV.