The proper way would be to build every emulator from scratch with different patches for all architectures. The same would be appropriate for emulationstation. Then remove every reference to RetroPie and reimplement their scripts to work on the different platforms osmc is running on.
If I had the time for that, I would have done it already, but there is not enough free time in my life.
Maybe Sam comes up with a solution that makes everyone happy, but I doubt it as long as people are comparing it to RetroPie.
If you really want to have all the functionality RetroPie provides in a convenient package, do a dualboot.
Edit: When I think about it: It could be possible with a chroot to raspbian with RetroPie installed. This would take up A LOT of space though as you basically will have two systems installed at once…
Theoretically: Could the retropie system be installed on a different mount (i.e. a usb drive, to not “waste” precious OSMC SD card space)
mcobit dual boot is the best solution…
But…(there is always a but…)
Berryboot: although it has hdmi-cec capabilities lucks system updating
Noobs: better but…no hdmi-cec support (yet)
Your project: sounds good but not a “full” retropie image
Image like this (http://blog.petrockblock.com/forums/topic/retropie-openelec-kodi-dual-boot/) looks good too (i know it is NOT osmc…but it is the same)
I ll stop asking that question…ok i understand;) Good try though (that is 4 sure)
Edit: hsus good question…i was wondering the same thing…
This could be a solution. Although it would be more complicated to set up again.
Of course a dualboot solution has it’s downsides. That’s why I am trying to do something different with this package.
This is a solution that works for me. If it doesn’t for you, feel free not to use it or be a bit more patient for changes to happen.
I think I found a solution for a full RetroPie installation with easy and fast switching from kodi as before.
It will take some time to test it completely and to make my scripts compatible with it but we will get there.
I was able to create a chroot from the RetroPie image that can be used to start emulationstation and the emulators just fine.
The downside is: It will take a whoopin’ 2GB of your SDcard without roms.
I may be able to get the size down long term though.
Im having similar problems with 360 wired controller config. If I use this guide: [How-to] Xbox 360 Controller OSMC my controller works flawlessly in OSMC. When I launch ES it is detected as a keyboard, I believe this is because we do a mapping in the xbmc.ini config file. This (kind of) ok for ES as you can navigate the menu fine using keypad but it does not map correctly to retropie games and it seems that the analog controls are not supported. Ive tried cutting down the xbmc.ini so that ES might detect the controller as a controller but ive had no luck.
I see three options: 1. Somebody who has this working could post their config files!
2. Since ES/retropie are working flawlessly with xpad, we could try to get kodi working with xpad.
3. Wait for @mcobit to finalise his work on including the FULL retropie install.
Any help appreciated.
I don’t believe that Kodi (as compiled in OSMC) supports gamepads for menu navigation. I have connected three gamepads which operate fine for ES and Retroarch but do not function within Kodi. I have also connected a gamepad in “keyboard mode” which would navigate in Kodi without issue. I think for the time being you can have ES/Retroarch support with analog the way you want OR you can have menu navigation in Kodi.
I can see this as an annoying issue for someone with no other means of navigation. Hopefully, OSMC will implement controller support within Kodi. Fortunately, until then, I am using a FLIRC and IR Remote for navigation in Kodi.
Just for info: It is coming along nicely.
I even installed the whole retropie stuff on my nas and mounted it from there with nfs.
Still figuring out some quirks.
Can you make the script ask during installation for the installation path?
Yeah, actually thought about it.
But right now all paths are hardcoded.
So let’s see if I can add some variables maybe with a configfile you can edit to point to the correct paths.
thanks for all of your work dude! You’re awesome!
Hope to have something to test for you tomorrow.
Be warned though: You have to uninstall your current installation. So back up your roms and BIOS!
Better not backup any configfiles as they will be different in some cases with the new image.
Anybody up for a test? Please send me a pm.
I want to confirm that it works before making it public this time.
Be warned, there could still be some bugs…
You’ll need a raspberry pi 2 and not to be afraid of reinstalling your system if something goes wrong.
I’m up for a test. I have my current setup as an image so not bothered if anything goes wrong. I’m current using your script with snes, mame and ps1 roms.
Mcobit thank you for your work on retrosmc, please i’m up for a test too, please I am proud to collaborate on this project, although my knowledge of linux are low
I use your script with mame, n64, ps1, snes and my beloved msx
Sorry jboy… Ive SOLVED this one.
You just need to use xboxdrv as a daemon to emulate a keyboard for OSMC as you will find via a google search. then alter the retropie.sh script to stop the daemon, copy a new config file that supports retropie (as seen on this forum) and restart the daemon.
It really is simple one you have the two configs sorted.
Im happy to post my scripts but they are “hacked” and not quite as dynamic as they should be.
The RPI 2 version seems to work for everybody who already tested. Now preparing the RPI 1 version.
Thanks for this nice How-To.
Just few questions :
Right now, only retroarch emulators will work, the others are deactivated, but I will try to add them when I find the time
This is still up to date ?
Can you add a list of supported consoles ?
Cross out where not applicable :
Atari 2600, NES, Game Boy, Game Boy color, Game Boy Advance, Super Nintendo, Master System, Megadrive (Genesis), FBA, iMame4all, PCEngine, MSX1/2, PSX, SegaCD, Sega 32x, Sega SG1000, Famicom Disk System.
This has an uninstallation option in the menu. It will remove the whole package if you don’t want to have it anymore,
but it will also remove any ROMS, BIOS, savefiles or configurationfiles you may have added or altered. So please make a backup of those if you want to use them later!
This is really clean after ? It will remove all installed packages too ? (dependencies install especially during this setup)
Thanks for answer