[• 5 v2 Instructions / FAQ]

• 5 v2 Instructions / FAQ
• 3.x Instructions / FAQ
• RaspJAMMA Mini Manual
• RaspJAMMA 4-P Manual
• Mac Partitioning Guide
• Dipswitch Guide
• RaspJAMMA PCB Layout
• How to Fit your Raspberry Pi
• GPIO Wiring Guide
• Compatible ROMS List

Also running at 103% speed.  My guess is both are running at 59ish hz.

I'd just copy the mode from 57.5 just below the 57.444 mode, it's much closer to original speed:
vcgencmd hdmi_timings 1920 1 70 270 140 240 1 6 7 16 0 0 0 60 0 37122000 1

One thing of note with the early Pi 'modelines' is the human readable hz bit is not part of the mode calculation (the 60 in that 57.5 mode for instance).  The '2' just before that is turning on pixel doubling too (which may be why you had a wide screen on one of your attempts, '0' is probably also safe and doesn't pixel double).

The other thing we are bumping up against is my care factor,  I just want Double Dragon working because I know it'll be one of the first games a lot of people will ask about and want to see/play.  It's really only Wonder Boy that I care about the accuracy and smoothness.

Wonderboy looks good to me in 172, full speed and smooth (at least from a quick game).  AdvMAME isn't as smooth, FBNeo seems to be inconsistant, 203 is slow.

Wonderboy looks good to me in 172, full speed and smooth (at least from a quick game).  AdvMAME isn't as smooth, FBNeo seems to be inconsistant, 203 is slow.

172 is smooth as silk but feels like it has just the smallest amount of extra lag compared to FBNeo.  FBNeo does have the odd jerk but is a very good.

172 is way better on this build of arpicade than my old build.  I'm very happy now.

Just went back and played Wonder Boy on FB-Neo on the competitor's product and it simply plays better on that device.  Not sure how to bridge that gap. Still glad that 172 is way better on the new version though.

interesting.  I wonder what the difference is.  There's no reason ARpiCADE couldn't match the performance of any other RPi distro...  it could come down to how old ARpiCADE_3 is, I'm sure there's been updates to a bunch of Pi3 stuff over the years while I've been working on Pi4 and 5 stuff (possibly Retroarch itself, I didn't update it to add the FBNeo core).  Could be a Linux background process I haven't disabled or something too that causes the odd jerk in FBNeo (if that's the whole difference).  Could, in theory, also be a FBNeo setting - I didn't adjust anything much from the old FBA config.

I can have a look at it but not sure I'll come up with much, unless its a RA setting or something.  Not knowing what the other software you're running is I can't compare the 2 directly but that may be the way to figure out the difference (I doubt very much any JAMMA adaptor hardware differences would be a factor outside of the general system configs).

Could you try adding this to run.sh

## set performance CPU governor
sudo sh -c "echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor"

It will need to be before attract-mode is launched in the file.  I put it near the top of the file.  Not sure if it will improve FBNeo, some times it was better than others for me.

----
I just did some testing using ARpiCADE_3v11 with both MAME 0.172 and FBNeo & wboy using frame advance (pause game with 'p', for MAME shift+p advances one frame, FBNeo 'k' advances one frame).  Both MAME and FBNeo showed the same single frame before throwing a tomahawk using the pause, hold input and advance one frame, let go of input, advance another frame and see tomahawk.  (SF2CE on 172 reacts straight away, pause, hold input + one frame advance, result on screen).  Unsure if genuine WonderBoy hardware would also have 1 frame before you see the tomahawk, I don't own a wonderboy PCB or a high speed cam to check lag without frame advance.

Is the other build you have using runahead with FBNeo?  1 frame of runahead removes the single frame between button press and seeing the tomahawk, but I'm not sure if that's actually accurate to real hardware.

___
EDIT: just tried frame advance on GroovyMAME0.279 (ARpiCADE_5v2.7) it also showed one frame before the tomahawk, same as 172 and FBNeo (without runahead) on Pi3.

I didn't want to mention the competitors name! I'm an arpicade man 😁

Can I direct message you on here? I'll look.

Yeah, DM is fine.

Weirdly I just checked WBoy in FBNeo on Pi5... super smooth, but the FBNeo RA core on ARpiCADE_5 doesn't support runahead(!) - now I have another rabbit hole to look in.... and probably recompiling in my future.

EDIT: while it has no runahead it does have Game Mode, which I didn't see in the options on ARpiCADE_3...

I haven't been using run ahead.

good to know, I'll turn it off again.

Can you confirm that force_turbo=1 is set in config.txt on your other OS?

Did some more messing about and think I have FBNeo smoothed out, not sure it plays better than MAME 0.172 though.  Maybe I'm just no good at the game but they feel the same to me having now back to backed them a few times.  Not sure what I'm missing, I upgraded the RA binary (which I think may have helped) and downgraded the FBNeo core to match it better (no idea at this point if that helped).  Messed with a bunch of the RA video options too, the most notible change was run ahead but I think it made the emulation less acccurate (unless MAME has 1 frame of additional latency in Wonder Boy, IDK).

Tried with and without force_turbo too, again inconclusive... don't think it did any more than the cpu govenor setting I posted above.

Would you mind running your other board through a pause / input frame advance test?  I'd like to know if that one frame before the tomahawk appears is there (even if you have run ahead turned off).

I can post an update with the changes I've made to RA etc. if you like but I made it on 3.11... if you're using 3.X results may vary.

good to know, I'll turn it off again.

Can you confirm that force_turbo=1 is set in config.txt on your other OS?

Yes, it is on

I think a 3.11 update will be fine.

So, I'm trying to solve this no signal error on my monitor.  got a brand new 3b+ and a image card directly from arpi cade. 


It's hooked up like this, but the led light on the monitor still flashes.

about running out of ideas.


As I took this video, I just got sound on the machine, so clearly it's working.  However, I can not get a picture.  that dangling blue cable is from my vga monitor .  can't remember  how that one got hooked up to the  board.