[FlashShift]

Ah I see. It seems to forget not only clock phase but its auto clock phase is also different. It also forgets the active pixels. If I manually update both of those (removing it from auto) it works again.

[FlashShift]

Still struggling with MCR games though. Spy Hunter is perfect on 0.78 but super jittery on 0.79 and higher.

[FlashShift]

I finally figured this out. Sampling phase needed adjustment. 0.81 working for me for Lumacode now.

[FlashShift]

There doesn’t appear to be a sticker on the bottom; I bought it from Stoneage Gamer maybe six months ago FWIW.

It looks like FW 0.80 is where the problems with Lumacode start. 0.79 works ok. I’ve attached screenshots between the two versions.

[FlashShift]

It’ll have to be this weekend but I’ll test 0.79. 0.79 is where the most changes got made to Lumacode.

[FlashShift]

From NES/Famicom straight into the AV2 port on OSSC Pro (Green/Y, IIRC), out standard HDMI port. Nothing special about the setup. I’ve tried with both AV2 YPbPr and RGsB (and scrolled through the rest for good measure).

For Spy Hunter, it’s going through JAMMA adapter into Axunworks SuperGun (also tested my HAS), into SCART, and out HDMI. Have tried Scaler, Line Multiplier, plenty of different settings. It’s almost black. Can barely see it with 0.81.

[FlashShift]

Hi- I upgraded from 0.78 to 0.81, and had to downgrade:

1. Lumacode seems to be broken; I have the c0pperdragon chip on my PPU on both a NES and a Famicom, works flawlessly with 0.78 however is mostly green and yellow using 0.81. I’ve gone through and verified the settings were correct. Downgrading rectified the problem.

2. It behaves differently with MCR games. While TRON seems to work better on default settings, Spy Hunter appears extremely dark and there is no way to improve it other than to turn off the different clamp settings (which makes the picture jitter). I’ve checked RGB gain on my Axunworks and it is too dark to see even at max with 0.81. Works fine with 0.78.

Would be happy to work with anyone interested in trying to debug the firmware; for now I’m back on 0.78.

• This reply was modified 3 months ago by FlashShift.

[Author]

Posts