marqs
Forum Replies Created
-
AuthorPosts
-
I also had a chance to probe the PSOne I mentioned, and in that case video & sync issues were caused by a bad 220uF cap on the PCB behind AV connector. Not sure if this is a widespread issue amon PSOnes, but if you have multimeter with cap tester function, it’s very easy to test it.
Is the linked switch perhaps using logic switches instead of analog multiplexers? Or maybe it’s mechanical if there is no power supply. If you have original AV cables for some of the consoles and RCA-scart adapter, you can try connecting that to AV1 and see if stable sync is at detected (picture is then blank).
It’s a known issue that has been fixed and will be part of 0.83 which is released soon.
July 23, 2026 at 8:14 PM in reply to: Request: Better support for MiSTer ao486 core in Direct Video mode #70240It looks like the core may not properly support direct video. Connected directly to my monitor or via HDMI->VGA converter to Pro produces no stable sync.
The garbage issue is now fixed and will be effective from fw v0.83. The issue with GB core seems to be that it indicates incorrect pixel repetition factor (2x instead of 5x) when menu is open.
The signal goes to U1 pin 2. I’d try reflowing that part and then scope if the signal is visible on the pin.
Can you try lower than Line5x? Some units have had these kind of issues when pushed close to the performance limit. There are some improvements on later firmwares but they are not compatible with vanilla v1.6 board.
If you have the original AV cable, you can try connecting composite lead into the green (Y) jack to see if you get stable B/W picture via AV2 YPbPr input. That could then rule out if the SCART cable is causing the issues.
Can you share link to the settings you’re using? Also is that 50 or 60Hz A1200?
I’ve seen one such PSOne that had curling with a 100Hz digital-enhanced CRT it was connected to so maybe the sync signal is different to earlier models. I should have a chance to try that unit with OSSC within the next few weeks to see if it results to similar sync issues and if there’s a simple fix (usually these kind of cases have got solved via increase of coast).
Only the firmware version is relevant, not the HW revision (assuming <1.8 is modified to support latest fw). My guess that the problem lies with the video ADC which may semi-consistently fail lock into certain signals which is not so easy to detect & fix. You could try enabling “Full VSYNC bypass” from compatibility menu which was added to address somewhat similar issue with MDA cards.
Actually if you get sync via AV2, then it already indicates the fault is with U1, or C103. If you have good luck, then it’s the latter or just a weak solder joint on U1 pin 2.
What board and firmware version you have? Also what does the front character display say and is the red LED on or off?
Since you mentioned you have a scope, can you scope output on U17A pin 19 (or from C11 pin facing it) with PS2 source? You should see same periodic sync / Y as from U17A input (pin 2). That should reveal whether the issue is with U17A or U1.
-
AuthorPosts
