@mediamogul said in How to activate Remote Control Setup GUI from PuTTY:

@Phoenix

Seek, and ye shall find:
https://github.com/retropie/retropie-setup/wiki/updating-retropie#making-a-backup-option-1

lol I didn't look for that one as I was more concerned about how to restart the emulationstation remote setup. That's a very handy little step, especially if it's a common issue ;)

Was totally my fault! I forgot I copied across an older config.txt file so it was missing:

# Enable audio (loads snd_bcm2835) dtparam=audio=on

@qrayg

That guide should work, but you'll want to check it against the wiki entry to be sure.

Check this file:
/opt/retropie/configs/nes/retroarch.cfg

You can also access it using the configuration editor
https://github.com/retropie/retropie-setup/wiki/Configuration-Editor

@yusuo you can make changes while in game (lr) via F1. The changes will not save unless you have save on exit on.
This alows you to test some configurations without writing it permanent, until you are ready.

@TheDutyPaid said in no dreamcast roms loading at all now:

@FOGOR The Link was to a post on this very forum, I am not sure why it is not there? I can't find a working link to it, but it was fine when I posted it.

the thread had been deleted.. not sure why. i restored it so it should work now.

I did a quick test and it seems you can not edit root owned files with that setting. I left "Return code variable" set to the default Autodetect. The file I was testing with:

/boot/config.txt

open up **

/opt/retropie/configs/all/retroarch-joypads/"whatever the xin mo file is called".cfg** and add this to it:

input_player1_joypad_index = "1"

input_player2_joypad_index = "0"

this will at least fix all emulators using retroarch. other emulators probably have an option to do the same in their config file

@Kristopherson05 I still need more information. How did you configure the controller? Did you use the autoconfigure in Emulationstation? Did you edit the configs manually? Where is the copy of your configs for us to inspect?

You say Joystick? Is it connected via a USB controller, if so which one? An Ipac? if so a 2 or 4? or even a mini-pac? or maybe a Xin Mo.......each one presents it's own challenges.

Maybe all this is sorted and you are using MAME. Maybe it's not a retroarch version so you could have hit TAB and messed up things?

In order to help, I suggest that you follow this:

https://github.com/retropie/retropie-setup/wiki/retroarch-configuration

Not sure that it is possible to provide any further answers at this point without speculation.

That worked. Thanks.

@Andrewpk200 said in Control EmulationStation only with Keyboard, games with either kbd/controller:

OK am i missing something?
I had the same issue with my Pi, it would often jump to the next emulator when jumping through the rom list,
I solved it by switching off quick system select in the UI menu, this basically makes it so that once in a rom list for an emu you would have to back out to emulator selection to change emu meaning no way to 'accidentally' jump to another emulator

AndrewPK

Ok, I don't think you are missing anything. Your solution is much better as I had no idea this was a feature option. My little ones dexterity are not quite as good and they hit left and right accidentally changing emulators instead of only up and down in the gamelist with the controller D-Pad. Thanks for the tip! :)

The PS3 driver is incompatible with the built in bluetooth stack, and you do not use bluetoothctl. When installing the ps3 driver (sixpair), the default bluetooth stack is actually disabled (it is re-enabled if you remove the ps3 driver)

Pairing in 4.0 should be basically the same as 3.8.1 just the location has changed. Not sure what the problem might be, but it was fine when I last tested. Perhaps you can try the standard RetroPie image to rule out a difference in the OSMC system.

@wolfzrat Did you ever manage to get this working? I have trouble pairing mine up, too...

@Hyell

Oh okay, thanks for the help. I guess I'll just have to wait till my controllers come in mail and try again.

@dankcushions said in Running advmame roms from USB drive:

@orgon3 said in Running advmame roms from USB drive:

@dankcushions Thanks so much! After following your guide to the letter, it works, with a few caveats.

the copy command yields a few errors that it cannot copy symlinks getting a weird "operation not permitted" even though ls -al shows full permissions for everyone. I am getting that when EmulationStation runs an sh command, and in retropie_setup.sh when updating certain emulators. When attempting to play certain games/emulators (example, pc port, opentyrian) I get an "operation not permitted" error and I cannot play the game.

I didn't know how to fix it when it says it can't do something and I see the file permissions says it can ;_;

Perhaps all three are linked to the same issue? My fix for now would be to wipe my sd card, put on raspbian, setup the usb stick in fstab, and THEN start the installation?

hmm, i think maybe a mv would be better than a copy?
sudo mv /home/pi/RetroPie/* /media/usb0/ - it's less steps, certainly! guide updated...

i'm not sure about the permissions thing, and i don't use any of the PC emulators/ports, so not sure about that :( possibly it has to do with relative symlinks - if any exist in retropie they need to be converted to hardlinks before they're moved. this is a bit beyond my linux level, so i'm just guessing here :(

Well, the problem also occurs when attempting to upgrade. For me, a useful feature. In the end, I'll resort to having a few systems stored on my sd card and a few on my usb stick. I'll probably end just editing the cfg file for now and changing the specific system's path. Even installing just the core creates a symlink for genesis.

Thanks for your help though! I'm sure some linux guy will reply.

Thanks to all for your answers.

I tried it with a XBox 360 Controller of a friend of mine. And this controller worked instantly.
So tomorrow i am able to test my PS2 and PS1 controller with the RasPi.

I hope that this helps me.

Just an update after further testing. Going from rpie 3.7 to 4.0 beta 2 even with the latest rpie update from earlier today linapple will not get out of window mode or allow joystick to work if you do the full install. Mame2000_libretro wont work at all. However if you do the quick install and then update those two emulators then do a full update after that they work. I have repeatedly tested this all day today. Same results every time.