ARpiCADE_5 - for Pi4 or Pi5

[cool_factor]

At work so cant try:

https://www.diskinternals.com/linux-reader/

Itll rule out Paragon issues. Maybe try and see if black screen problem still happens using it.

EDIT: Bummer, appears to be read only access.

[FrizzleFried]

Confirmed - AdvMAME vids/snaps/etc all fixed with the path fix within Attract Mode. What file can I change (if any) to do so from within linux? I'm trying to make as much "done" as possible for my latest image.

I'm at a point now where everything is done in the latest image aside from what I have to do in-cabinet. That process is about a 20 minute process (changing to vertical, adding 480i, updating for the controls, adding all the displays, removing all the non-usable displays, changing the path for AdvMAME, etc)... anything I can do to automate any of that makes the image that much closer to "done" at loadup.



Next step is to create a few custom romlists (Shumup, Classics, Etc.)...

I might get off my arce and do what I've wanted to do forever... make "virtual" versions of popular multigame boards out there... do a Romlist with just the 60-in-1 games in it. Do a Romlist with the Bitkit games in it. Do a Romlist with the SDArcade games in it. Etc...

[cool_factor]

Bummer. That tells me Dee2er is going to likely have to compile it.

That link I provided has it compiled already, you have to create an acct to be able to download it. Unless I read it wrong you're just copying and pasting certain files over existing.

[dee2eR]

Confirmed - AdvMAME vids/snaps/etc all fixed with the path fix within Attract Mode. What file can I change (if any) to do so from within linux? I'm trying to make as much "done" as possible for my latest image.
adding all the displays, removing all the non-usable displays, changing the path for AdvMAME, etc)... anything I can do to automate any of that makes the image that much closer to "done" at loadup.

You will want to investigate /home/pi/.attract/attract.cfg and also /home/pi/.attract/emulators/advmame.cfg (for the double /firmware/ fix)

[dee2eR]

Bummer. That tells me Dee2er is going to likely have to compile it.

That link I provided has it compiled already, you have to create an acct to be able to download it. Unless I read it wrong you're just copying and pasting certain files over existing.

Unfortunately it is compiled for x86... at least I thought it was when I looked yesterday...

You're right though, once we have MAME recompiled it can just overwrite the old MAME binary with the new one - justy one file. It can be done as an update for what we already have without much issue.

[dee2eR]

BTW... I'm running mine overclocked to 2880 / 960 (20% overclock) without so much as a hiccup. The fan barely even comes on (I've seen it come on during gameplay for 2 games and even then only once in a while). I will say though, my garagecade is rocking about 50 degrees so it's nice and cool in there. I've run it 3000/1000 without so much as an issue but when you have to re-image every time you make a change, I figured it would be safer to go back to 2880/960 ... though I would like to see how far this will go (though I've read that any gains over 3000mhz show very little actual benefit).

You may not actually be OCing. I noticed in your config.txt in th eimage you sent you had both overclock and underclocks setup at once. I think the underclock may have been overriding the OC as it was later in the file.

[dee2eR]

• Vertical ARpiCADE intro screen (which is an easy fix for even me... as all I have to do is modify the actual image being used to make it a vertical image... no big deal what so ever).

You then need to remake the boot initrmfs with the new image. The image used is /usr/share/plymouth/themes/pix/splash.png - skip the instruction to copy to there from the more easily accessible /boot/previews (/boot/firmware/previews/ when running on the Pi) if you don't need to do that.

sudo cp /boot/firmware/previews/system/splash.png /usr/share/plymouth/themes/pix/
sudo update-initramfs -k all -u -v
sudo reboot

Updating the initramfs will take a few minutes. If all goes well you will see the results when you reboot.

[FrizzleFried]

BTW... I'm running mine overclocked to 2880 / 960 (20% overclock) without so much as a hiccup. The fan barely even comes on (I've seen it come on during gameplay for 2 games and even then only once in a while). I will say though, my garagecade is rocking about 50 degrees so it's nice and cool in there. I've run it 3000/1000 without so much as an issue but when you have to re-image every time you make a change, I figured it would be safer to go back to 2880/960 ... though I would like to see how far this will go (though I've read that any gains over 3000mhz show very little actual benefit).

You may not actually be OCing. I noticed in your config.txt in th eimage you sent you had both overclock and underclocks setup at once. I think the underclock may have been overriding the OC as it was later in the file.

I noticed that a couple images ago...



...fixed it of course.

[dee2eR]

Just tried writing to the /boot/ partition of the image FrizzleFried sent using Win10 (after I'd fixed the 2nd partition with GParted) and did not get any corruption... looks like I may have to try harder to replicate this one.

So far I renamed vertrol.txt to vertrol.bak.txt successfully, I took the SD card back to Win10 and renamed it again. While I was at it I attempted to mount the second partition as it could be seen (Windows could not mount it but offered to format it for me, no thanks). Ejected the mounted /boot/ partition took it back to my Linux box and both partitions still work fine...

Unless GParted did some magic when it fixed the 2nd partition that is stopping it happening again I think it has to be either Paragon or Win11 related... possibly, I can try again tomorrow on a mates Win11 box, pretty sure it has Paragon on it too.

EDIT: reading back cool_factor is using Win10... I'm leaning heavily into this being Paragon related.

[FrizzleFried]

These days I only really have to get in to the linux side to add ROMLISTS. Well, 90% of the time it's that. If you could move the ROMLISTS folder to the Windows side... perhaps I could test with Paragon not running at all...