Open bodgit opened 3 years ago
I can only tell that it struggles to separate VSync. There's no good fix that I can point to at this time, but if you search through older issues, maybe you can find something.
I did some enquiring on an arcade forum and apparently the M72 outputs 256 vertical pixels as opposed to the normal 240/224. Would that be the reason it's not locking onto the sync signal? If so, can the software be updated to handle that or does the hardware fundamentally not support such a signal?
It's more about the format of the CSync (combined HS + VS) that some arcade boards produce. There can be some quirks to it that are just hard to deal with. A software update might be able to fix this board, but it might break some others..
Would it help to capture the sync signal on an oscilloscope?
I presume you don't care too much about all of the hsync pulses in the middle of the screen, it's the vsync pulse at the bottom/top of the screen that is the troublesome area?
I think I managed to capture it: From my limited understanding of csync I was expecting to see inverted hsync pulses during the vsync so I hooked up my CPS2 which works fine: That doesn't have them either, but I notice the vsync pulse is about half as wide as the M72, (the BX-AX value). Finally I tried my MVS which also works: That does have the hsync pulses, and the vsync pulse is about the same duration as the CPS2. Does that help at all?
I've successfully used a GBS-C with a number of arcade boards, (Capcom CPS-I/II/III, MVS MV1B, etc.), but I've tried to use it today with an Irem M72 board and the GBS-C refuses to find a stable sync signal. It correctly detects the RGBS input and I briefly see the LED on the ESP board flash (it normally stays on when a signal is detected) but then it stays off. Based on other bug reports here I enabled the "Print Infos" option and captured some of the log. I'm not sure how to interpret the output but I'm hoping it makes sense to you:
I have managed once by fluke to get some sort of picture however it was very unstable with a lot of tearing and then I think the code watching the sync line kicked in, tweaked the settings slightly, and I lost the picture again.
Any ideas?