Does retropie run on other machines other than the raspberry pi? If so which ones???

Drakaen391

Overall it might.... I know the wiki has mention for odroid....

The biggest problem is non pie builds usually have to be manually installed

mediamogul

@vic3vers4 said in Does retropie run on other machines other than the raspberry pi? If so which ones???:

some of them seem more powerful and probably emulate a little better

Many of the other boards are not as well supported due to having a smaller community behind them. It's not uncommon to see the Pi outpace them due to the software being more optimized.

ExarKunIv

@vic3vers4

right now there are only 2 other builds out there. none of them as good as the one for the Pi, but they are being worked on

they are

OTA for the Odroid XU4
and Pine RetroPie for the Pine64
of course you have one for the PC

Parabolaralus

I know im new here, but id like to add to this. I started with a Pi3MB and tried out RetroPie x86 using lubuntu on an old-ish (1st gen i3) computer which i fell in love with. It worked great for quite a while so i gave away that Pi3 like i didnt even ask for a soda pop in exchange and just kept on using that computer.

A month or two ago something changed within retroarch and the controller mappings and i quickly found out it was mapping player one to something that doesnt exist. Maybe an on screen keyboard such as Orca (which i removed) or something else, but either way it just doesnt work anymore. I was able to replicate the same behavior across 3 desktop computers at which point i gave up and bought the new model 3b+.

Long story short alternatives are great and may function with relatively little troubleshooting, but at some point it may be more of a hassle then its worth...Plus if you look around their support is almost non-existant.

mitu

@parabolaralus said in Does retropie run on other machines other than the raspberry pi? If so which ones???:

Plus if you look around their support is almost non-existant.

Who's support ?

Parabolaralus

What I meant is that if you look at the orangepi forums or the others theres nowhere near as much info on what people have done to troubleshoot certain things as there is on here....The community!

Most of my issues ive resolved just by looking through everyone elses posts. Except the one i finally gave up on!

jonnykesh

@parabolaralus That's the upside of using something that lots of people use. It is rare that you are the first person to encounter the problem.
If you are the first then hopefully someone else will jump in or a dev will ask for further info.

Except the one i finally gave up on!

I'm intrigued now. What was the issue you were unable to fix?

Parabolaralus

At risk of highjacking his thread: Im not too worried about it anymore, but im sure someone else will run across this and i have plenty of devices to test fixes on.

Anyway so not too long ago an update was pushed out with retroarch along with 4.4 from what i understand and if youre running an x86 build youre building from source which to my knowledge only gives you the most recent version easily at least through the setup script.

With that update it seems to register the first device connected as player one which ties retroarch's menu to the controller. Not a problem, except that whatever device its tying this to doesnt exist. An invisible keyboard.
I actually went pretty far into troubleshooting this including stripping the computers of pcie devices, disabling usb ports etc but could never come up with a solution. I even went as far as clean installing lubuntu and debian on 3 different machines (i3, i5 and a core2quad) that i had laying around and setting up the retropie software according to: https://github.com/RetroPie/RetroPie-Setup/wiki/Debian
I totally thought it was some kind of MB issue registering a device and it turns out not so much. Could even be part of the OS as far as i know, but thats where i stopped.

If you have any ideas i could setup another and run some tests...whats really strange though is that the first time you boot into emulationstation this is not a problem as in you could setup retroarch and your LR cores, but the second you restart the computer with that same gamepad connected (nothing else) nothing works within retroarch.

Ive been using this for over a year doing the same thing over and its been fine until that 4.4 release.

jonnykesh

@parabolaralus I quickly scanned your response...
If you are using RetroArch 1.7.2 (I think) then that is how the controller scheme has changed.
RetroPie currently uses 1.7.1 but will, at some point change to use that version of RetroArch.
RetroPie have no control over what RetroArch decide to do. It's something they obviously want to implement.
RetroPie devs have 3 choices.

Follow the change and deal with it.
Fork RetroArch (unlikely)
Stick with 1.7.1 (I doubt it)

Parabolaralus

Yea it does compile RetroArch 1.72 so it makes sense, but what doesnt make sense is that no matter what i do i cannot get around that first device that doesnt exist. Hopefully this isnt a problem when the pi gets updated!
Do you think it could possibly be an on screen keyboard? I thought i removed everything related to that, but may have missed it...

jonnykesh

@parabolaralus Have you tried configuring a USB keyboard just to try and take up that "missing" device?
I run RetroPie on a Debian Laptop also but don't update it much (just because it complies everything from source and is a massive PITA!)
Have you tried the joystick selection script by a great user here Meleu?

Parabolaralus

I have actually and still no go! Id use the same exact keyboard that i used for setup and would also isolate it as the only device and still when i launch retroarch after a reboot nothing from that keyboard.

Heres whats also very strange; On my laptop just as with yours which obviously has a built in keyboard all is fine and in fact this is how i played FF7 on Saturday...I dont use controllers though on the laptop.

jonnykesh

@parabolaralus Sounds very strange indeed.
I'm not going to update just to see if mine breaks!
Have you considered a re-install of RetroPie?
I know it's a last resort but sometimes it just sorts weird issues like this.

Parabolaralus

Well...i thought i updated my laptop, but as it turns out as im on it now i did not and its on RetroArch 1.71. Ill do an update and see what happens...My pi 3b+ works even with my current overclocking tests so if things go south...

I did reinstall retropie on all 3 machines. My method of testing involved stripping the drive of its partition table, install my OS of choice (deb based of course), and then i installed retropie. Nothing else in between.

Edit: More info

I was wrong on that. Its RetroArch 1.7.1 on the desktop machine, but i was able to unfortunatly recreate this on the pi by doing an apt update, apt upgrade.
It upgraded a few things such as the bootloader and the kernel, but as im watching it it seemed to have partially removed xpad - i say partially because it stated removing xpad and blah blah, but then in the retropie setup script it showed it as installed. Im not sure which action if not both caused the issue, but reinstalling xpad after a reboot did not resolve it.

So my Pi no longer works in Retroarch for player one. Does anyone know of any fixes for this, incompatabilities, bugs within the newest kernel or anything of the sort?
It is entirely possible that i did the same on the desktop before doing that second reboot so im kinda leaning toward it being kernel issue since xpad was NOT installed.