Deathsmiles on lr-mame2015 : Any performance tips?

stevas

Thanks for the suggestion of over voltage to 6, but it's solved nothing for me.

I try to go anything above:

gpu_freq=700
v3d_freq=750
arm_freq=1950

And the game I'm testing (Dreamcast capcom Vs snk) just craps itself after starting a match (reboots itself).

From the numbers I see talked about on here, either I'm just flat out doing something wrong, or I've been extraordinarily unlucky? Or flycast is glitchy as hell?

pjft

@stevas as mentioned, please start a separate thread and provide more details there. Does the game not crash in lower frequencies? If so, then yes, you're out of luck there.

But don't change GPU freq on the pi 4. Remove that and try again. See this: https://www.raspberrypi.org/documentation/configuration/config-txt/overclocking.md

roslof

@stevas I'm thinking now it's either your kernel version or cooling on the Flirc.

Have you upgraded lately?
https://www.raspberrypi.org/documentation/raspbian/updating.md

roslof

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

@stevas as mentioned, please start a separate thread and pedicure more details there.

Good point.

stevas

Okay, there's a possible explanation here.

I recently changed PSU (to one which has a switch).
And it seems fine with over voltage 5, but not 6. I totally forgot I was using that now. Apologies.

I also didn't realise you were supposed to use individual settings rather than gpu_freq - so thanks for that heads up. (Does the hdmi_enable and the gpu_freq fighting over core_freq possibly upset things, btw? Because... Yeah, I was using both.)

The kernel should be relatively up to date, as I did update all after a recent rebuild. Like, maybe 10 days ago.
(Quick related question: is it possible to update all and specifically NOT update just one package? Say, fbneo. Just... Everything but that?)

Is that "specific to pi 4b" section a very recent addition? I swear I was on that OC page, like, a week ago, and didn't notice it...

Anyway, I'll go back to my official PSU and try some things out, and if I still have such issues I'll raise a new shout for help!

Thanks a bunch, y'all are great.

pjft

I have to say that "pedicure" instead of "provide" isn't the worst auto correct I've ever had. Fixed that.

The remarks around the pi 4 have been there for a while, it's what caused me to set the 3 settings individually when I was playing with it. But you never know, go test things out! Feel free to tad me in the new thread, or report back here if successful.

stevas

Haha, I did wonder if there was some weird use of the word in the pi world I was as of yet unaware of...

Yeah, thanks loads - I'll try your individual settings and see if the official PSU fixes the weirdness I'm seeing...

stevas

Well, if anything, it's even worse.

I'm really starting to hate this thing.

stevas

Sigh.

Okay, I figured out that the entire problem is capcom vs snk through flycast, which seems to suffer from some sort of memory leak.
I'm unsure if:
a) this is due to that specific game, or;
b) it's because I've set some flycast core option the pi just does not like -
but, overclocking seems to accelerate the issue, i.e. the more you OC, the faster it forces a reboot.

I will raise this as a separate issue, but it looks like my OC settings are fine; and yes, I wasted a LOT of time thinking they were the problem.
A.
LOT.
/thousand yard stare/

Edit
And you know what, I just realised that:
"There is a memory leak somewhere in the Reicast code" is in the documentation for flycast.
So... Arse.

barbudreadmon

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

but, overclocking seems to accelerate the issue, i.e. the more you OC, the faster it forces a reboot

3 possible causes for those reboot :

overheating => try better cooling or safer overclocking
power supply issues => maybe your psu is bad
bad board => buying a raspberry pi is a lottery... might be worth mentioning the early models of pi4 had faulty components...

Also :

i don't know of any memory leak in flycast code
if a memory leak was causing a reboot of your device (a freeze/crash after using every last bit of memory would be more likely), it would happen on every device, that's not the case
flycast is not reicast

AdamBeGood

@barbudreadmon As this thread is so tangential now, and you used to work on YabaSanshiro - I have no sound effects (I have music) on Exhumed/Powerslave (I tried both Euro and US versions). Any idea what that could possibly relate to? I know the emulator is still not 100% the finished article, I just wondered if you had any thoughts on things I could fiddle with? I've tried Settings->Audio->Output and then changed the driver, but none of them make a difference.

Edit: feel free to utterly ignore this, it is just one game that is vexing me so thought I'd quickly ask.

barbudreadmon

@AdamBeGood no idea and not interested, i don't work on this anymore

AdamBeGood

@barbudreadmon Not a problem at all. Sorry for asking, I know it was a bit cheeky. Cheers!

Also, Flycast is fantastic - so thank you for that.

roslof

Game: Beastorizer (beastrzr.zip)
Pi-Type: 4B (OC CPU: 1025; GPU 750)
Emulator: lr-mame-2016
Test: Watch full intro or play game
Default Framerate: 55-57 FPS
CPU Change: Decrease to 70%
New Framerate: Between 59.8 and 60 FPS (blip of 53FPS during 3D to 2D transition)
Summary: Very good improvement. No noticeable decrease in gameplay speed.

roslof

Game: Battle Arena Toshinden 2 (ts2)
Pi-Type: 4B (OC CPU: 1025; GPU 750)
Emulator: lr-mame-2016
Test: Play game, observe framerate
Default Framerate: 55-60 FPS
CPU Change: Decrease to 80%
New Framerate: Solid 60 FPS
Summary: No noticeable decrease in gameplay speed.

pjft

Interesting that you're going for 3D games here. Good to hear it helps with these!

I imagine that your OC CPU isn't 1025 though?

Have a great day and do share more of these!

dodonpachi

Any updates in performance tips for the CV1K games? Mushimesama and Dodonpachi Daifukkatsu are so close when the CPU overclock is set to 30%, but while I don't get audio drops, the slowdown is unfortunately too slow to be enjoyable. On other forums, I've read adjusting blitter delay can help--has anyone tried that? (Or know how to adjust that on lr-mame2016)

dodonpachi

Reviving this thread as it's relevant to the discussion. The last CV1K game, Dodonpachi SaiDaiOuJou, has been finally released...

... sort of, as a meme romhack.

I've tested it in lr-mame2016 with CPU overclock set to 30. It runs fairly well.

pjft

@dodonpachi you can't just drop that video here and leave it at that :D

What are we looking at here and, if it's a "romhack", what does that mean? Is it the actual game (as close as it gets, at least)? Does the most recent lr-mame2016 accept it if we compile it from source?

All I know of the game comes from here, and I suppose this is timely as yesterday I bought Dodonpachi Daioujou and Dodonpachi Daifukkatsu (again) on iOS as I actually find that these bullet-hell games play quite differently and satisfyingly on a touchscreen as well, though it becomes a completely different game.

Regardless, I'm all ears :) Thanks for sharing, and let us know more!

dodonpachi

@pjft it's a romhack of SaiDaiOuJou, titled "SaiDaiOuJou & Knuckles." It is in fact the real SDOJ, and I'm playing it as we speak on my Pi 4B using lr-mame2016. It's altered to have the player characters swapped with (I'm not making this up) Knuckles, a photo realistic tyrannosaurus rex, and Hello Kitty. The final boss was changed to Sans from Undertale.

However, when you find the rom, you have to rename the zip "DFKBL" in order to play it. Since SDOJ isn't support in Mame yet, it's only playable by tricking the emulator into thinking it's Dodonpachi Daifukkatsu Black Label.

The clean, unaltered SDOJ rom is still nowhere to be found, but allegedly it will be released by the creator of this hack on 4/20/22 (420... again with the memes).

Edit once more, for context: SaiDaiOuJou was the final Dodonpachi game made for arcades, released in 2012. Though almost 10 years old and clearly easy to emulate, the rom had not been released to the public until now... sort of. Previously, the only way to play this game was to import a copy of the Xbox 360 port.