Deathsmiles on lr-mame2015 : Any performance tips?

roslof

@pjft understood.
Minor (a non-issue for me): If you mess with the MAME slider option, it will visually lock to whatever value is set. But the slider at the bottom of the screen always matches the core setting. I think this is fine... Impressive that this actually works!

Will continue to verify the core value sticks and that performance is affected, but overall, looking great!

pjft

@roslof Ah, what you're saying is that MAME slider option changes will not reflect in the core options, is that it? Or can you elaborate?

Thanks.

roslof

@pjft sure:

STEPS:

Boot game
Change core setting
TAB/Check slider value for CPU (changes correctly)
Adjust slider value until CPU value changes
Return to core setting (it won't match the slider value)
Change core setting to a new value
TAB/Check slider value for CPU (will not match core; remains visually unchanged)
Observe the actual MAME slider bar at the bottom of the screen. (it WILL match core)

So I believe this is just a visual issue with the TAB/Slider menu not updating if you manually override in MAME. Minor. Would only likely cause confusion to people tuning both Options and TAB/Slider settings simultaneously, which I believe would be low-to-zero folks. #8 above (the bar at the bottom) always seems to be in-sync. So yay!

pjft

@roslof Yeah, I'm not going to worry about that one. Especially as this specific slider/option is hidden by default - only shows up if you actually enable the cheats - but, if the core option is available, it should make the need to go to that menu redundant.

Also, because I don't want to be hacking away (even further) a sync between MAME-options and libretro-options. :)

SeraphisCain

@pjft This is great, thank you! I'll test it out later today and let you know if I have any issues.

roslof

@pjft said in [Deathsmiles on lr-mame2015 :

Also, because I don't want to be hacking away (even further) a sync between MAME-options and libretro-options. :)

I could only imagine!

I tested your 2016 build extensively (>4hrs now). Very solid. Absolutely no notable issues, and only added benefit. Now I have to keep this version of MAME locked down so I don't override it with a newer MAME-2016. ;-)

Worth a shot creating a PR upstream. Your change could also [captain-obviously] benefit lr-mame2015 and lr-mame (currently at 0.220).

If I have time, will play around with DoDonPachi Dai-Ou-Jou Tamashii and DoDonPachi III on lr-mame (MAME 0.220) and see if there are similar benefits.

AdamBeGood

@pjft Maybe a stupid question, but how do you create a new system? I am so disorganized that I am unsure which games I have running on lr-mame2016 and not sure I want this setting on all of them.

It's cool that you managed to work out how to see the slider via the config, clever stuff.

pjft

@roslof isn't 3 pretty much Daioujou?

I might be making things up, but I don't see why those wouldn't work 100% speed in lr-mame. As far as I understand it, it's just that the ROM dumps are recent, but the system itself is even emulated at 100% on FBNeo on the Pi3, if I recall correctly.

Have you tried them already, and are they slow? Let me know.

@AdamBeGood it is hacky, but the short version is to add a second line to the emulators.cfg file that points to the location where you place this binary. I have mine in the same path but on a separate lr-mame2016-pjft folder. On my phone, so apologies if I'm not more thorough here at the moment.

roslof

@AdamBeGood

It sounds like you already have lr-mame2016 installed, so you shouldn't need a new system. Just launch the ROM and tap a joystick button to enter the runcommand menu. Don't change the default emulator. Use option #2 (Select emulator for ROM) and choose lr-mame2016. So that way, all ROMs you didn't specify will use the default emulator, but only the ROM(s) you choose can use an alternative emulator like lr-mame2016.

To add PJFT's file
Not sure if you completed this series of steps. Again, assuming you have lr-mame2016 installed, you may choose to make a backup of the original binary.

sudo cp /opt/retropie/libretrocores/lr-mame2016/mamearcade2016_libretro.so /opt/retropie/libretrocores/lr-mame2016/mamearcade2016_libretro.so.bak

then extract @pjft 's file mamearcade2016_libretro.so into that directory.
You'll then need to set its permission to execute:

sudo chmod +x /opt/retropie/libretrocores/lr-mame2016/mamearcade2016_libretro.so

Hope some or all of this helps.

roslof

@pjft said in Deathsmiles on lr-mame2015 : Any performance tips?:

the system itself is even emulated at 100% on FBNeo on the Pi3, if I recall correctly.

You're absolutely right. I missed that FBNeo supported it (older romset) and just checked and performance in lr-mame is at framerate. Nothing to see here.

AdamBeGood

@roslof and @pjft Thanks for the help, I'll have a look at this tomorrow!

stevas

Sorry to hijack this thread somewhat, but how do I regularly see posts stating overclock to stuff like:

over_voltage=6
h264_freq=750
isp_freq=750
v3d_freq=830
hdmi_enable_4kp60=1
arm_freq=2050

... When I go anywhere over 1950 arm, or 750 v3d, and my Pi4 becomes unusably unstable? It'll last about ten minutes before randomly crashing on whatever I happen to be doing (even just on the Retropie menu or editing files).

Are these numbers only possible with a cooled system? I'm using a flirc case (so: no fan.)

Also, every now and then someone posts a setting I've not even heard of. isp_freq what? h264 when?

Edit: you know what, never mind, I can see I missed part of this discussion about OC now, and trying to make sense of it...

AdamBeGood

@stevas My Pi handles what you are saying your overclock settings are absolutely fine. Mine is in an Aluminium Armour case, no fan. I think this might be the "silicon lottery" I've heard of, where some Pis can just take more than others... I might be wrong though.

Once mine gets to 2100, things go awry!

pjft

Not wanting to derail the conversation - please feel free to kick off another thread around the actual overclocking - I have found that these settings work well on 3 RPi 4B's I have around here, 2 2GB and one 4 GB models.

The 2100 was almost stable one the 4GB one (which is where I first tried these) but ended up freezing randomly after a while. These have been fairly stable.

Different boards will have different success rates with overclocking.

I have v3d for the 3D games (Saturn and Dreamcast, unsure if some PSP as well), and the rest is just par for the course.

AdamBeGood

@pjft I often have trouble getting into mega.nz. Is there some trick to it? At the moment I just try every hour or so and eventually I will be able to access the file. I've tried on my phone and PC, when it comes up on one it will come up on the other.

AdamBeGood

@Darksavior Which setting is it in my latency settings that makes the audio drop out? I still have them set like that and don't know which one it is.

pjft

@AdamBeGood Here's the same on Google Drive:

(new link): https://drive.google.com/file/d/1faM11qnX0p3BD4BW3ipSz5MwABT_jra7/view?usp=sharing

stevas

Thanks for the replies all.

I realised though, I have voltage only at 4. Not sure if that's why I get issues trying to push these values, I'll try that out.

Edit: yeah, the random freezing is what I was talking about. Is it possible that's down to the over voltage not being set high enough? Anyway, I will test that.