Topic: Cv1000 slowdown accuracy tweaks

[skykid]

You might be using some very old version of the core then, recent versions allow fine tuning from 25 to 55.
The decimals need to be set in dips.
The last number (so the 57 from your example) is the blitter delay (from dips too).

Thanks for the fast reply. That's weird, because I'm using Batocera as a frontend and it's the latest Pi4 image (Batocera 35) and FBneo was part of the package. The FBneo core version is v1.0.0.03 3cbdf40. Is it possible to update the core through RA without losing my current settings (as I've done a fair amount of configuring)?

And sorry for being an idiot. I think I understand tabbing to blitter delay using a keyboard, but what are 'dips' exactly? Not Dipswitches right?

[barbudreadmon]

v1.0.0.03 3cbdf40

That version is from july and should include both the fine tuning of cpu clock below 55 and the decimals + blit delay through dips, however i can't guarantee batocera is using our unmodified source code.

Dips = Dipswitches indeed.

[skykid]

That version is from july and should include both the fine tuning of cpu clock below 55 and the decimals + blit delay through dips, however i can't guarantee batocera is using our unmodified source code.

Dips = Dipswitches indeed.

EDIT: Ok ignore that. I think I understand how it works now. The decimal point is actually in options > dip switches > el_rika?s tenth percent adjust. So to get 42.6% in Daiifukkatsu I set CPU overclock to 42% and then the tenth percent adjust to .6 for 42.6%, then the blitter delay to 59.

Does that sound right?

[dink]

The cpu overclock decimal section is in the pcb's dip's section, because fbneo doesn't have a way to change the cpu clock in decimals.  If you think that's frustrating, try changing the cpu decimals in mame standalone ui version, it took me 3 days and several explanations from el_rika before I got it right.


best regards,
- dink

[skykid]

The cpu overclock decimal section is in the pcb's dip's section, because fbneo doesn't have a way to change the cpu clock in decimals.  If you think that's frustrating, try changing the cpu decimals in mame standalone ui version, it took me 3 days and several explanations from el_rika before I got it right.


best regards,
- dink

I trust you on that.

So the way I?m doing it in my previous post is correct then?

[barbudreadmon]

So the way I'm doing it in my previous post is correct then?

Yes

[skykid]

Amazing, thanks so much to el-rika and dink for all your hard work, I can already see the difference.

As an aside (ish) since there are no settings for CAVE PGM titles, should I assume the likes of Ketsui are fine at defaults? Because the CPU setting defaults to 100% and sometimes I feel like it might be running a tad too fast. Could be my imagination though.

[barbudreadmon]

It seems there are some interesting news about cv1k blitter delay : https://github.com/mamedev/mame/pull/10849

[dink]

I've been keeping an eye on it

[Tatsuya79]

It's been merged.

[dink]

I havn't forgotten - just certain things preventing me from doing anything at this time.

best regards,
- dink

[dink]

buffi's new blitter code is in, and the old in-accurate method is still available via a DIP selection for testing (Blitter Timing: Accurate or not).

best regards,
- dink

[SirHenrythe5th]

Awesome!, can?t wait to update and test the Cave-SHMUPs in the evenning.
Thanks a lot!

[Tatsuya79]

Thanks!

I played mushi futari black and saidaioujou, it had slowdowns.   
I'm not sure how accurate it is but seems close to real arcade gameplay I compared it too (with the cpu at 50%).

[el_rika]

Fine ​tunned some values (Mushihimesama Ultra, Daifukkatsu BL) and finally properly analysed Futari 1.5 Ultra for the past month or so. This is probably top 5 hardest games ever made.

Actual pcb footage of Futari Ultra is hard to find, but with some help, i managed to find a couple of amazing superplays with Reco Normal and Palm Abnormal. The slowdown is 'very' close to pcb now. Try it at your own risk