PAL overscan dimensions

This is an archive of a topic from NESdev BBS, taken in mid-October 2019 before a server upgrade.
View original topic
PAL overscan dimensions
by on (#183643)
According to book, I am Error:

"On NTSC sets, up to eight pixels of the upper and lower borders of the PPU’s output are lost to overscan,
reducing its visible scanline count to 224. PAL sets lose a single upper scanline and two pixels on the left and right."

I have yet to find an emulator where the default overscan for PAL drops 2 columns of pixels on the left and right. Are the dimensions in that quote correct?

Edit: The wiki seems to suggest the same. I'm not sure why emulators are not doing this.
Re: PAL overscan dimensions
by on (#183644)
Because we only consciously noticed it in the past couple years, and puNES is the only first-class emulator to have seen significant development effort in that time.
Re: PAL overscan dimensions
by on (#183645)
lidnariq wrote:
Because we only consciously noticed it in the past couple years, and puNES is the only first-class emulator to have seen significant development effort in that time.


To that end, I just checked the puNES 0.100 overscan settings. The defaults appear to be 8 for up, down and left and 9 for right for both NTSC and PAL as far as I can tell.
Re: PAL overscan dimensions
by on (#183646)
I only said that puNES is the only emulator that's been being developed at the right time for it to even be known as a difference on PAL sets.