Attract-Mode Support Forum
Attract-Mode Support => General => Topic started by: pibuilder on October 13, 2018, 07:46:44 AM
-
Hello I'm Looking for a prebuilt compatible for a RPI3B+ IMG SINGLE ROM Load directly to one MAME game. I want one for a horizontal set up and one for a vertical setup not sure if that matters. Primarily my focus would be for a horizontal game.
As an example I want it to hide all of the Raspberry boot screens, I DO want it to display my custom Splash screen, Automatically launching ONE Single game / loading it NO MENUS.
Ideally It's an image where I can change / modify in the future that particular game with ease should I build different games with the same SINGLE ROM / direct load.
-
You could modify the Retropie image, its Docs describe how to disable boot messages (https://retropie.org.uk/docs/FAQ/#how-do-i-hide-the-boot-text) and how to set the splash screen (https://retropie.org.uk/docs/Splashscreen/). Attract-mode is part of its experimental packages (https://retropie.org.uk/docs/Updating-RetroPie/#using-the-retropie-setup-script), but you'd have to do its setup yourself.
edit: To boot into AM instead of Retropie's standard frontend Emulation Station, you just have to edit the file /opt/retropie/configs/all/autostart.sh and replace the command to start Emulation Station to AM's starting command.
There was an attempt to build an AM-based Retropie image (https://retropie.org.uk/forum/topic/93/attract-mode-with-retropie-alternative-to-emulationstation), but it has not been updated for two years, and the Retropie forum rules state that only the official, unmodified Retropie image will be supported there (edit: they will help users to modify the official setup themselves, though).
-
At the end of the day I'm sure someone has an .img file they can share I DON'T want any ROMs included on it just so it's easy enough for me to add a specific 1x rom to the folder, edit a line of text in a config file. My biggest concern is turn on the Rpi3B+ & having it load directly into the MAME game with NO MENU, almost as if it was an original PCB is what I'm looking to essentially accomplish.
-
sounds kinda neet.... mini arcade pcb's
baby jama boards :P
-
My biggest concern is turn on the Rpi3B+ & having it load directly into the MAME game with NO MENU, almost as if it was an original PCB is what I'm looking to essentially accomplish.
That can be also done quite easily with Retropie.
- Boot Retropie once into Emulation Station and set up your controller(s).
- Put your ROM file in the directory /home/pi/RetroPie/roms/arcade.
- Edit the config file /opt/retropie/configs/all/autostart.sh, put a "#" before emulationstation #auto so that it reads #emulationstation #auto. This will disable the start of Emulation Station at boot time.
- Add this line after #emulationstation #auto with the name of your ROM file instead of NAMEOFYOURROMFILE:
/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ arcade '/home/pi/RetroPie/roms/arcade/NAMEOFYOURROMFILE'
Retropie should boot directly into this game then. If you ever want to boot into Emulation Station again, just remove the "#" that you put before its starting line in the autostart.sh and put a "#" before the added line instead to stop it from starting the game. The "#" marks a line as a comment that should not be executed.
-
My biggest concern is turn on the Rpi3B+ & having it load directly into the MAME game with NO MENU, almost as if it was an original PCB is what I'm looking to essentially accomplish.
That can be also done quite easily with Retropie.
- Boot Retropie once into Emulation Station and set up your controller(s).
- Put your ROM file in the directory /home/pi/RetroPie/roms/arcade.
- Edit the config file /opt/retropie/configs/all/autostart.sh, put a "#" before emulationstation #auto so that it reads #emulationstation #auto. This will disable the start of Emulation Station at boot time.
- Add this line after #emulationstation #auto with the name of your ROM file instead of NAMEOFYOURROMFILE:
/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ arcade '/home/pi/RetroPie/roms/arcade/NAMEOFYOURROMFILE'
Retropie should boot directly into this game then. If you ever want to boot into Emulation Station again, just remove the "#" that you put before its starting line in the autostart.sh and put a "#" before the added line instead to stop it from starting the game. The "#" marks a line as a comment that should not be executed.
Can you or someone please post this pre-built image file without any roms of course possibly including Gridlee a legal rom as an example the problem is I already have a pre-built image with loads of games and the memory card is super maxed out with video snaps , marquee images or nonsense which I don't want any of that. Hopefully someone has a clean pre-built image they can share compatible with the rpi3b+.
Currently my autostart.sh looks like this:
setterm -cursor off
stty -echo
clear
attract 2>&1 | grep -o $'\033\[2J'
After placing in the text as you recommended It still loads to my wheel / a menu within Attract Mode & DOES NOT launch the game directly. Can you or anyone else notice any mistakes within this autostart.sh:
setterm -cursor off
stty -echo
clear
attract 2>&1 | grep -o $'\033\[2J'
#emulationstation #auto
opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ arcade '/home/pi/RetroPie/roms/arcade/galaga'
-
Can you or someone please post this pre-built image file without any roms of course possibly including Gridlee a legal rom as an example the problem is I already have a pre-built image with loads of games and the memory card is super maxed out with video snaps , marquee images or nonsense which I don't want any of that. Hopefully someone has a clean pre-built image they can share compatible with the rpi3b+.
Sorry, I can only help you modify the official Retropie image, if you want to try that route.
The official image is available here: https://retropie.org.uk/download/
After placing in the text as you recommended It still loads to my wheel / a menu within Attract Mode & DOES NOT launch the game directly. Can you or anyone else notice any mistakes within this autostart.sh:
Your autostart.sh is completely different from the official Retropie autostart.sh. The latter only contains a single line "emulationstation #auto". My instructions are meant for that one. Thus, just adding my lines to your autostart.sh isn't going to do much good. You should either delete the old content (be sure to backup the file first!) or put an "#" before every line in it.
Also, you forgot a "/" at the start of the last line. It has to begin with "/opt/..." and not "opt/..."
Finally, you only used "galaga" as the ROMs filename. Does it really have no extension like ".zip" or similar? You have to use the whole filename including any extension.
Having said all that, I really recommend that you work from scratch with the official Retropie image instead of your custom made one, as you can't be sure in what ways it differs from the official one, which could create problems if you apply a modification that's meant for the official image.
-
Having said all that, I really recommend that you work from scratch with the official Retropie image instead of your custom made one, as you can't be sure in what ways it differs from the official one, which could create problems if you apply a modification that's meant for the official image.
Initially I tried adding the / & the .zip with what I left out to my modded / custom .img and still couldn't get things going (the single ROM load / launch no menu etc).
With that being said I'm doing a FRESH build on my rpi3b+ as you suggested. So far:
-I downloaded & installed 4.4 retro pi...
-Emulation station up and running, I have wifi setup & working, [added the ROM(s) to the proper folder]
-Despite the fact that I only want ONE single rom I loaded most of .78 MAME set so hopefully once I get this going I can just modify the line of text to correspond to the ONE rom I want to launch.
-TESTED game launch using regular emulation station, game(s) load fine.
-my autostart.sh only currently shows the following without me modifying it:
emulationstation #auto
Next I added in what you said to do and my autostart.sh file now looks like this:
#emulationstation #auto
/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ arcade '/home/pi/RetroPie/roms/arcade/tmnt.zip'
WORKS ! Loads right to TMNT ! thanks !
Now my focus is to:
-HIDE bootup text / raspberry logo's. (Minor as machines would be turned on prior to people / the masses seeing it but still want to Hide that stuff anyways with the exception of my own custom splash.
-Major thing is I need a SAFE SHUTDOWN single press with a hidden inside cabinet micro switch to leave the ROM and shut it down rather than launching it back to any menu, I literally want it to SHUTDOWN from that single ROM. It can be "ESC" or anything on the IPAC so the keystroke doesn't matter i.e. it could be "shift", F8" Whatever... but when hitting it I need it to safely shut the pi down to prevent corruption of the sd card.
-
My pleasure. :) And thanks for the step-by-step description, it may help others doing the same. As for your remaining questions:
The Retropie Docs describe how to disable the boot text here: https://retropie.org.uk/docs/FAQ/#how-do-i-hide-the-boot-text
You can disable the splash screen in the Retropie Setup > Configuration / tools > splashscreen
Some links about the shutdown button:- A checklist with some options: https://retropie.org.uk/forum/post/122426
- How can you run a script triggered by a joystick input? – https://unix.stackexchange.com/questions/107818/how-can-you-run-a-script-triggered-by-a-joystick-input
- cyperghost's Multi Switch Shutdown Script: https://retropie.org.uk/forum/topic/17415/multi-switch-shutdown-script
- A video about adding a power switch to the Pi: https://www.youtube.com/watch?v=4nTuzIY0i3k
- A hardware solution, the Powerblock: https://blog.petrockblock.com/2015/07/04/powerblock-another-power-switch-for-the-raspberry-pi/
(there's a dedicated subforum for all Petroblocks on https://retropie.org.uk/forum/category/14/controlblock-powerblock-co)
It may be a good idea to join the Retropie forum and ask there about it, because I have no practical experience in such a button. Since you're using the official Retropie image now, they will give you support for it. I'm called Clyde there, by the way.
-
My pleasure. :) And thanks for the step-by-step description, it may help others doing the same. As for your remaining questions:
The Retropie Docs describe how to disable the boot text here: https://retropie.org.uk/docs/FAQ/#how-do-i-hide-the-boot-text
prior to branching off and signing up to another site you've been extremely helpful and hopefully you can aid me on these last few things...OK I went to the link you recommended [https://retropie.org.uk/docs/FAQ/#how-do-i-hide-the-boot-text], perhaps I'm doing something wrong or not typing it in the proper spot but: When I exit a game it takes me to the pi's "terminal text". Within the link you provided it says to type in just to start out logo.nologo: turns off raspberry(s) at boot
However when I try that first I'm getting this error within the terminal text (says command not found):
(https://preview.ibb.co/cT6MO0/nologo.jpg) (https://ibb.co/fn0gO0)
-
You have to add those options to the file /boot/cmdline.txt, or modify them if they are already present.
For example, my cmdline.txt looks like this:
dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=f2d3cb4f-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait loglevel=3 consoleblank=0 plymouth.enable=0
Now I would add the options logo.nologo and quiet to the end of the line:
dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=f2d3cb4f-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait loglevel=3 consoleblank=0 plymouth.enable=0 logo.nologo quiet
You can do that quickly by entering this command in the text console:
sudo echo " logo.nologo quiet" >> /boot/cmdline.txt
sudo executes the following command with root (i.e. administrator) permissions, because all files in /boot are owned by root and can't be modified by Retropie's standard user "pi". echo writes the following text somewhere, in this case to /boot/cmdline.txt. The >> does append the text to the file (a single > would overwrite the whole file).
Mind the single space before logo.nologo, so that the option will be separated by a space from the end of the existing line. That said, be careful to enter all my commands exactly as written to avoid more or less severe mistakes.
Some more commands for the console (again, all text behind a "#" is just a comment):
# edit the file in a rudimentary editor, exit it with ctrl+x
sudo nano /boot/cmdline.txt
# restart your game (at least I think so)
exit
# start Emulation Station
emulationstation
# restart the Pi
sudo reboot
# shutdown the Pi
sudo halt
-
So I'm using winSCP and I'm able to modify other things however if I touch the cmdline.txt file I can't make any changes. Won't even let me delete the file....
Permission denied error:
(https://image.ibb.co/b9bpbL/errorcode.png) (https://imgbb.com/)
When trying to type in what you said into the terminal
sudo echo " logo.nologo quiet" >> /boot/cmdline.txt
I actually copied / pasted it in PuTTy... I got this error:
(https://preview.ibb.co/kVpxVf/2nderror.png) (https://ibb.co/duZ9bL)
-
1. You can't modify the cmdline.txt file because the /boot volume is mounted as read only. Remount the /boot volume as read/write to modify the cmdline.txt.
sudo mount /boot -rw -o remount
sudo nano /boot/cmdline.txt
2. To have your system shutdown after you use your emulator "exit" button(s). Change your autostart.sh to this
#emulationstation #auto
/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ arcade '/home/pi/RetroPie/roms/arcade/tmnt.zip'
sudo poweroff
3. Why are you asking these questions here? This has absolutely nothing to do with Attract-Mode. I don't mind but it doesn't make much sense.
Update - I was incorrect in saying that the /boot volume is mounted as read only in #1 above. I mixed up this OS for another popular Pi OS that does make the boot volume read only. You can just do this instead.
sudo nano /boot/cmdline.txt
-
So I'm using winSCP and I'm able to modify other things however if I touch the cmdline.txt file I can't make any changes. Won't even let me delete the file....
Those files can only be modified (or deleted) with root permissions, which WinSCP doesn't have since it logs in as the normal user "pi". You would need a SCP (Secure CoPy) tool that can execute sudo on the remote system do edit those files.
I actually copied / pasted it in PuTTy... I got this error:
Oops, my mistake, sorry. The redirection via ">>" doesn't get the root permissions we gave echo via sudo. You'll have to write it like this:
sudo su -c "echo ' logo.nologo quiet' >> /boot/cmdline.txt"
Alternatively, you can edit the file manually with sudo nano /boot/cmdline.txt. You exit the editor with ctrl+x, then answer the question to write the file with "y" and confirm the filename with enter.
A third option would be to copy the file as user pi, then either use the first echo command or edit it with WinSCP, and then copy it back as root:
# copy the file as pi to /tmp
cp /boot/cmdline.txt /tmp
# append the options via echo (this time without sudo) or edit it with WinSCP
echo " logo.nologo quiet" >> /tmp/cmdline.txt
# copy it back to /boot WITH sudo, so it belongs to root again
sudo cp /tmp/cmdline.txt /boot
… progets beat me to it by a fews minutes while I was writing this. I'll post my reply anyway since we offer different solutions. :)
-
1. You can't modify the cmdline.txt file because the /boot volume is mounted as read only. Remount the /boot volume as read/write to modify the cmdline.txt.
This won't work in Retropie (edit: tested it – it doesn't), because /boot is already mounted as rw there, but only root has write permissions in it.
3. Why are you asking these questions here? This has absolutely nothing to do with Attract-Mode. I don't mind but it doesn't make much sense.
That's why I suggested to continue on https://retropie.org.uk/forum/. :) But I also don't mind to answer any questions I can here.
-
1. You can't modify the cmdline.txt file because the /boot volume is mounted as read only. Remount the /boot volume as read/write to modify the cmdline.txt.
This won't work in Retropie (edit: tested it – it doesn't), because /boot is already mounted as rw there, but only root has write permissions in it.
3. Why are you asking these questions here? This has absolutely nothing to do with Attract-Mode. I don't mind but it doesn't make much sense.
That's why I suggested to continue on https://retropie.org.uk/forum/. :) But I also don't mind to answer any questions I can here.
LOL. I tested and updated my post before I saw this. I was thinking about LibreELEC and OpenELEC which make the /flash boot volume read only by default.
-
LOL. I tested and updated my post before I saw this. I was thinking about LibreELEC and OpenELEC which make the /flash boot volume read only by default.
No sweat, I didn't even think of this possibility, because I'm used to *buntu Linux and Retropie where /boot is rw. :)
-
2. To have your system shutdown after you use your emulator "exit" button(s). Change your autostart.sh to this
#emulationstation #auto
/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ arcade '/home/pi/RetroPie/roms/arcade/tmnt.zip'
sudo poweroff
Thanks ! that worked perfectly however I'm testing this outside of a dedicated cabinet on my TV at the moment and on my ps4 controller I was able to "exit" the emulator which shut down the pi, i have a few concerns / questions...
1.) How safe is "sudo poweroff" within the autostart.sh in other words I want to ensure this prevents corrupting the micro SD card, as opposed to just unplugging the game / cutting power via a surge protector (which I know is a no-no).
2.) How do you change the "exit" keys as of now it's my Sony PlayStation 4 Dualshock controller which is "hotkey / ps button logo in the center, along with "options" button. In other words when I place this into a cabinet I'll be using an IPAC controller / keyboard encoder which I can essentially MAP / programs any keys to have it "EXIT" or in this case shut down the pi. I'm using MAME Libretro2003 / I believe it's in conjunction with RetroArch. In a perfect world I'd like to hit "ESC" on the keyboard to have it "exit / shutdown" the pi.
3.) I didn't get rid of the 4 raspberry pi logo's yet nor the load up text which I'd still like to do. & I'm confused about that because of a permission denied lock-out.
-
1. It's safe. You can also use "sudo halt", "sudo shutdown", "sudo init 0" or any other method to power the system off safely. There are slight differences. I like "sudo poweroff" because it will also power off most linux devices (but not the Pi).
2. Pressing the "Esc" key in RetroArch should exit the emulator (and shutdown your Pi) by default. You shouldn't have to change anything for it to work.
3. I provided a way to edit the cmdline.txt file in a previous post. If you have permission issues login as "root" to make the change. You can also put the sd card in a PC and edit the file there, you won't have permission problems doing it this way but you must use a unix aware text editor such as Notepad ++ and not the builtin notepad or wordpad program. It would be a good idea to make a backup of the file before you modify it, just in case.
-
3.) I didn't get rid of the 4 raspberry pi logo's yet nor the load up text which I'd still like to do. & I'm confused about that because of a permission denied lock-out.
I don't know if you can get rid of the raspberrys (I would have to research that further myself).
Aside from progets' two solution for the permissions problem, I also gave you two and a quick description for the nano editor:
Oops, my mistake, sorry. The redirection via ">>" doesn't get the root permissions we gave echo via sudo. You'll have to write it like this:
sudo su -c "echo ' logo.nologo quiet' >> /boot/cmdline.txt"
Alternatively, you can edit the file manually with sudo nano /boot/cmdline.txt. You exit the editor with ctrl+x, then answer the question to write the file with "y" and confirm the filename with enter.
A third option would be to copy the file as user pi, then either use the first echo command or edit it with WinSCP, and then copy it back as root:
# copy the file as pi to /tmp
cp /boot/cmdline.txt /tmp
# append the options via echo (this time without sudo) or edit it with WinSCP
echo " logo.nologo quiet" >> /tmp/cmdline.txt
# copy it back to /boot WITH sudo, so it belongs to root again
sudo cp /tmp/cmdline.txt /boot
Just choose your preferred method, or try some of them, and tell us any problems you may face with an explicit description what you did.
We're nearly there! :D
-
I don't know if you can get rid of the raspberrys (I would have to research that further myself).
Yes, you can. It's the logo.nologo part of the cmdline.txt.
P.S. I should mention that the cmdline.txt needs to all be on one line. No [CR] or word wrap.
-
logo.nologo: Ah, I didn't know that. As a long term Linux geek, I like the boot messages, and so I don't use the guide to hide them myself. :) I just point others to it and help them to use it.
I already mentioned that the options have to go to the end of the line, but things like that can be easily overlooked, so it makes sense to mention them again.
Now I would add the options logo.nologo and quiet to the end of the line:
dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=f2d3cb4f-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait loglevel=3 consoleblank=0 plymouth.enable=0 logo.nologo quiet
-
1. It's safe. You can also use "sudo halt", "sudo shutdown", "sudo init 0" or any other method to power the system off safely. There are slight differences. I like "sudo poweroff" because it will also power off most linux devices (but not the Pi).
Good to know that's reassuring... thanks.
2. Pressing the "Esc" key in RetroArch should exit the emulator (and shutdown your Pi) by default. You shouldn't have to change anything for it to work.
Thankfully exactly just that... It worked, the ESC key shutdown the Pi (which is exactly what I wanted it to do...So thanks!) :-)
3. You can also put the sd card in a PC and edit the file there, you won't have permission problems doing it this way but you must use a unix aware text editor such as Notepad ++ and not the builtin notepad or wordpad program. It would be a good idea to make a backup of the file before you modify it, just in case.
I did just that easiest method for me just loaded the sd card into my PC used notepad++ to edit the "cmdline.txt" file added logo.nologo quiet WORKS PERFECTLY !!
BIG Thanks to Favdeacon & progets as I now have exactly what I wanted a single load rom on the rpi3b+ with no garbage in the start and a clean safe shutdown in the end. My last to do should be rather simple I just need to add BIOS's for games that might need it in the future & SAMPLES for sound being I'm using .78 set of MAME. I plan on keeping all the set on the sd card this way all I need to do is basically in place of say TMNT I just need to rename it to a different ROM file and in theory should work. Outside of that I'll just need to hit TAB in MAME to map the keys according to whatever game I build simply brilliant ! I would share my image but IF any one follows this thread its VERY easy to get this going. I noticed that even though I'm not using the full 32gig card the .img file retains the 32gig size for whatever reason other wise I'd share it without the ROMs... but If anyone reads through this thread is so simple to set this up. Again some PCB's (original hardware) is very unreliable, pricey, upkeep etc etc... this is such a great way to create a "dedicated" reliable single clean one ROM launch as if it were the original machine.
I didn't test it yet but the only one I might see having trouble with this is possibly Daphne / Dragon's Lair ? I've gotten it working on my ATTRACT MODE setup with my thousands of games build but a single launch with that might be more involved, I don't know. I own an original Cinematronics Dragon's Lair with a Laser Disc player, they will eventually have disc rot etc, this is really good way to preserve these games for future players. However I don't even want to think about what's involved with getting the score board to function with it etc ...
-
Good to know that it worked. :) And you learned some things along the way that empower you to modify your system to your needs. That wouldn't be the case if you just downloaded a premade image someone else created. (Yeah, I'm preaching a bit about doing things ourselves. 8) ) And you will still get official support in the Retropie forum if you ever need it, since you used the official image.
I plan on keeping all the set on the sd card this way all I need to do is basically in place of say TMNT I just need to rename it to a different ROM file and in theory should work.
To change the game that is loaded at boot? Yes, or you could make one line for each game in the autostart.sh and enable/disable them via prefixed "#" characters, or you could make multiple autostart.sh files (e.g. autostart.tmnt, autostart.pacman, etc.) and copy them to autostart.sh. The latter would be done in the console like this:
cp /opt/retropie/configs/all/autostart.tmnt /opt/retropie/configs/all/autostart.sh
You could even make little scripts to do that:
mkdir /home/pi/bin # create a directory named "bin" in user pi's home dir, this is needed only once
echo "/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ arcade '/home/pi/RetroPie/roms/arcade/tmnt.zip'" > /opt/retropie/configs/all/autostart.tmnt
echo "cp /opt/retropie/configs/all/autostart.tmnt /opt/retropie/configs/all/autostart.sh" > /home/pi/bin/tmnt
chmod u+x /home/pi/bin/tmnt
From now on, you just have to type "tmnt" [enter] in the console to "enable" tmnt as the bootup game. 8) (I very much hope that I didn't make any typing errors. If so, feel free to throw it back into my face.)
I noticed that even though I'm not using the full 32gig card the .img file retains the 32gig size for whatever reason
That's because images are 1:1 copies of the whole storage medium. Some imaging programs can determine unused blocks and compress the image accordingly, but it would still be an image of the whole medium – just compressed.
other wise I'd share it without the ROMs... but If anyone reads through this thread is so simple to set this up.
I'm glad that you discovered this, and that I didn't drive you away by insisting that you better modify the official RP image. :D
I didn't test it yet but the only one I might see having trouble with this is possibly Daphne / Dragon's Lair ?
The emulator Daphne is a little tricky to set up. A good place to start would be – again – the official RetroPie Docs:
https://retropie.org.uk/docs/Daphne/
Have fun with your emulation rig. But be warned, they tend to be like model railways that will never be truly finished. ;D
-
I forgot what program I used back in the day but essentially it creates a list of the file names such as that of notepad / .txt file of everything that's in the folder aka just the ROM folder. This would be helpful because a .txt file takes up virtually no room. Also it's been a hot minute since I've used say Clrmame or one of those RomLister programs but that would REALLY be what I would want so say I have a little over 2,000 ROMs in the folder .zip files what ever & say "bublbobl.zip" it would create a .txt file that would say;
Bubble Bobble - bublbobl.zip
[insert game title here] - gamename.zip
[insert game title here] - gamename.zip
[insert game title here] - gamename.zip
I found this website extremely helpful with .zip names version changes etc... http://adb.arcadeitalia.net/default.php
but ideally I'd want to run said program to create a simple .txt file without having to cross reference the internet / a website I can just hit ctrl+F to find whatever game title which I need to name the corresponding .zip to have it as that single load ROM. The other reason why I'd like to create my own .txt file matching the game names to the .zip of the Rom is I removed most of the clones.
Also to note as opposed to plugging in the sd Card into a Pi, powering on the pi, using WinSCP to modify the autostart.sh.... In other words is it possible to view / and modify autostart.sh if I just use my PC / sd card adapter ?
-
Also to note as opposed to plugging in the sd Card into a Pi, powering on the pi, using WinSCP to modify the autostart.sh.... In other words is it possible to view / and modify autostart.sh if I just use my PC / sd card adapter ?
Not without third-party software that can read Linux' ext4 filesystems. Windows itself can't read or write ext4 natively.
That said, you could use a so-called Live System (https://en.wikipedia.org/wiki/Live_USB) that boots a modern Linux Desktop from a USB Stick or DVD. Many popular Linux distributions have installation images that include a Live mode, e.g. all of the Ubuntu variants. The Live system runs only from the stick or DVD, so your Windows on your hard drive will remain untouched. But since Linux can read and write Windows file systems for over ten years now, you could use a Live system to access your Retropie card as well as your Windows hard drive, and copy data between them.
One obstacle worth noting is that the Windows to be accessed has to be shut down properly. The "fast startup" mode of Windows 8 + 10 doesn't umount the file system properly, and the Linux Live system can only access file systems that are completely shut down.
-
I went to switch it back to galaga.zip which the game loaded however prior it had a NAG screen which I'm well familar with in terms of the emulations is not 100% video accurate etc, I know it's here:
/opt/retropie/configs/all/
The option is:
mame2003-skip_warnings = "enabled"
I did this and I'm still seeing the NAG screen very annoying.
My "retroarch-core-options.cfg" file shows this:
cap32_autorun = "enabled"
cap32_Model = "6128"
cap32_Ram = "128"
fba-diagnostic-input = "Hold Start"
fuse_machine = "Spectrum 128K"
gambatte_gb_colorization = "custom"
mame2003-skip_disclaimer = "enabled"
mame2003-dcs-speedhack = "enabled"
mame2003-samples = "enabled"
mame2003-frameskip = "0"
mame2003-skip_warnings = "enabled"
mame2003-sample_rate = "48000"
mame2003-external_hiscore = "disabled"
mame2003-dialsharexy = "disabled"
mame2003-mouse_device = "mouse"
mame2003-crosshair_enabled = "enabled"
mame2003-rstick_to_btns = "enabled"
mame2003-tate_mode = "disabled"
mame2003-skip-rom-verify = "disabled"
mame2003-vector-resolution-multiplier = "1"
mame2003-vector-antialias = "disabled"
mame2003-vector-translucency = "enabled"
mame2003-vector-beam-width = "1"
mame2003-vector-flicker = "20"
mame2003-vector-intensity = "1.5"
I tried changing the text / from disabled to enabled etc , It shows the changes using notepad++ or with modifying it with WinSCP. I turn the game back on to see the same stupid NAG screen! I drag and drop "retroarch-core-options.cfg" from my desk top to replace the file, relaunch the pi, same NAG screen still shows soooo annoying. Whatever I do I can't seem to prevent it from displaying.
I did however switch it to The Simpsons ala changing the autostart.sh to it's zip file name "simpsons.zip" and that loaded up fine because it doesn't have any known issues with the game. I'm just doing preventative maintenance so that in the future when I "write" the micro SD card over and over again I'm trying to avoid any issues I would run into. On my Attract-Mode build where I have tons of games It doesn't have the issue I don't know why it's not working on this single load image I created, luckily most of the .78 set doesn't have major issues with it.
-
Is there another file retroarch-core-options.cfg in the directory /opt/retropie/configs/mame-libretro/? If so, check it for the option, too. It would override the cfg file in the …/configs/all directory.
-
Only thing I see under /opt/retropie/configs/mame-libretro is;
emulators.cfg & retroarch.cfg
within retroarch.cfg shows this:
# Settings made here will only override settings in the global retroarch.cfg if placed above the #include line
input_remapping_directory = "/opt/retropie/configs/mame-libretro/"
#include "/opt/retropie/configs/all/retroarch.cfg"
IF i go back to the path; /opt/retropie/configs/all it's not saving the setting for whatever reason, I agree with you somethings overriding it. the file currently shows;
cap32_autorun = "enabled"
cap32_Model = "6128"
cap32_Ram = "128"
fba-diagnostic-input = "Hold Start"
fuse_machine = "Spectrum 128K"
gambatte_gb_colorization = "custom"
mame2003-skip_disclaimer = "enabled"
mame2003-dcs-speedhack = "enabled"
mame2003-samples = "enabled"
mame2003-frameskip = "0"
mame2003-skip_warnings = "disabled"
mame2003-sample_rate = "48000"
mame2003-external_hiscore = "disabled"
mame2003-dialsharexy = "disabled"
mame2003-mouse_device = "mouse"
mame2003-crosshair_enabled = "enabled"
mame2003-rstick_to_btns = "enabled"
mame2003-tate_mode = "disabled"
mame2003-skip-rom-verify = "disabled"
mame2003-vector-resolution-multiplier = "1"
mame2003-vector-antialias = "disabled"
mame2003-vector-translucency = "enabled"
mame2003-vector-beam-width = "1"
mame2003-vector-flicker = "20"
mame2003-vector-intensity = "1.5"
which clearly needs to say "enabled" it keeps reverting back to disabled regardless of what I do.
-
Did you try to edit it on the Pi itself by nano /opt/retropie/configs/all/retroarch.cfg ?
-
Did you try to edit it on the Pi itself by nano /opt/retropie/configs/all/retroarch.cfg ?
No I don't really like to edit / make any changes that way, I lack the Pi confidence... Again so far for the games I'm using it for I haven't ran into an issue however this for would be nice to clear that dumb screen. I know how to do it I just don't understand why it isn't saving the setting. I can get back into Emulation Station if it can be done that way, I think that's how I did it on my other "Attract Mode" many roms build I can't remember.
-
Did you try to edit it on the Pi itself by nano /opt/retropie/configs/all/retroarch.cfg ?
No I don't really like to edit / make any changes that way, I lack the Pi confidence...
Yet, it may help to diagnose and/or solve the problem, in case something is wrong with the other methods. nano is just a text editor for the console, like Notepad. So, the above command doesn't do anything you didn't do before by editing the file with Notepad, or overwrite it with an edited version using WinSCP.
Alternatively, you could install an ssh client for Windows, log into your pi (like WinSCP does) via ssh, and use nano this way from your PC.
edit: Another alternative to see if the file is written correctly would be to just show its contents on the Pi itself by this command:
less /opt/retropie/configs/all/retroarch.cfg
In less, you can browse the file with the cursor keys and PgUp/Down, and exit with "q".
As always, I'm not trying to force you to do anything, just giving suggestions that I think might help. :)
Again so far for the games I'm using it for I haven't ran into an issue however this for would be nice to clear that dumb screen. I know how to do it I just don't understand why it isn't saving the setting. I can get back into Emulation Station if it can be done that way, I think that's how I did it on my other "Attract Mode" many roms build I can't remember.
I think that Emulation Station won't help in this case, because the option Skip Warnings in part of RetroArch's core options you can only access via RA's configuration menu when the particular core (here: MAME) is loaded, i.e. a MAME game is running. The standard button combination to access the RA menu is "Select + B" – if you set the "Hotkey" in Emulation Station to be the same button as "Select" (as most people do, it is a kind-of-standard).
In the RA menu, the option Skip Warnings is located in the Quick Menu, in its submenu Options (Quick Menu > Options > Skip Warnings). Maybe it helps to set it there.
-
Just my 2 cents but why are you even using the runcommand if you're not using ES (EmulationStation) or AM (Attract-Mode)? Why not modify your autostart.sh to natively launch RA (RetroArch) and then you can use the "-c" switch to specify the retroarch.cfg file which has the "mame2003-skip_warnings = "disabled"" entry? By using the RP (RetroPie) launching scripts you're just mudding the water and making things more complex due to their structured .cfg file hierarchy.
I'll also mention that by default, RA disables saving changes to its config file. To change this you need to modify RA either manually through the retroarch.cfg file or using the RA GUI.
retroarch.cfg
config_save_on_exit = "true"
-
Just my 2 cents but why are you even using the runcommand if you're not using ES (EmulationStation) or AM (Attract-Mode)?
Short answer: Because I told him to. ;) But I didn't have any particular reason for that besides familarity on my side, and because ES provides an easy way to configure the controls once for most RetroPi emulators (mainly all RA cores).
BUT that said, there's no real reason to not just start RA directly.
I'll also mention that by default, RA disables saving changes to its config file. To change this you need to modify RA either manually through the retroarch.cfg file or using the RA GUI.
I don't like this option very much, since it's easy to save messed-up configurations after playing around with the options. I use the manual saving function of the RA menu instead, to protect me from my own daftness.
Just my 2 cents in addition to yours. :)