March 9, 2017 at 9:31 AM #11713
I have a Taito F3 arcade board that I’m hooking up to the OSSC (firmware 0.76) through SCART with a Home Arcade System (HAS) SuperGun V3. My other arcade boards work fine with this setup, but the Taito board refuses to sync. However, the Taito does sync with my Framemeister. I’ve posted a screenshot of the FM input Status screen below, but first here’s a list of different things I’ve tried:
1) Switched Sync Cleaner off and on.
2) Switched the HAS Sync Generation jumper between all three possible settings (buffered, regenerated, unprocessed).
Here’s a link to a screenshot of the Input Status on the FM:
And here’s a link to the HAS’s manual that discusses its Sync settings:
Any suggestions on how I can get this to work on the OSSC?March 9, 2017 at 7:56 PM #11718
What’s the OSSC saying on its LCD when you connect the board and what does the info screen say when you press the info button on the remote?March 9, 2017 at 11:01 PM #11724
If I recall correctly those Taito boards used very long hsync pulse which was interpreted as vsync unless “Vsync threshold” (in sync menu) was significantly increased.March 10, 2017 at 3:55 AM #11730
OK, if I crank the Vsync Threshold up to its maximum value of 30.76, the board ALMOST syncs-it flickers back and forth between sync and no sync.
When I push Info on the remote, the display flickers between 260p, 15.42kHz, 59.34Hz and 261p, 15.42kHz, 59.11Hz.
Thoughts?March 10, 2017 at 11:00 AM #11734
The wiki says “Games running on this PCB use 240p with odd field signal modes. To ensure the game works correctly, select the correct input on the OSSC before starting up the game and do not change it during game play.”
Hardware like this has caused quite a number of headaches it seems. You could try connecting another source to a different input and switching to that then back to the F3. A bit of a kludge workaround but it has worked for me in the past.March 22, 2017 at 12:33 AM #11948
It took me a week to get around to testing this again, but I can confirm that switching inputs back and forth doesn’t seem to make a difference with allowing the OSSC to “lock” onto the Taito F3 board’s signal, with my setup at least.
I’ve also tested various other arcade boards, and my other Taito boards are troublemakers as well – my Rastan and Heavy Unit boards both have similar syncing issues that the F3 does with the OSSC, but they all work perfectly with the Framemeister.
I know that there’s a lot of arcade boards out there and many of them put out unusual signals, so I don’t mind using my Framemeister for the Taito boards. It’s just a pity because on my other non-Taito arcade boards, the OSSC looks noticeably nicer.
I don’t know if it’s possible to allow for a greater Vsync Threshold than 30.76 in a future firmware, but if it is, I suspect that would get the Taito boards to sync because they’re SO CLOSE to working at 30.76. Please let me know if there’s anything else I should try.
March 22, 2017 at 12:35 PM #11954
- This reply was modified 1 month ago by ShootTheCore.
Hmm, I know it’s a major hassle but could you try some of the older firmwares too? These reports of changing behaviour with systems that sue the odd field signals really needs nailing down.March 22, 2017 at 3:48 PM #11964
Sure, I can do that. Which specific older firmwares should I try?March 24, 2017 at 12:28 AM #11996
That’s a good question…let’s go back all the way to 0.69!March 28, 2017 at 7:15 PM #12073
I tested a F3 board with 0.5x firmware back in 2015. I’ll try getting a F3 for testing with the latest fw, but it might take some time.
You must be logged in to reply to this topic.