@Duhjoker said in 8bitdo FC30pro not working in emulators:

Why are my posts all in code squares ?

Because you used a four space indent which can be used for code blocks. http://commonmark.org/help/

@cujoac said in Back-Up for fresh install:

on't have to go through the trouble of re-coding my control settings and re-scrape my games. Let me know, I'm not sure w

Your main retroarch.cfg which can be found in:

/opt/retropie/configs/all/

Or if you have a windows computer just enter the following path into windows explorer and you should be into the config folder:

\RETROPIE\configs\all

I also would copy the config files of my controllers. They are located in the /retroarch-joypads/ folder which is located in the path I mentioned above. Saved me a ton of headache lol.

I like ice cream.

.7 amps, and it actually tried to boot... Amazing lol...

I second the ultimarc utrak works fine. Also, the dual tankstick works great too

@auswear WORKED LIKE A CHARM! Thanks so much!

@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...