I’ve read that you have to adjust the sample phase when using this mode and find the sweet spot. I’ve tried every possible sample phase setting but there is always a small region of the screen that has some kind of fuzziness effect. Is this just incompatibility with my monitor?
I’m using NTSC Genesis. I played with the H.samplerate on 240p_L3M2 and it seems 427 does the trick. However it seems like 320×240 optimized mode cuts off part of the overscan on the right side. Any way to prevent that?
Edit: Seems like the H.active option is meant to address this, but I’m seeing discrepancies between the 240p test suite and actual gameplay with Generic 4:3 mode. In Generic 4:3 the full overscan in shown on the right, but in 320×240 optimized it will still get cut off even if I adjust the H.active value to make the overscan appear in the 240 test suite overscan test. You can also see this in the grid test by turning on the gray background.
If your display cannot handle the 348 multiple, then no. The reason you can see it in generic mode is because it uses a multiple of the pixel aspect corrected horizontal length, 390. (427*(32/35) = 390.4)
Personally, I see no reason for that area to be visible anyway.