Auto progressive scan?
#11
yes, you need to compile choosing the debug version in the configuration manager. takes shorter time to compile then the release builds.
Reply

Sponsored links

#12
Took me some time to figure it out but I think I got it.


Attached Files
.txt   emuLog.txt (Size: 41,18 KB / Downloads: 231)
Reply
#13
It's only using interlaced mode.

Code:
Set GS CRTC configuration. Interlace Interlaced. Field Type FIELD. Mode NTSC 640x448 @ 59.940 (59.82)

there should probably be a new log message if it switches to Progressive , detection on GS Frame is probably wrong then... ( did it mention progressive on the GS frame at your recent test when emulog was generated ? )
Reply
#14
(12-10-2015, 06:34 PM)ssakash Wrote: It's only using interlaced mode.

Code:
Set GS CRTC configuration. Interlace Interlaced. Field Type FIELD. Mode NTSC 640x448 @ 59.940 (59.82)

there should probably be a new log message if it switches to Progressive , detection on GS Frame is probably wrong then... ( did it mention progressive on the GS frame at your recent test when emulog was generated ? )

Yes it did mention progressive.
Reply
#15
I'll look into the GS frame video mode detection when I get some free time, Thanks for reporting.
Reply
#16
Well, the progressive mode is sort of a lie. It certainly fooled me. Tongue

See https://github.com/PCSX2/pcsx2/commit/45...0355e9ee34
Reply
#17
should be fixed on the latest development builds as of 0f1fec4 , Thanks for reporting.

(12-10-2015, 08:38 PM)turtleli Wrote: Well, the progressive mode is sort of a lie. It certainly fooled me. Tongue

See https://github.com/PCSX2/pcsx2/commit/45...0355e9ee34

also fooled me for quite a while Tongue2
Reply




Users browsing this thread: 1 Guest(s)