Deathsmiles on lr-mame2015 : Any performance tips?
-
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.
-
@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.
-
-
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...
-
@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!
-
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.
-
-
@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.
-
@AdamBeGood Here's the same on Google Drive:
(new link): https://drive.google.com/file/d/1faM11qnX0p3BD4BW3ipSz5MwABT_jra7/view?usp=sharing
-
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.
-
@stevas Definitely - without over_voltage 6 my pi would not boot. I forgot that once.
-
PR submitted upstream - a simplified version of the code, actually.
https://github.com/libretro/mame2016-libretro/pull/43
If anyone wants to test the latest version, here it is. Nothing should really have changed, but the more the merrier.
https://mega.nz/file/UFU11KSI#9kTKoOWAg-WpqCbTm7tKXei5cPgFAizDciurrbyPQuk
And here on Google Drive:
https://drive.google.com/file/d/1faM11qnX0p3BD4BW3ipSz5MwABT_jra7/view?usp=sharing
-
-
@AdamBeGood sounds like you're downloading to a PC, then uploading to the pi? You could put it in your pi home drive, where you should have permission to save. Something like /home/pi/Downloads
Then you could open a console window and move it to the correct location.
sudo mv /home/pi/Downloads/mamearcade2016_libretro.so /opt/retropie/libretrocores/lr-mame2016/
-
@roslof help me out here - running from the lr-mame binary I get segmentation faults on both ddp3 and ddpdojt . Am I missing something?
-
@pjft said in Deathsmiles on lr-mame2015 : Any performance tips?:
@roslof help me out here - running from the lr-mame binary I get segmentation faults on both ddp3 and ddpdojt . Am I missing something?
Launch ddp3 with verbose logging enabled. Copy /dev/shm/runcommand.log output to pastebin.com and post link here.
-
@roslof That works perfectly! But my Overclock setting still isn't saving.... Do I need to change it within the config rather than within the game?
-
@AdamBeGood said in Deathsmiles on lr-mame2015 : Any performance tips?:
@roslof That works perfectly! But my Overclock setting still isn't saving.... Do I need to change it within the config rather than within the game?
Change it from the Core Options. Not from the MAME Tab slider options.
How: While running the game, with your game controller, hold your hotkey, and whatever button you mapped to "X" to enter RetroArch menu. Then scroll down to Options. Change CPU in there. THEN scroll to the top of the Options menu and Create a game configuration, so the CPU change only saves for the game you are running.
-
@roslof Clever stuff! Yep, that works. Thank you!
-
@roslof Nevermind. Nothing that reinstalling the binary didn't fix - interesting.
Thanks.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.