Closed 987123879113 closed 2 years ago
Notes so I don't redo work: Bug does not exist 95cb7968f30c2f9b6a15a917b4df77875832cee3 March 1st Bug does not exist 67e83a647d024316ac017c9ec939a746480e7962 April 3rd Bug does not exist 211472e2d3cab33478b4ba754645312bf40209a0 April 14th Bug does not exist 133f40c099535f609351e85afe349f2113105b4f April 15th Bug exists e96e75673ed4419f770383032cedf0a11dc2c38a April 16th Bug exists f7946f90685e3ca3fbbaa3a67dc36530f63fc1e2 April 16th Bug exists 12052536354461f64a3f8ab8fecb6d14110c4401 April 18th Bug exists c24ecdcdf89a0d535911647561515d42730753da May 8th
Looks like this is the PR that broke things. https://github.com/PCSX2/pcsx2/pull/5810
Enabling "Screen offsets" as mentioned in the PR makes things look worse, cutting off all sides now (except maybe the right?):
Enabling "Show overscan" fixes the issue as long as "Screen offsets" is off:
Enabling "Screen offsets" and "Show overscan" is a mess + the bottom is still cut off:
Before the PR, the showed that it is rendering at 640x478. After the PR it shows it is rendering at 640x448.
With the 31kHz flag on the P2IO set, the game will boot in 640x480. "Show overscan" has no effect on the screen in that mode. 640x480, show overscan disabled:
640x480, show overscan enabled:
640x480, screen offsets enabled + show overscan disabled:
640x480, screen offsets enabled + show overscan enabled:
Not really qualified to say what code exactly is right or wrong, but show overscan always being enabled + screen offsets always being disabled seems to always be the best configuration for Python 2 games. Will update setup guide and troubleshooting guide with this info.
A few months back something changed in upstream in the graphics emulation code that causes the video to be cropped differently. Should go back and try to pinpoint what it was exactly and revert that change specifically.
Screenshots were made using the internal screenshot tool/F8.
Correct (taken using 133f40c):
Broken: