RetroFE forums
General Category => Announcements => Topic started by: Pieter Hulshoff on May 28, 2017, 08:34:18 AM
-
I've just received a Pi3 yesterday, and hope to create a nice SD-Card image for it using RetroFE. I'd like some input on what kind of features people would like to see in such a setup. Any thoughts?
-
I've just received a Pi3 yesterday, and hope to create a nice SD-Card image for it using RetroFE. I'd like some input on what kind of features people would like to see in such a setup. Any thoughts?
Have a look at the hyperpie images or motionblue for example. They combine retropie with attractmode. I would love a retropie setup with RetroFE.
Verstuurd vanaf mijn SM-G930F met Tapatalk
-
Looks like we could really use that setup tool. 😀
Sent from my SM-G920F using Tapatalk
-
Looking forward to it
-
Hai there,
Also looking foward to iT;-)
A software / hardware shutdown would be nice.
A gpio control for joy and buttons ( maybe a soft Power off and on)
A hotkey combi for enter retroFE?
Greets,
Ger
-
A software / hardware shutdown would be nice.
A gpio control for joy and buttons ( maybe a soft Power off and on)
A hotkey combi for enter retroFE?
Software shutdown is easy; I already have that in my Linux setup. :)
GPIO is on the to-do list for sure; I've received some buttons and an arcade joystick to see if I can use the GPIO as keyboard encoder.
What do you mean with a hotkey combi? The idea is to boot directly to RetroFE so it can be used in an arcade/console setup.
-
What I mean is, if you want to change a setting in a NON RetroFE setting(like mame or a other emulator). You Can switch between them. In retropie is this not possible if you make it attractmode. And that is not user friendly.
Greets,
Ger.
-
What I mean is, if you want to change a setting in a NON RetroFE setting(like mame or a other emulator). You Can switch between them. In retropie is this not possible if you make it attractmode. And that is not user friendly.
Easiest would probably be to make the quit key go back to the desktop, while the shutdown option turns off the system.
-
I can help with testing the image once you get that far
Sent from my SM-G920V using Tapatalk
-
Neither ld-mame2003 nor mame 0.185 are very fast on my Pi3 at the moment (pacman topping at 50% without frame skip at 1200 MHz). I think I'll have a look at Retropie to see if it's a matter of having the right configuration settings...
-
Apparently you're not supposed to run them under x... Time to give Retropie a whirl.
Sent from my SM-G920F using Tapatalk
-
If you are giving RetroPie a try, I have been developing an experimental RetroPie module for installing RetroFE. My goal is configure it to use the standard RetroPie filesystem layout, config settings, and use of the runcommand.sh script for launching. It should be a full replacement or complementary install to EmulationStation. I'd be happy to share it later this weekend if you would like to try it out.
My only challenge is that I don't have access to my RPi3 right now, so I am developing against the x86/Ubuntu/X11 flavor of RetroPie. There could be some minor differences that I can't test yet. However, if you could just confirm the exact list of package dependencies for installing RetroFE on RetroPie, that should be enough to get things up and running. I know that the package list used in the compilation instructions isn't correct - several SDL libraries need an extra "-0" tacked on the end for the x86 version, and I believe change are needed for the Pi too.
-
I'm not there yet, but I'd love a copy of your work to test. I only just received a pi3, so I'm still learning.
Sent from my SM-G920F using Tapatalk
-
I have been using RetroFE on a Pi for about a year. It once worked pretty well and was able to use the RetroPie "runcommand" which is ideal. Over the past year there have been changes making it harder and harder to work with my RetroPie build. First, the "runcommand" option for the launcher.confs seemed to break so I went to my own command line launching of the emulators in the launcher.confs. Second, the RetroArch GL video driver stopped working properly so I need to reference separate retroarch.cfg files in RetroFe to use the SDL2 video drivers. Third, on the latest build I can't seem to get the emulators to launch with focus, they are always behind RetroFE regardless of the "fullscreen" or "fullscreen windowed" options in RetroArch.
I hope to see you getting something running well on the Pi and I'm willing to help. Lately, I have opted for another FE on my Pi since it's very stable and works great on the cheap hardware.
-
Are these changes in RetroFE or changes in the Retropie image that caused these problems?
Sent from my SM-G920F using Tapatalk
-
To be honest, I'm not sure. It could also be changes in RetroArch since that's used for most things on the Pi. In the past year its had many upgrades too. I'm willing to bet that it's a combination of everything (Raspbian, RetroFE, RetroPie and RetroArch).
Not to sound like a jerk but AM (Attract-Mode) is king on the Pi right now. EmulationStation (the default RetroPie FE) has limited development and only recently supported videos. I will even go on to say that using the newer "experimental" Attract-Mode install from RetroPie is less than ideal. RetroPie and a separate AM (+ SFML, ffmpeg, etc.) works much better.
I recognize you from the HyperSpin forums. I've been into emulation for a while. I think we are part of a small group that actually plays with emulation on both Windows and Linux. The Pi is even a separate Linux breed due to it's limited power.
I'll also mention that if the RetroPie "runcommand" works in RetroFe you'll be able to directly access the RetroPie setup/config menus without having to go into EmulationStation. This is almost a must for most people and can be done in AM today.
BTW - You might look at the old forum where you can see my posts about Pi issues and solutions. I can also provide main settings.conf and systems settings.conf for a RetroPie build as well as launcher.conf for direct command line and/or RetroPie "runcommand".
-
No worries, the truth shall set you free. 😀 If AM is currently better on the pi, then I guess I have some work to do. As said: I'm new to the pi, so I've got some experiments to run, and figure this thing out. Then I can focus on improving things, and fixing bugs. 😀
Sent from my SM-G920F using Tapatalk
-
Always love your "can do" attitude! Let me know if I can help in any way.
-
Well, any links to handy tutorials would save me some searching time. 😀 Time's the thing I'm lacking most in life.
Sent from my SM-G920F using Tapatalk
-
To make your FE ideal for a Pi I think you need to base it on RetroPie. No tutorial, download the latest RetroPie image https://retropie.org.uk/download/ (https://retropie.org.uk/download/)and then compile RetroFE on top and get it to work. I'll help with any configs. It should be super easy to see and have the FE working right. Emulators might be a bigger issue.
-
Retropie comes with several installed emulators though, right? If its launchable from the commandline, RetroFE should be able to handle it or I can write scripts to make it work...
Sent from my SM-G920F using Tapatalk
-
To me, the only major challenge in achieving a full RetroPie integration is the naming convention. RetroPie filesystems and configs use a "shortname" system naming convention ("Super Nintendo Entertainment System" = "snes", and so on). RetroFE (seems) to prefer a long name for the metadata input files, plus most of the preexisting collection assets and configs. Personally, I prefer the long names, as I standardized on HyperSpin/RocketLauncher names a long time ago, and I prefer to keep that consistent across various build.
My approach to solving this (for now) is a mapping file that translates long names to short names. Similar to EmulationStation on RetroPie, I have created a wrapper script in /usr/bin for launching RetroFE. The wrapper reads the mapping file at launch time, and updates the collection settings.conf files to change the long names to short names. From there, everything pretty much works. I also have a single launcher for run command.sh. All of this gets set up by the RetroPie module at the time of build/install/update.
All of this can easily be configured manually, but I've been trying to come up with a solution that keep existing RetroPie and RetroFE documentation valid...and isn't too much of a hack. Maybe some will think that's what this is, but hey...it's a starting point. If folks have better ideas, I'm interested - at least I now I have a better understanding of how the RetroPie internals work so we can try and keep native integration.
-
I use the default RetroPie setup and just point RetroFE to the correct places. This allows you to have the full names that RetroFE uses but the default folders RetroPie uses. Here are some examples.
Main settings.conf (point the baseItemPath to /home/pi/RetroPie/roms)
##############################################################################
#
# For support, visit www.retrofe.com
# or visit irc.foreverchat.net (channel #retrofe)
#
# For Documentation, visit www.retrofe.com/documentation
#
##############################################################################
#######################################
# Display
#######################################
fullscreen = no
horizontal = stretch # or enter in the screen pixel width (i.e 1024)
vertical = stretch # or enter in the screen pixel width (i.e 768)
layout = Aeon Nox
hideMouse = yes
showParenthesis = no
showSquareBrackets = no
# specify the name of the first collection to load on start
firstCollection = Main
# specify whether RetroFE should switch to Favorites list if it exists.
autoFavorites = false
#######################################
# Video playback settings
#######################################
# set to "no" for very old/slow systems
videoEnable = yes
# Number of times to loop video playback (enter 0 to continuously loop)
videoLoop = 0
#######################################
# General
#######################################
# exit the frontend when the back button is pressed on the first page
exitOnFirstPageBack = yes
# enter 0 attract mode, otherwise enter the number of seconds to wait before enabling attract mode
attractModeTime = 45
# remember the last highlighted menu when re-entering a menu
rememberMenu = no
#######################################
# Base folders of media and ROM files
#######################################
# Override if you choose to have your media stored outside of RetroFE.
# If this is commented out your artwork will be searched in collections/<collectionname>/<imagetype>
# baseMediaPath=d:/media
# Override if you choose to have your ROMs stored outside of RetroFE.
# If this is commented out your roms will be searched in collections/<collectionname>/roms
baseItemPath = /home/pi/RetroPie/roms
Nintendo Entertainment System settings.conf (point paths to RetroPie folders)
# Uncomment and edit the following line to use a different ROM path.
list.path = %BASE_ITEM_PATH%/nes
list.includeMissingItems = false
list.extensions = nes,smc,sfc,fig,swc,mgd,zip
list.menuSort = yes
launcher = Nintendo Entertainment System
media.screenshot = %BASE_ITEM_PATH%/nes/snap
media.screentitle = %BASE_ITEM_PATH%/nes/title
media.artwork_back = %BASE_ITEM_PATH%/nes/boxart_back
media.artwork_front = %BASE_ITEM_PATH%/nes/boxart
media.logo = %BASE_ITEM_PATH%/nes/wheel
media.medium_back = %BASE_ITEM_PATH%/nes/cartart_back
media.medium_front = %BASE_ITEM_PATH%/nes/cartart
media.video = %BASE_ITEM_PATH%/nes/video
media.story = %BASE_ITEM_PATH%/nes/story
Nintendo Entertainment System.conf launcher using RetroPie runcommand
executable = /opt/retropie/supplementary/runcommand/runcommand.sh
arguments = 0 _SYS_ nes "%ITEM_FILEPATH%"
Nintendo Entertainment System.conf launcher without using RetroPie runcommand
executable = /opt/retropie/emulators/retroarch/bin/retroarch
arguments = -L /opt/retropie/libretrocores/lr-fceumm/fceumm_libretro.so "%ITEM_FILEPATH%"
-
My (WIP) RetroPie module for RetroFE is attached. Copy this file to ~/RetroPie-Setup/scriptmodules/supplementary/ .
To install, run ~/RetroPie-Setup/retropie_setup.sh , then go to Manage packages | Manage experimental packages | retrofe (should be near the end of the list).
Once installed, the full set of retroFE configs is accessible via RetroPie's "config/all/retrofe" samba share for easy management.
The version I am attaching should provide a full build, install/remove, and basic configuration of RetroFE. It does not do any of the automatic mapping of system/platform names that I mentioned earlier. However, it does create a custom launcher for each of the systems that RetroPie supports out of the box. Therefore, to get a collection up and running, I recommend the following minimal changes to the collection's settings.conf:
list.path = /home/<username>/RetroPie/roms/<platform shortname>/
launcher = <platform shortname>
For example, to enable the sample Sega Genesis collection that comes with the retroFE build, you would substitute <platform shortname> above with megadrive. You will also need to copy files into RetroPie's "roms/megadrive" samba share, since the above config is using the standard RetroPie location, and not the roms directory within the RetroFE collection.
I look forward to any feedback!
-
Thanks. 😀 I will check it out soon
Sent from my SM-G920F using Tapatalk
-
I managed to play Super Mario World on Retropie with scanlines: not bad at all. :) Play was smooth. I guess the next step is to install RetroFE, and get cracking...
-
My retropie does not have the libgstreamer-plugins-good1.0-dev package, and throws an error... I can compile without, but it won't play video. 😭
-
Slowly getting there; RetroFE is running with video and sound now. 😀
Sent from my SM-G920F using Tapatalk
-
I share your focus issue for launching games; I've had these issues before, but haven't found a solution on the pi yet.
Sent from my SM-G920F using Tapatalk
-
Out of curiosity, did you use the RetroPie module, or are you playing on your own?
Sent from my iPad using Tapatalk
-
I used your module, but had to make a few small changes so far to make it work.
Sent from my SM-G920F using Tapatalk
-
MAME2016 core works well; just need to figure out how to get that launching fixed. I may need to kill off the SDL window before launch, but I'd prefer not to.
Sent from my SM-G920F using Tapatalk
-
I've launched a few questions on the boards to figure out how to do this. The problem is that if I have to destroy the renderer and window, I also have to destroy all textures created for that renderer, and then recreate them when the game returns, and in that case also do that for other pages on the stack. It's quite a code change to do that, so I'd rather first try to see if there's a way around this without breaking everything down. :) That's even aside from the fact that it's not a very pretty solution, because it briefly shows what's behind the front-end before and after launching the game. If anyone has a suggestion while I try to get answers from elsewhere, please let me know. :)
-
Outside of the launching issues you are working through (can you share the thread you posted to?), could you please let me know what other changes you made to the module to get up & running to your liking? I can update it accordingly...
-
Outside of the launching issues you are working through (can you share the thread you posted to?), could you please let me know what other changes you made to the module to get up & running to your liking? I can update it accordingly...
I'll upload the script soon; it's just a small change to installed packages: the plugin change, and I added alsa support (to get sound in video). I'm still playing around with the C++ code to see if I can solve the launch issues.
https://discourse.libsdl.org/t/program-launched-from-sdl-program-is-launched-behind-the-sdl-program/22628/2
https://raspberrypi.stackexchange.com/questions/68383/emulator-launches-behind-sdl-front-end
https://retropie.org.uk/forum/topic/11002/adding-retrofe-emulator-launches-behind-the-front-end
It is my intention to add default launchers for all supported emulators in the bitbucket repository before this is done so they can simply be added to the installation by the script. First though I need to figure out how to actually properly launch an emulator. :)
-
Are you using launchers that invoke the runcommand.sh script? Or did you configure one that calls an emulator directly? If you are bypassing run command, that could be where the problem is coming from.
Unfortunately, I still don't have my Pi to help troubleshoot with you. I might be able to get it back this weekend.
-
One other thing...I saw in the other threads that you wanted to see if auto booting into RF would help. You can change from ES to RF by editing /opt/Retropie/config/all/autostart.sh. If that file doesn't exist for some reason, you can also enable/disable/edit the autostart through RetroPie-Setup. It is the 2nd option under "Configuration/Tools".
-
Thanks, I will give both things a closer look. I'm not familiar with the run command, so I'll have to look into that.
Ah, this may help: http://www.retrofe.com/forum/index.php?topic=427.0
-
Yes, that kind of configuration is essentially what my module script sets up. If you haven't already done so, try setting up a collection to use the launchers that should have been created on a per-system basis. You will see that those launchers use runcommand.sh
Ah...I also see the note about configuring RetroFE to use the SDL2 driver...maybe that helps too. Let us know!
-
Thanks, I will give both things a closer look. I'm not familiar with the run command, so I'll have to look into that.
Ah, this may help: http://www.retrofe.com/forum/index.php?topic=427.0
This link doesn't work for me.
I followed the links to your posts above and saw you asking about directly booting RetroFE and hiding boot text. You can modify the /opt/Retropie/config/all/autostart.sh file as MisterB suggests to boot to RetroFE. Here's how to hide the boot text https://github.com/retropie/retropie-setup/wiki/FAQ#how-do-i-hide-the-boot-text.
-
Thanks, I will give both things a closer look. I'm not familiar with the run command, so I'll have to look into that.
Ah, this may help: http://www.retrofe.com/forum/index.php?topic=427.0
This link doesn't work for me.
I followed the links to your posts above and saw you asking about directly booting RetroFE and hiding boot text. You can modify the /opt/Retropie/config/all/autostart.sh file as MisterB suggests to boot to RetroFE. Here's how to hide the boot text https://github.com/retropie/retropie-setup/wiki/FAQ#how-do-i-hide-the-boot-text.
The link isn't working, because the old site is down; I made sure to save a copy on my computer before this happened. :)
I already had a closer look, but unless I want to change the video driver for all the emulators I guess I'll have to properly break down the SDL layers like EmulationStation does. I guess I'd better take care of that. :)
Thanks for the link; I'll have a closer look, and work on that as well. I want the RetroFE installation script to take care of all these things, so that after it's complete you'll have a fully operational RetroFE setup.
I did notice though that RetroPie does not look kindly upon people hosting their work elsewhere, so I'll have to see how best to handle that. Perhaps just an installation script with instructions, combined with a link to their site, and hopefully integration into a next version would be best.
-
I think adding onto RetroPie via a script makes the most sense. It won't rub anyone the wrong way and it will also allow people using SD images (I dislike this) to try the FE.
Why not leverage the original script as a base and install the same way - "bash <(curl -s https://bitbucket.org/teamretro/retrofe/raw/default/Scripts/Raspi2/install.sh)"? Getting built into a future release of RetroPie might be good but in the case of Attract-Mode, it's less than desirable.
I'll post a couple of the scripts that I made for my RetroPie to Attract-Mode migration with a twist to support RetroFE. They should be similar to some of the things you might want for RetroFE.
DB_From_HS.sh
wget http://hyperlist.hyperspin-fe.com/genall.php?system=311 -O "/home/pi/retrofe/meta/hyperlist/Atari 2600.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=1 -O "/home/pi/retrofe/meta/hyperlist/Atari 5200.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=31 -O "/home/pi/retrofe/meta/hyperlist/Atari 7800.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=2 -O "/home/pi/retrofe/meta/hyperlist/Atari Lynx.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=6 -O "/home/pi/retrofe/meta/hyperlist/MAME.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=16 -O "/home/pi/retrofe/meta/hyperlist/NEC TurboGrafx-16.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=44 -O "/home/pi/retrofe/meta/hyperlist/Nintendo 64.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=316 -O "/home/pi/retrofe/meta/hyperlist/Nintendo Entertainment System.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=125 -O "/home/pi/retrofe/meta/hyperlist/Nintendo Game Boy.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=35 -O "/home/pi/retrofe/meta/hyperlist/Nintendo Game Boy Advance.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=124 -O "/home/pi/retrofe/meta/hyperlist/Nintendo Game Boy Color.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=14 -O "/home/pi/retrofe/meta/hyperlist/Sega 32X.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=56 -O "/home/pi/retrofe/meta/hyperlist/Sega CD.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=48 -O "/home/pi/retrofe/meta/hyperlist/Sega Dreamcast.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=302 -O "/home/pi/retrofe/meta/hyperlist/Sega Game Gear.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=319 -O "/home/pi/retrofe/meta/hyperlist/Sega Genesis.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=308 -O "/home/pi/retrofe/meta/hyperlist/Sega Master System.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=319 -O "/home/pi/retrofe/meta/hyperlist/Sega Genesis.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=309 -O "/home/pi/retrofe/meta/hyperlist/Sony PlayStation.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=310 -O "/home/pi/retrofe/meta/hyperlist/Sony PSP.xml"
wget http://hyperlist.hyperspin-fe.com/genall.php?system=303 -O "/home/pi/retrofe/meta/hyperlist/Super Nintendo Entertainment System.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Atari 2600.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Atari 5200.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Atari 7800.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Atari Lynx.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/MAME.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/NEC TurboGrafx-16.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Nintendo 64.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Nintendo Entertainment System.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Nintendo Game Boy.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Nintendo Game Boy Advance.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Nintendo Game Boy Color.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Sega 32X.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Sega CD.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Sega Dreamcast.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Sega Game Gear.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Sega Master System.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Sega Genesis.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Sony PlayStation.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Sony PSP.xml"
attract -i "/home/pi/retrofe/meta/hyperlist/Super Nintendo Entertainment System.xml"
Menu_Plus_Setup.sh
mkdir /home/pi/RetroPie/roms/setup
cat >> /home/pi/RetroPie/roms/setup/EmulationStation.sh << EOF
clear
echo "Switching default boot system to EmulationStation and rebooting"
echo ""
sed -i 's/attract/emulationstation/g' /opt/retropie/configs/all/autostart.sh
sudo reboot
EOF
cat >> /home/pi/RetroPie/retropiemenu/Attract-Mode.sh << EOF
echo "Switching default boot system to Attract-Mode and rebooting"
echo ""
sed -i 's/emulationstation/attract/g' /opt/retropie/configs/all/autostart.sh
sudo reboot
EOF
chmod +x /home/pi/RetroPie/retropiemenu/Attract-Mode.sh
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/audiosettings.rp >> "/home/pi/RetroPie/roms/setup/Audio Settings.sh"
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/bluetooth.rp >> /home/pi/RetroPie/roms/setup/Bluetooth.sh
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/configedit.rp >> "/home/pi/RetroPie/roms/setup/Configuration Editor.sh"
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/wifi.rp >> "/home/pi/RetroPie/roms/setup/Configure Wifi.sh"
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/filemanager.rp >> "/home/pi/RetroPie/roms/setup/File Manager.sh"
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/raspiconfig.rp >> "/home/pi/RetroPie/roms/setup/Raspberry Pie Setup.sh"
echo sudo reboot >> /home/pi/RetroPie/roms/setup/Reboot.sh
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/retroarch.rp >> "/home/pi/RetroPie/roms/setup/Retroarch Setup.sh"
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/retronetplay.rp >> "/home/pi/RetroPie/roms/setup/Retroarch Netplay.sh"
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/rpsetup.rp >> "/home/pi/RetroPie/roms/setup/RetroPie Setup.sh"
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/runcommand.rp >> /home/pi/RetroPie/roms/setup/RunCommand.sh
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/showip.rp >> "/home/pi/RetroPie/roms/setup/Show IP Address.sh"
echo sudo poweroff >> /home/pi/RetroPie/roms/setup/Shutdown.sh
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/splashscreen.rp >> "/home/pi/RetroPie/roms/setup/Splash Screen.sh"
mkdir /home/pi/RetroPie/roms/setup/box
mkdir /home/pi/RetroPie/roms/setup/cart
mkdir /home/pi/RetroPie/roms/setup/box
mkdir /home/pi/RetroPie/roms/setup/marquee
mkdir /home/pi/RetroPie/roms/setup/snap
mkdir /home/pi/RetroPie/roms/setup/video
mkdir /home/pi/RetroPie/roms/setup/wheel
cp /home/pi/RetroPie/retropiemenu/icons/audiosettings.png "/home/pi/RetroPie/roms/setup/snap/Audio Settings.png"
cp /home/pi/RetroPie/retropiemenu/icons/bluetooth.png /home/pi/RetroPie/roms/setup/snap/Bluetooth.png
cp /home/pi/RetroPie/retropiemenu/icons/configedit.png "/home/pi/RetroPie/roms/setup/snap/Configuration Editor.png"
cp /home/pi/RetroPie/retropiemenu/icons/wifi.png "/home/pi/RetroPie/roms/setup/snap/Configure Wifi.png"
cp /home/pi/RetroPie/retropiemenu/icons/filemanager.png "/home/pi/RetroPie/roms/setup/snap/File Manager.png"
cp /home/pi/RetroPie/retropiemenu/icons/raspiconfig.png "/home/pi/RetroPie/roms/setup/snap/Raspberry Pie Setup.png"
cp /home/pi/RetroPie/retropiemenu/icons/retroarch.png "/home/pi/RetroPie/roms/setup/snap/Retroarch Setup.png"
cp /home/pi/RetroPie/retropiemenu/icons/retronetplay.png "/home/pi/RetroPie/roms/setup/snap/Retroarch Netplay.png"
cp /home/pi/RetroPie/retropiemenu/icons/rpsetup.png "/home/pi/RetroPie/roms/setup/snap/RetroPie Setup.png"
cp /home/pi/RetroPie/retropiemenu/icons/runcommand.png /home/pi/RetroPie/roms/setup/snap/RunCommand.png
cp /home/pi/RetroPie/retropiemenu/icons/showip.png "/home/pi/RetroPie/roms/setup/snap/Show IP Address.png"
cp /home/pi/RetroPie/retropiemenu/icons/splashscreen.png "/home/pi/RetroPie/roms/setup/snap/Splash Screen.png"
chmod +x /home/pi/RetroPie/roms/setup/*.sh
wget http://attractmode.org/images/logo.png
mv logo.png /home/pi/RetroPie/retropiemenu/icons/Attract-Mode.png
cat >> /home/pi/.attract/emulators/Setup.cfg << EOF
# Generated by Attract-Mode v2.2.1
#
executable /bin/bash
args "[romfilename]"
rompath /home/pi/RetroPie/roms/setup
romext .sh
system Setup
artwork box /home/pi/RetroPie/roms/setup/box
artwork cart /home/pi/RetroPie/roms/setup/cart
artwork flyer /home/pi/RetroPie/roms/setup/box
artwork marquee /home/pi/RetroPie/roms/setup/marquee
artwork snap /home/pi/RetroPie/roms/setup/video;/home/pi/RetroPie/roms/setup/snap
artwork wheel /home/pi/RetroPie/roms/setup/wheel
EOF
sed -i '/\<sound\>/i \display Setup' /home/pi/.attract/attract.cfg
sed -i '/\<sound\>/i \ layout Basic' /home/pi/.attract/attract.cfg
sed -i '/\<sound\>/i \ romlist Setup' /home/pi/.attract/attract.cfg
sed -i '/\<sound\>/i \ in_cycle yes' /home/pi/.attract/attract.cfg
sed -i '/\<sound\>/i \ in_menu yes' /home/pi/.attract/attract.cfg
sed -i '/\<sound\>/i \ filter all' /home/pi/.attract/attract.cfg
sed -i '/\<sound\>/i \ ' /home/pi/.attract/attract.cfg
sed -i 's/window_mode default/window_mode fullscreen/g' /home/pi/.attract/attract.cfg
attract -b Setup
sed -i '/<\<gameList\>>/a \ </game>' /opt/retropie/configs/all/emulationstation/gamelists/retropie/gamelist.xml
sed -i '/<\<gameList\>>/a \ <image>./icons/Attract-Mode.png</image>' /opt/retropie/configs/all/emulationstation/gamelists/retropie/gamelist.xml
sed -i '/<\<gameList\>>/a \ <desc>Change system boot to the Attract-Mode frontend and reboot.</desc>' /opt/retropie/configs/all/emulationstation/gamelists/retropie/gamelist.xml
sed -i '/<\<gameList\>>/a \ <name>Attract-Mode</name>' /opt/retropie/configs/all/emulationstation/gamelists/retropie/gamelist.xml
sed -i '/<\<gameList\>>/a \ <path>./Attract-Mode.sh</path>' /opt/retropie/configs/all/emulationstation/gamelists/retropie/gamelist.xml
sed -i '/<\<gameList\>>/a \ <game>' /opt/retropie/configs/all/emulationstation/gamelists/retropie/gamelist.xml
sudo reboot
-
Thanks, I will give both things a closer look. I'm not familiar with the run command, so I'll have to look into that.
Ah, this may help: http://www.retrofe.com/forum/index.php?topic=427.0
BTW - Was this post from me (I know that I was trying to get people interested in the Pi on the old site)? If so, I might be able to give some insight. Can you re-post this?
-
Thanks, I will give both things a closer look. I'm not familiar with the run command, so I'll have to look into that.
Ah, this may help: http://www.retrofe.com/forum/index.php?topic=427.0
BTW - Was this post from me (I know that I was trying to get people interested in the Pi on the old site)? If so, I might be able to give some insight. Can you re-post this?
No, but you did participate in the dicussion. :)
-
Thanks, I will give both things a closer look. I'm not familiar with the run command, so I'll have to look into that.
Ah, this may help: http://www.retrofe.com/forum/index.php?topic=427.0
BTW - Was this post from me (I know that I was trying to get people interested in the Pi on the old site)? If so, I might be able to give some insight. Can you re-post this?
No, but you did participate in the dicussion. :)
Sorry, my mistake.
I think that you'll find most of my posts on the old site about the Pi if that helps you.
-
I guess I'm still a little confused about what everyone is trying to accomplish with the RetroPie integration. I agree that hosting a separately hosted RetroFE-based image is undesirable, but it's also unnecessary - that's where I was hoping my module/script would help out. The intention is submit it for formal incorporation into RetroPie, so that anyone could go into RetroPie-Setup and 'turn it on' - just the AttractMode, MehStation, and ES-Kids.
Progets - If you haven't tried it or looked at the source, running the install/update script will compile and install the latest RFE from BitBucket. The steps mimic what is in the old RPi script, plus more auto configuration to make RFE work well in a RetroPie environment. Are there other specific steps you believe the script should make? I guess I'm curious about the concerns you have with AttractMode being installed in via the RetroPie-Setup.
Pieter - With regards to your concerns about changing the video driver for the emulators, that could be inserted in the script as well - probably not the most elegant solution if you can prevent the need in the first place. But especially considering the majority of RetroPie pushes folks to RetroArch for emulation, that's a single config change that I could automate. Additionally, I could modify the autoboot settings as well - however, the RetroPie admins might not look kindly on that. That's a case where it might be netter to let people know that they should use the autobot config setting that is built into the setup tool.
At the end of the day, I think I've got things pretty close to usable and can script in any gaps. If you guys can provide some requirements for improving usability, I'd like to help.
-
Progets - If you haven't tried it or looked at the source, running the install/update script will compile and install the latest RFE from BitBucket. The steps mimic what is in the old RPi script, plus more auto configuration to make RFE work well in a RetroPie environment. Are there other specific steps you believe the script should make? I guess I'm curious about the concerns you have with AttractMode being installed in via the RetroPie-Setup.
I tried it and it didn't work for me. I didn't look into why or fixing it. Personally I could careless about any auto configuration, that's an easy one time thing (which I have already done). Really the biggest issue with RetroFE on the Pi is the emulators not launching with focus. This makes the frontend pretty useless.
The RetroPie Attract-Mode install sucks because it doesn't include hardware video decoding, it uses symbolic links that are different than a regular Attract-Mode install and it adds every system under the sun which I don't need or like. This makes updating AM or RetroPie a pain because every time you update either it puts back all the unwanted systems in to AM. It would be like needing to reconfigure RetroFE every time you update. By installing AM separately you can update RetroPie or AM without needing to reconfigure anything in AM. It also make getting support easier because people on the AM forums aren't expecting the changes that the RetroPie install has made.
-
My goal is to allow the easiest possible path to run RetroFE on the pi. From that perspective I thought that a separate SD image would be best, but from what I've learned a good install script would work just as well. I will also take the upgrade path into account.
I've already progressed quite a bit with the C++ code. It's working for me, but I want to do some more cleanups and tests before I check it into bit bucket. Once that's up and running, you should be able to run RetroFE on RetroPie without too much trouble; I'm sure you can handle the installation process for now while I work on a script that handles everything for users with less knowledge of the pi. :)
-
I've updated the code in bit bucket; please give this a try, and let me know if this works out for you. Don't forget to set unloadSDL = true in the settings.conf (default on the new settings.conf in bit bucket).
-
It needs gstreamer1.0 to compile retrofe. Once retrofe is running it is able to launch games with the RetroPie runcommand which is nice.
Videos seem slow but I need to test a little more.
-
It needs gstreamer1.0 to compile retrofe. Once retrofe is running it is able to launch games with the RetroPie runcommand which is nice.
Videos seem slow but I need to test a little more.
It did feel a bit slow here and there, but overall I think it works pretty well. Perhaps a theme should be used that only displays a single video rather than the two used in Aeon Nox. I also need to figure out a way to auto select a 16x9 or 4x3 theme depending on the screen resolution.
-
I tried the "Default 16x9" layout before my prior post. It could be my videos but they're the same ones I use in EmulationStation and Attract-Mode on the Pi. I'll test some more when I have time.
-
Just a quick update.
When I tested above I built a new SD card. I installed RetroPie from the 4.2 image, updated raspi-config, updated retropie, tried to install retrofe (failed), installed gstreamer1.0, deleted and reinstalled retrofe. The builtin videos (Arcade and Genesis) played ok but my videos didn't (they work fine in ES or AM).
I have copied off the retrofe folder from the new SD card and moved it to a different SD card with my personal retropie build. My videos do play ok here. I have tested the runcommand and non-runcommand launchers and both work on my build. I have to say retrofe works much better on my personal build than on a new build (this could be just video related).
On both builds retrofe maxes out the CPU when running the FE. In AM using ffmepg to hardware decode videos makes a huge difference in CPU use and Pi temp (about 20 degrees celsius). I don't know if this is an option for retrofe but when you're dealing with a Pi every little bit of CPU offloading helps.
For what it's worth, my Pi build is at RetroPie 4.2.3. The latest is at Retropie 4.2.8. I'm updating my image to see if it makes a difference but I doubt it will since my image is was updated less than 2 months ago.
-
Before I spend a lot of time looking into ffmpeg (a library I have little experience with), could you check if the 100% CPU is also used when video has been turned off? In other words: is it the video playing that causes this or is there a different cause for it?
With regards to videos not playing on a specific build: that's probably a decoder issue. I'm not sure which decoder those specific videos use...
-
I put a base retropie image on my sdcard. Will install retrofe tonight and test. Will need to dust off my linux know how again. ;)
Sent from my SM-G920V using Tapatalk
-
Before I spend a lot of time looking into ffmpeg (a library I have little experience with), could you check if the 100% CPU is also used when video has been turned off? In other words: is it the video playing that causes this or is there a different cause for it?
With regards to videos not playing on a specific build: that's probably a decoder issue. I'm not sure which decoder those specific videos use...
On my personal RetroPie build turning off the videos drops the CPU to around 80%. On a basic RetroPie build the CPU is stays at 100% even with the videos off.
All my videos are from emumovies. On the Pi I use the SD videos (because of space and performance). The videos use the h264 codec.
-
Ok, so videos only take 20%. How much impact does the theme have?
Sent from my SM-G920F using Tapatalk
-
Ok, so videos only take 20%. How much impact does the theme have?
Sent from my SM-G920F using Tapatalk
I updated my post above. On a basic build the CPU didn't drop.
Themes don't change the CPU use very much but do make a big difference using the FE.
-
So sorry if this seems like a linux n00b question. I ran the command:
bash <(curl -s https://bitbucket.org/phulshof/retrofe/raw/default/Scripts/Raspi2/install.sh)
but i am afraid I do not have a retrofe program to run. I type
./retrofe/Artifacts/linux/RetroFE/retrofe to start and doesnt exits. Checked the folder too.
./root/retrofe/Artifacts/linux/RetroFE/retrofe is the path on my pi. Anyway help is appreciated I am close to testing.
-
So sorry if this seems like a linux n00b question. I ran the command:
bash <(curl -s https://bitbucket.org/phulshof/retrofe/raw/default/Scripts/Raspi2/install.sh)
but i am afraid I do not have a retrofe program to run. I type
./retrofe/Artifacts/linux/RetroFE/retrofe to start and doesnt exits. Checked the folder too.
./root/retrofe/Artifacts/linux/RetroFE/retrofe is the path on my pi. Anyway help is appreciated I am close to testing.
You need gstreamer1.0 to compile retrofe.
You can run this before the retrofe install command you mention above
sudo apt-get install gstreamer1.0
-
Ok, so videos only take 20%. How much impact does the theme have?
Sent from my SM-G920F using Tapatalk
I've been playing around with my personal retropie build. I'm now using the "RAW" theme and it's pretty responsive. With videos turned on it uses 100% of the CPU. When I turn off the videos the same theme drops to only 20% CPU usage.
Retrofe video handling is extremely taxing on the Pi. The same videos play fine with little CPU change on other FEs on the Pi.
-
Sound like gstreamer isn't using the hardware then; I'll see if I can figure out which package is needed for that.
Sent from my SM-G920F using Tapatalk
-
I have all the RetroPie setup scripts running in RetroFE. This means you won't need to run ES when using RetroFE to make changes or updates. I also have Kodi launching from RetroFE.
I have everything on the Pi overclocked and it runs pretty well using the RAW theme. With videos enabled RetroFE is running around 60% CPU. I think that this can be tuned to make for a great Pi FE.
-
I'd welcome a copy; would save me some work. 😀
Sent from my SM-G920F using Tapatalk
-
I'd welcome a copy; would save me some work. 😀
Sent from my SM-G920F using Tapatalk
This can be done a few ways. It's just a matter of preference. Since my build is designed to run multiple FEs using a RetroPie base I like to put the scripts and artwork in the same place as the roms for any system (/home/pi/RetroPie/roms). This keeps it standardized and easy for me to know where everything is located. If you plan to only use RetroFE you might opt to place these things within the RetroFE structure.
That being said, this is how I'm doing it
cd <retrofe_directory>
nano retrofe_setup.sh
add this to the file and save it
mkdir /home/pi/RetroPie/roms/setup
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/audiosettings.rp >> "/home/pi/RetroPie/roms/setup/Audio Settings.sh"
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/bluetooth.rp >> /home/pi/RetroPie/roms/setup/Bluetooth.sh
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/configedit.rp >> "/home/pi/RetroPie/roms/setup/Configuration Editor.sh"
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/wifi.rp >> "/home/pi/RetroPie/roms/setup/Configure Wifi.sh"
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/filemanager.rp >> "/home/pi/RetroPie/roms/setup/File Manager.sh"
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/raspiconfig.rp >> "/home/pi/RetroPie/roms/setup/Raspberry Pie Setup.sh"
echo sudo reboot >> /home/pi/RetroPie/roms/setup/Reboot.sh
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/retroarch.rp >> "/home/pi/RetroPie/roms/setup/Retroarch Setup.sh"
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/retronetplay.rp >> "/home/pi/RetroPie/roms/setup/Retroarch Netplay.sh"
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/rpsetup.rp >> "/home/pi/RetroPie/roms/setup/RetroPie Setup.sh"
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/runcommand.rp >> /home/pi/RetroPie/roms/setup/RunCommand.sh
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/showip.rp >> "/home/pi/RetroPie/roms/setup/Show IP Address.sh"
echo sudo poweroff >> /home/pi/RetroPie/roms/setup/Shutdown.sh
echo sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch /home/pi/RetroPie/retropiemenu/splashscreen.rp >> "/home/pi/RetroPie/roms/setup/Splash Screen.sh"
mkdir /home/pi/RetroPie/roms/setup/boxart
mkdir /home/pi/RetroPie/roms/setup/cartart
mkdir /home/pi/RetroPie/roms/setup/marquee
mkdir /home/pi/RetroPie/roms/setup/snap
mkdir /home/pi/RetroPie/roms/setup/video
mkdir /home/pi/RetroPie/roms/setup/wheel
cp /home/pi/RetroPie/retropiemenu/icons/audiosettings.png "/home/pi/RetroPie/roms/setup/snap/Audio Settings.png"
cp /home/pi/RetroPie/retropiemenu/icons/bluetooth.png /home/pi/RetroPie/roms/setup/snap/Bluetooth.png
cp /home/pi/RetroPie/retropiemenu/icons/configedit.png "/home/pi/RetroPie/roms/setup/snap/Configuration Editor.png"
cp /home/pi/RetroPie/retropiemenu/icons/wifi.png "/home/pi/RetroPie/roms/setup/snap/Configure Wifi.png"
cp /home/pi/RetroPie/retropiemenu/icons/filemanager.png "/home/pi/RetroPie/roms/setup/snap/File Manager.png"
cp /home/pi/RetroPie/retropiemenu/icons/raspiconfig.png "/home/pi/RetroPie/roms/setup/snap/Raspberry Pie Setup.png"
cp /home/pi/RetroPie/retropiemenu/icons/retroarch.png "/home/pi/RetroPie/roms/setup/snap/Retroarch Setup.png"
cp /home/pi/RetroPie/retropiemenu/icons/retronetplay.png "/home/pi/RetroPie/roms/setup/snap/Retroarch Netplay.png"
cp /home/pi/RetroPie/retropiemenu/icons/rpsetup.png "/home/pi/RetroPie/roms/setup/snap/RetroPie Setup.png"
cp /home/pi/RetroPie/retropiemenu/icons/runcommand.png /home/pi/RetroPie/roms/setup/snap/RunCommand.png
cp /home/pi/RetroPie/retropiemenu/icons/showip.png "/home/pi/RetroPie/roms/setup/snap/Show IP Address.png"
cp /home/pi/RetroPie/retropiemenu/icons/splashscreen.png "/home/pi/RetroPie/roms/setup/snap/Splash Screen.png"
chmod +x /home/pi/RetroPie/roms/setup/*.sh
cat >> launchers/Setup.conf << EOF
executable = /bin/bash
arguments = "%ITEM_FILEPATH%"
EOF
mkdir collections/Setup
cat >> collections/Setup/settings.conf << EOF
# Uncomment and edit the following line to use a different ROM path.
list.path = /home/pi/RetroPie/roms/setup
list.includeMissingItems = false
list.extensions = sh
list.menuSort = yes
launcher = Setup
media.screenshot = /home/pi/RetroPie/roms/setup/snap
media.screentitle = /home/pi/RetroPie/roms/setup/title
media.artwork_back = /home/pi/RetroPie/roms/setup/boxart_back
media.artwork_front = /home/pi/RetroPie/roms/setup/boxart
media.logo = /home/pi/RetroPie/roms/setup/wheel
media.medium_back = /home/pi/RetroPie/roms/setup/cartart_back
media.medium_front = /home/pi/RetroPie/roms/setup/cartart
media.video = /home/pi/RetroPie/roms/setup/video
media.story = /home/pi/RetroPie/roms/setup/story
EOF
sed -i -e '$a\Setup' collections/Main/menu.txt
chmod +x retrofe_setup.sh
bash retrofe_setup.sh
This should get it working and give you a little artwork that is included with RetroPie. Obviously you can add more artwork to pretty it up. I borrowed the logo (wheel) artwork for the "Setup" collection from the Attract-Mode Unified layout http://forum.attractmode.org/index.php?topic=1123.msg8202#msg8202 (http://forum.attractmode.org/index.php?topic=1123.msg8202#msg8202)
P.S. This is the script I shared on page three but modified for RetroFE instead of Attract-Mode. I test it and it works on a basic RetroPie build with RetroFE added.
-
@progets, @dougan78 or @Pieter Hulshoff
I am looking at putting RetroFE on my Pi 2 but only if my theme works well (lol).
Therefore, as you all have a system up and running, would any of you be willing to do a test of my theme for me?
It's a simple theme, not graphically intense.
Theme Thread: http://retrofe.nl/SMF/index.php?topic=157.msg1944#msg1944
Theme: https://mega.nz/#!MJZDnJxC!3txsLOtlBEcR4vGRxvV4iI4JcssIprglaS3ShTNkYgE
XML with Pieters additions (for latest retrofe exe): http://retrofe.nl/SMF/index.php?topic=157.msg1952#msg1952
If my theme works without issue, I will start looking at getting RetroFE onto my Pi 2.
-
So I got gstreamer1.0 installed. Got it installed. I am testing my theme RetroSpin - Static 16x9. I added Atari 7800 just to test. I need to play with it more but videos are not playing at all atm.
my path to them in my setup is here: /home/pi/RetroFE/collections/Atari 7800/medium_artwork/video
The Atari 7800 Settings.conf has media.video path : media.video = %BASE_MEDIA_PATH%\%ITEM_COLLECTION_NAME%\medium_artwork\video^M
The main settings.conf has VideoEnable = yes
So not sure what gives on that.
Seems kind of pokey still since the last time I played with it. Like everything is half speed.
Boxes and carts slide on and off slower. Wheel is slower. Maybe the videos are playing and they are just off the screen, maybe I will disable videos and see if it speeds up next. Thanks
-
So I got gstreamer1.0 installed. Got it installed. I am testing my theme RetroSpin - Static 16x9. I added Atari 7800 just to test. I need to play with it more but videos are not playing at all atm.
my path to them in my setup is here: /home/pi/RetroFE/collections/Atari 7800/medium_artwork/video
The Atari 7800 Settings.conf has media.video path : media.video = %BASE_MEDIA_PATH%\%ITEM_COLLECTION_NAME%\medium_artwork\video^M
The main settings.conf has VideoEnable = yes
So not sure what gives on that.
Seems kind of pokey still since the last time I played with it. Like everything is half speed.
Boxes and carts slide on and off slower. Wheel is slower. Maybe the videos are playing and they are just off the screen, maybe I will disable videos and see if it speeds up next. Thanks
This might be my fault with bad advice. I haven't been able to test yet but I think that the full gstreamer1.0 package might be the issue. I think this should be a smaller subset of it or a plugin. This is a difference between a build I have working decently and a build that's pretty slow.
@Pieter - which specific gstreamer package(s) are you using?
-
I'll get back with some answers soon. I've been busy with other priorities, but I'll get back on this as soon as life permits. 😀
Sent from my SM-G920F using Tapatalk
-
No biggie just looking to give it a test again. Will hold off until I hear more. Thanks gents!
Sent from my SM-G920V using Tapatalk
-
Ok, that's odd. I just did a small test, but RetroFE 0.8.9 (with the fixes to properly launch emulators) is a LOT slower with video than e.g. 0.8.6. Did you notice a strong drop in performance as well? This may just be a general drop in performance that's causing the video to run slower.
-
Ok, that's odd. I just did a small test, but RetroFE 0.8.9 (with the fixes to properly launch emulators) is a LOT slower with video than e.g. 0.8.6. Did you notice a strong drop in performance as well? This may just be a general drop in performance that's causing the video to run slower.
I personally can't say. Other than your most recent release (or much older releases), the games wouldn't launch so I didn't use RetroFE for a period of time on the Pi. I do notice a difference of the latest RetroFE running with the old gstreamer install requirements vs a "sudo apt-get install gstreamer1.0". I only noticed this since I did a forklift move (picked up the new install folder and moved over to an older RetroFE build but current with RetroPie). There's a performance difference for certain. That's why I suspected the gstreamer packages as being part of the performance hit with the videos.
-
I don't think that's it, but I'll figure it out somehow. I have the same package installation for both versions, and 0.8.6 is simply much faster than 0.8.9 with regards to video display. It's quite possible that's simply because the pi is busy calculating other things that were changed, because I didn't really make any changes in the video display, but as said: I'll figure it out. :) I did install gstreamer1.0-omx, but so far I don't see any difference. I'll check if I need to do any code changes to make use of it.
-
I think I fixed it. :) Problem was that fonts were reloaded every time the objects were cleared (which happens rather regularly). They only need to be reloaded when unloadSDL is true and a game has been launched. Video performance is a lot better now (I was right: video performance was lacking since the pi was too busy doing other things: reloading fonts for printing text).
-
I think I fixed it. :) Problem was that fonts were reloaded every time the objects were cleared (which happens rather regularly). They only need to be reloaded when unloadSDL is true and a game has been launched. Video performance is a lot better now (I was right: video performance was lacking since the pi was too busy doing other things: reloading fonts for printing text).
Nice work! Bet that wasnt too easy.
Sent from my SM-G920V using Tapatalk
-
Ok recompiled on my setup and tested and it does seem faster. I would say it is not as fast as my cab with my Retrospin Static theme but works in general. I do have a few issues with artwork not showing up. That I fixed as it was a linux CaSEseNsiTIVe thing. And the videos do not play for me yet on the system menu. The main menu videos are playing fine. Not sure why it is the items in my include.txt match the video file names in the video folder. Need to figure that out.
-
It's better but still runs 100% CPU with the default Aeon Nox. I still see a reduced CPU usage when using specific gstreamer packages vs. the gstreamer full compile.
@Pieter - Did you determine which specific gstreamer package(s) you are using? Are you confident that the gstreamer install isn't a factor?
-
It's better but still runs 100% CPU with the default Aeon Nox. I still see a reduced CPU usage when using specific gstreamer packages vs. the gstreamer full compile.
@Pieter - Did you determine which specific gstreamer package(s) you are using? Are you confident that the gstreamer install isn't a factor?
No, I'm not at all confident that the gstreamer packages aren't a factor; I know they can be a huge factor. Which specific packages reduce your CPU usage?
The videos should run much smoother now though; that's at least what I expect from the latest fixes.
-
So, I'm finally back to working on my installer script for RetroPie. The info in this thread has been very helpful in driving some changes!
Regarding the RetroPie gstreamer requirements, I also wanted to avoid installing the full package. Right now, I've whittled the full list of dependencies on RetroPie down to the following, which now supports video and the video sound. I'm not sure that this setup would be considered CPU optimized...overall utilization across the 4 cores is only like 30%, but it totally maxes out a full core on occasion (retrofe process total cpu 70-150%)
tortoisehg g++ cmake dos2unix zlib1g-dev libsdl2-2.0-0 libsdl2-mixer-2.0-0 libsdl2-image-2.0-0 libsdl2-ttf-2.0-0
libsdl2-dev libsdl2-mixer-dev libsdl2-image-dev libsdl2-ttf-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev
gstreamer1.0-libav zlib1g-dev libglib2.0-0 libglib2.0-dev sqlite3 gstreamer1.0-plugins-good gstreamer1.0-alsa
I suspect I can remove libgstreamer-plugins-base1.0-dev, but I haven't tried it yet.
-
Getting back to the script development... I want to make the RetroFE integration into RetroPie as seamless as possible, and I feel like the biggest challenge is the naming convention. RetroPie has this concept of "short" platform names and a corresponding full name, which are defined in the platforms.cfg files (~/RetroPie-Setup/platforms.cfg and /opt/retropie/configs/all/platforms.cfg). I think it would be easiest and most "native" to RP if this naming convention was carried over to the RFE collections. My concern is that the metadata for RFE is coming from the HyperSpin XML files, which follow a different system naming format. The mismatch between the metadata system names and the RP-native platform names means that we won't pull back any metadata for the games.
So I guess I have 2 questions....
- Do folks agree that it would be easier for users if the RetroFE collections on a RetroPie setup were following the RP "short name" convention? Personally, I like the idea of consistency between the names shown in the RP "roms" directory, and the RFE collection names. Paths can then be standardized. This can simplify the collection configs, and probably also simplifies the sharing of artwork assets between RP FE's as we move forward as well.
- If we can agree on the above, should we consider a config option in the collection's settings.conf that explicitly defines the collection's metadata source name, optionally overriding the use of the collection's directory name?
Thank you for your consideration....
-
Yes, I agree that it would be wise to follow the RetroPie setup, and the feature you're looking for for the meta already exists; just look at the Arcade collection (settings.conf).
The only thing the directory name really impacts is the printed (text) name of the collection, but we may be able to overwrite that from the info.conf file.
Sent from my SM-G920F using Tapatalk
-
Question: How exactly does gstreamer-omx fit into all of this? Is it just a plugin, to be used automatically if the videos fit the supported decoder or do I have to do something special in the code to make it work? I've been looking around via Google, but I haven't found much help in that area yet.
-
Yes, I agree that it would be wise to follow the RetroPie setup, and the feature you're looking for for the meta already exists; just look at the Arcade collection (settings.conf).
The only thing the directory name really impacts is the printed (text) name of the collection, but we may be able to overwrite that from the info.conf file.
I just checked: it can indeed be overwritten from settings.conf or info.conf, simply by setting the title variable there. In short: I see no reason not to use the RetroPie default naming. :)
-
Does anyone have issues with a controller/joystick/gamepad controlling the RetroFE frontend after launching and playing a game? Once I return from playing the first game in RetroFE the gamepad no longer controls RetroFE and only a keyboard works.
-
Does anyone have issues with a controller/joystick/gamepad controlling the RetroFE frontend after launching and playing a game? Once I return from playing the first game in RetroFE the gamepad no longer controls RetroFE and only a keyboard works.
I haven't checked that part to be honest, but I'll give it a try. It's quite possible I forgot to reinitialize the controllers after closing down and restarting SDL.
-
Found the issue; trying to fix it by adding hot-pluggable functionality. That was on the to-do list anyway. 😀
Sent from my SM-G920F using Tapatalk
-
Does anyone have issues with a controller/joystick/gamepad controlling the RetroFE frontend after launching and playing a game? Once I return from playing the first game in RetroFE the gamepad no longer controls RetroFE and only a keyboard works.
Try the latest code; I've hopefully added hot-pluggability, which should also fix this issue.
-
Does anyone have issues with a controller/joystick/gamepad controlling the RetroFE frontend after launching and playing a game? Once I return from playing the first game in RetroFE the gamepad no longer controls RetroFE and only a keyboard works.
Try the latest code; I've hopefully added hot-pluggability, which should also fix this issue.
Having issues with the new build. I haven't had a lot of time to test but here's what I see for now.
pi@retropie:~/retrofe $ cmake --build RetroFE/Build
[ 2%] Building CXX object CMakeFiles/retrofe.dir/Control/UserInput.cpp.o
/home/pi/retrofe/RetroFE/Source/Control/UserInput.cpp: In member function ‘bool UserInput::update(SDL_Event&)’:
/home/pi/retrofe/RetroFE/Source/Control/UserInput.cpp:302:72: error: ‘SDL_JoystickFromInstanceID’ was not declared in this scope
SDL_JoystickClose( SDL_JoystickFromInstanceID( e.jdevice.which ) );
^
CMakeFiles/retrofe.dir/build.make:158: recipe for target 'CMakeFiles/retrofe.dir/Control/UserInput.cpp.o' failed
make[2]: *** [CMakeFiles/retrofe.dir/Control/UserInput.cpp.o] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/retrofe.dir/all' failed
make[1]: *** [CMakeFiles/retrofe.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2
pi@retropie:~/retrofe $
-
Does anyone have issues with a controller/joystick/gamepad controlling the RetroFE frontend after launching and playing a game? Once I return from playing the first game in RetroFE the gamepad no longer controls RetroFE and only a keyboard works.
Try the latest code; I've hopefully added hot-pluggability, which should also fix this issue.
Having issues with the new build. I haven't had a lot of time to test but here's what I see for now.
pi@retropie:~/retrofe $ cmake --build RetroFE/Build
[ 2%] Building CXX object CMakeFiles/retrofe.dir/Control/UserInput.cpp.o
/home/pi/retrofe/RetroFE/Source/Control/UserInput.cpp: In member function ‘bool UserInput::update(SDL_Event&)’:
/home/pi/retrofe/RetroFE/Source/Control/UserInput.cpp:302:72: error: ‘SDL_JoystickFromInstanceID’ was not declared in this scope
SDL_JoystickClose( SDL_JoystickFromInstanceID( e.jdevice.which ) );
^
CMakeFiles/retrofe.dir/build.make:158: recipe for target 'CMakeFiles/retrofe.dir/Control/UserInput.cpp.o' failed
make[2]: *** [CMakeFiles/retrofe.dir/Control/UserInput.cpp.o] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/retrofe.dir/all' failed
make[1]: *** [CMakeFiles/retrofe.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2
pi@retropie:~/retrofe $
Seems like the SDL version of RetroPie is out of date; you need 2.0.5 for this feature to work. I had the same issue under Windows where I had to update SDL2. I'd already updated mine in order to compile the latest MAME.
-
Does anyone have issues with a controller/joystick/gamepad controlling the RetroFE frontend after launching and playing a game? Once I return from playing the first game in RetroFE the gamepad no longer controls RetroFE and only a keyboard works.
Try the latest code; I've hopefully added hot-pluggability, which should also fix this issue.
Having issues with the new build. I haven't had a lot of time to test but here's what I see for now.
pi@retropie:~/retrofe $ cmake --build RetroFE/Build
[ 2%] Building CXX object CMakeFiles/retrofe.dir/Control/UserInput.cpp.o
/home/pi/retrofe/RetroFE/Source/Control/UserInput.cpp: In member function ‘bool UserInput::update(SDL_Event&)’:
/home/pi/retrofe/RetroFE/Source/Control/UserInput.cpp:302:72: error: ‘SDL_JoystickFromInstanceID’ was not declared in this scope
SDL_JoystickClose( SDL_JoystickFromInstanceID( e.jdevice.which ) );
^
CMakeFiles/retrofe.dir/build.make:158: recipe for target 'CMakeFiles/retrofe.dir/Control/UserInput.cpp.o' failed
make[2]: *** [CMakeFiles/retrofe.dir/Control/UserInput.cpp.o] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/retrofe.dir/all' failed
make[1]: *** [CMakeFiles/retrofe.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2
pi@retropie:~/retrofe $
Seems like the SDL version of RetroPie is out of date; you need 2.0.5 for this feature to work. I had the same issue under Windows where I had to update SDL2. I'd already updated mine in order to compile the latest MAME.
I ran "bash <(curl -s https://bitbucket.org/phulshof/retrofe/raw/default/Scripts/Raspi2/install.sh)" tonight. Doesn't this install SDL2 from source? If so, how can I get a "newer" version?
Update - I see that the script only calls for SDL2 2.0.3 now.
Update 2 - Once I compiled SDL2 2.0.5 I was able to compile the latest RetroFe. The controller issue has been resolved with this RetroFE build. Great work Pieter!
-
The script needs updating for sure, and the new RetroPie release should have 2.0.5 installed by default.
Sent from my SM-G920F using Tapatalk
-
Just my 2 cents, the install.sh should be updated to include the newer SDL2 2.0.5 and also the original RetroFE dependencies (those work much better than a full gstreamer install). Once you have that I think most people can figure it out from there.
original RetroFE dependencies (I'm not certain all of these are needed)
sudo apt-get install g++ cmake libsdl2-image-dev libsdl2-mixer-dev libsdl2-ttf-dev libsdl2-dev gstreamer1.0-dev libgstreamer-plugins-base1.0-dev gstreamer1.0-plugins-good gstreamer1.0-libav zlib1g-dev libglib2.0-0 libglib2.0-dev sqlite3 gstreamer1.0-alsa gstreamer1.0-pulseaudio
P.S. I didn't see your post since it fell on a new page before I made this comment.
-
The script needs updating for sure, and the new RetroPie release should have 2.0.5 installed by default.
Sent from my SM-G920F using Tapatalk
The RetroPie 4.2 image doesn't have SDL2 2.0.5. It may come if you update RetroPie to 4.2.10 but I'm using a scratch disk because I'm porting the binary to "my build" so I didn't update RetroPie before building RetroFE. If I have time maybe I'll try.
Update - You must be right about the latest RetroPie including SDL2 2.0.5 because it works on "my build" without additional dependencies and the control works after exiting a game. Again, great job!
-
I've had a few other things on my mind lately, but I plan to get back into this. What's your current status with regards to setting this up?
I understand that Raspbian Stretch has just come out, which might be a good way to get the latest MAME versions up and running as well. I want to have a look and see how well MAME can handle the consoles on the Pi3 (NES, SNES, etc.). I use MAME for almost everything pre-N64 on my PC.
-
The latest version of my RetroFE install module for RetroPie is attached. Copy this file to ~/RetroPie-Setup/scriptmodules/supplementary/
To install, run sudo ~/RetroPie-Setup/retropie_setup.sh , then go to Manage packages | Manage experimental packages | retrofe (should be near the end of the list).
Once installed, the full set of RetroFE configs is accessible via RetroPie's "config/all/retrofe" samba share for easy management.
This is a pretty substantial upgrade over the previous version:
- Build dependencies fixed, with different packages depending on platform (Raspbian vs Ubuntu)
- Launchers created for all systems supported by RetroPie, using runcommand.sh
- RetroPie Menu collection created (thanks Progets for the inspiration)
- Settings updated to use the RetroPie rom directory
- Default collections renamed (and reconfigured) to use the standard RetroPie system naming convention
It would be great if some folks could test this out and provide additional feedback.
-
Thanks, I will give it a try soon. :)
-
Will reimage my card and give it a whirl next week
-
The script needs updating for sure, and the new RetroPie release should have 2.0.5 installed by default.
Sent from my SM-G920F using Tapatalk
The RetroPie 4.2 image doesn't have SDL2 2.0.5. It may come if you update RetroPie to 4.2.10 but I'm using a scratch disk because I'm porting the binary to "my build" so I didn't update RetroPie before building RetroFE. If I have time maybe I'll try.
Update - You must be right about the latest RetroPie including SDL2 2.0.5 because it works on "my build" without additional dependencies and the control works after exiting a game. Again, great job!
In addition to the RetroPie module, I am also working on an updated general install script for the RPi that uses SDL2.0.5 on a vanilla Jessie/Stretch image. As part of that, I've tried to distill the build & runtime dependencies to the bare minimum, and understand which components require them. I hope to share the working script soon, but figured I'd share those dependencies now, so other can review, test, and provide feedback.
BUILD_DEPEND="build-essential"
SDLRELEASE_BUILD_DEPEND="libasound2-dev libdbus-1-dev libudev-dev"
SDLIMAGE_BUILD_DEPEND="libjpeg62-turbo-dev libpng-dev libtiff5-dev libwebp-dev"
SDLMIXER_BUILD_DEPEND="libflac-dev libfluidsynth-dev libmad0-dev libmodplug-dev libvorbis-dev"
SDLTTF_BUILD_DEPEND="libfreetype6-dev libgl1-mesa-dev"
RETROFE_BUILD_DEPEND="tortoisehg cmake zlib1g-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libglib2.0-dev"
RETROFE_RUNTIME_DEPEND="gstreamer1.0-plugins-good gstreamer1.0-libav gstreamer1.0-alsa"
-
The latest version of my RetroFE install module for RetroPie is attached. Copy this file to ~/RetroPie-Setup/scriptmodules/supplementary/
To install, run sudo ~/RetroPie-Setup/retropie_setup.sh , then go to Manage packages | Manage experimental packages | retrofe (should be near the end of the list).
Once installed, the full set of RetroFE configs is accessible via RetroPie's "config/all/retrofe" samba share for easy management.
This is a pretty substantial upgrade over the previous version:
- Build dependencies fixed, with different packages depending on platform (Raspbian vs Ubuntu)
- Launchers created for all systems supported by RetroPie, using runcommand.sh
- RetroPie Menu collection created (thanks Progets for the inspiration)
- Settings updated to use the RetroPie rom directory
- Default collections renamed (and reconfigured) to use the standard RetroPie system naming convention
It would be great if some folks could test this out and provide additional feedback.
I did a fresh 4.2 retropie image. Put the retrofe.sh in place. It installed with one error on lib-magiccore_extra or some such module. Rebooted. config/all/retrofe was not there. Going to run all the updates on the OS now and tested running the install again to see if I get same error.
-
yeah same thing after updating. Let me know if you need more info.
-
More info would definitely be helpful. Can you attach your install log? I believe it can be found at ~/RetroPie-Setup/logs. If you aren't sure which one contains the errors, you can view the zipped contents directly using the 'zcat' command (no need to unzip). Thanks!
-
More info would definitely be helpful. Can you attach your install log? I believe it can be found at ~/RetroPie-Setup/logs. If you aren't sure which one contains the errors, you can view the zipped contents directly using the 'zcat' command (no need to unzip). Thanks!
Log started at: Sun 27 Aug 02:27:51 UTC 2017
RetroPie-Setup version: 4.2.18 (549d284)
System: Linux retropie 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
= = = = = = = = = = = = = = = = = = = = =
Installing dependencies for 'retrofe' : RetroFE emulator frontend
= = = = = = = = = = = = = = = = = = = = =
Did not find needed package(s): libmagickcore-extra. I am trying to install them now.
Hit http://archive.raspberrypi.org jessie InRelease
Hit http://mirrordirector.raspbian.org jessie InRelease
Hit http://mirrordirector.raspbian.org jessie/main armhf Packages
Hit http://archive.raspberrypi.org jessie/main armhf Packages
Hit http://mirrordirector.raspbian.org jessie/contrib armhf Packages
Hit http://mirrordirector.raspbian.org jessie/non-free armhf Packages
Hit http://archive.raspberrypi.org jessie/ui armhf Packages
Hit http://mirrordirector.raspbian.org jessie/rpi armhf Packages
Ign http://archive.raspberrypi.org jessie/main Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en
Ign http://archive.raspberrypi.org jessie/main Translation-en
Ign http://mirrordirector.raspbian.org jessie/main Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/main Translation-en
Ign http://archive.raspberrypi.org jessie/ui Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en
Ign http://archive.raspberrypi.org jessie/ui Translation-en
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
libmagickcore-6.q16-2-extra is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Could not install package(s): libmagickcore-extra.
Log ended at: Sun 27 Aug 02:28:22 UTC 2017
Total running time: 0 hours, 0 mins, 31 secs
-
Well this is a little frustrating since the package that is causing the error (libmagickcore-extra) is a total nice-to-have. It just converts the SVG logo file that EmulationStation uses for the RetroPie 'collection' into a PNG that RetroFE can display for its RetroPie collection. Apparently I am trying to install a virtual package, rather than a specific version, and the RetroPie installer doesn't like that.
Not sure how I missed this previously.
You can replace the package in line 338 directly (change to libmagickcore-6.q16-2-extra), or just download an updated copy of the script (updating the original post w/ the source code now).
-
Well this is a little frustrating since the package that is causing the error (libmagickcore-extra) is a total nice-to-have. It just converts the SVG logo file that EmulationStation uses for the RetroPie 'collection' into a PNG that RetroFE can display for its RetroPie collection. Apparently I am trying to install a virtual package, rather than a specific version, and the RetroPie installer doesn't like that.
Not sure how I missed this previously.
You can replace the package in line 338 directly (change to libmagickcore-6.q16-2-extra), or just download an updated copy of the script (updating the original post w/ the source code now).
Will test again this week. Thanks so much!
-
So far so good. So now after I get this run, I need to compile retrofe and move the program over to the \\192.168.1.8\configs\all\retrofe folder? Then how do you tell it to launch retropie be default instead of emulation station?
Thanks so much!
Edit: I compiled it and threw it in the retrofe folder and ran it and it didnt have my retorspin theme. Need to futs with it more. Let me know if I am doing something silly. Thanks again.
-
If the module ran without error, it already compiled retrofe for you and put it in your path. No need to compile on your own or move it into the folder. Should just be able to call 'retrofe' from the command line to launch. The corresponding config files and support media are what is exposed in that config share.
-
I figured as much. that is why I was surprised when retrofe was not in that path so I couldnt just do a sudo ./retrofe when I was there. Here is my log.
-
If you could test my layout RetroSpin - Static 16x9 and see if you get videos that would be great. I am looking to update RetroSpin - Static 16x9 to be more linux compatible and found a few images that need to be renamed to lower case or upper case in some instances. None of my videos are currently loading.
-
The log file you attached looks good. No indications that the install failed.
Can you run which retrofe from the command line?
Output should be /usr/bin/retrofe
You can also look for that file directly and try to run it. Let me know what you find.
-
I also applied your theme to the vanilla install. I have videos and wheels but no backgrounds?
-
Yeah mine was like that then I removed the default stuff out of menu.txt and put Atari 2600 only in there and it displayed my stuff with out videos. I think I may need to work with Pieter on a separate thread to fix if you have the same issue. Thanks for checking it out. Just looking to make it as accessible as possible.
-
The log file you attached looks good. No indications that the install failed.
Can you run which retrofe from the command line?
Output should be /usr/bin/retrofe
You can also look for that file directly and try to run it. Let me know what you find.
Yeah it is there so I was over thinking it. I should be able to launch retrofe from anywhere if it is there? or it should have copied to the retrofe folder in configs?
-
Yes, you should be able to launch it from anywhere after installing with my script. If you want RetroPie to automatically boot into it, you can edit the configs/all/autostart.sh script from the Samba share and replace 'emulationstation' with 'retrofe'.
-
Thank you for that. So far I have tested atari 7800 and works great. Launcher, launches games. SIngle controller works fine. What else do I need to test for you?
-
I don't have any specific testing needs if you've been able to validate that RetroFE is behaving similar to how it does on other platforms. However, I'd be interested in any feedback on the usability / setup process. I tried to keep the RetroFE configuration requirements minimal while integrating as seamlessly into RetroPie as possible. If there is anything that could be improved, please let me know.
-
I ordered the new Raspi3B+ and wanted to install a fresh RetroPie to it. How far is the progression with RetroPie and RetroFE? I really would prefer RetroFE. AS far as I know my old RetroPie setup for my Raspi3 wouldn't work anymore, because the Raspi3B+ needs atleast Raspian Strech.
-
It was working quite well about 7 months ago; haven’t played with my Pi for a while. Someone uploaded a script in one of the threads on this forum back then.
-
Any chance of getting a 3b+ version guys?
-
Any chance of getting a 3b+ version guys?
Won't the Pi3 installation script work on the 3b+? I don't own a 3b+ at the moment, so there's much I can do there beyond what I might be able to set up on the 3.
-
I thought the RetroFE script just built on the Retropie image so if that was up to date then RetroFE would be too. Like you Pieter I dont have a 3b+, i did install it on a spare Pi2 the other day but i did have to edit line 338 to
read ( imagemagick libmagickcore-6.q16-3-extra ) to get it to run
-
I think the scripts needs an update anyway; it's been a while since anyone played with it. I'm not even sure the latest code in bit bucket would build directly, since it uses some C++11 code. I'm finishing up some work on the latest features at the moment, but afterwards I plan on grabbing some small computers like the Pi and Odroid to see what needs to be done to get things up and running again.
-
I am always down for testing stuff. Just let me know.
-
Hi is there retrofe for pi 3 b+ ??
Sorry to bump an old post and I did a search and this post came up
-
There's no complete image, but there was an install script posted in the forums about 2 years ago. I have no idea what the current status of it is; I'm looking at Odroid and Pine at the moment.
-
system with coin accepter will be nice