Good choice.XtraSmiley wrote:So, I just got a cool new game. Dogyuun. I excitedly opened the box and hooked up my OSSC to my new LG C9 OLED TV... nothing.6t8k wrote: I'm still interested in learning more about the chip's inner workings, however. What is the root cause of the sync anomaly? How does that initialization vector work that gets written to the 0x0e register when the game boots? How do two GP9001 chips interact with each other?
In case a patch for Batsugun/Dogyuun becomes feasible, you'll be able to read about it here, but all further poking is only tangentially related to this thread, so I'll leave it open for now if or how much of that I'll post here myself.
THEN, I remembered this thread. I was so focused on Fixeight and Knucklebash, I forgot the game that started this thread...DOGYUUN!!!!!!!
Damn. OK, so I can't even get a simple sync, even with a h.samplerate moved up.
A. Any progress on a patch?
B. So OSSC Pro will definitely fix this problem, right?
> A. Any progress on a patch?
No update so far.
> B. So OSSC Pro will definitely fix this problem, right?
You can expect a perfectly clear, stable and skew-free picture, but it will not be as good as a game without the sync anomaly, a patched game, or the cps2_digiav solution. There will be a very small amount of stutter due to a dropped/duplicated frame every now and then. This is to synchronize the output frame rate to the game's refresh rate, because the OSSC Pro will generate its own input sampling and output pixel clock signals instead of deriving them from the game's sync signal. In this manner, the anomaly contained in the latter is bypassed, but the clock signals cannot be exactly matched to the game's refresh rate.