@sturbek I dunno about turning off a USB port, but if you are using a powered hub, you could trigger that on and off via GPIO as you suggest. Nothing is built into RetroPie to do this--you're gonna have to build something from scratch.

A recent MAKE article was published with details about how to go about it with a relay:
https://makezine.com/2018/03/19/control-electronic-relays/

Thanks mitu. I didn't see that topic in my search. I'll try a few things. :)

I have a sub to emumovies.com. I wonder if I can overwrite their files to my card. I'll have to check the file names.

@rbaker Yes. They used my Pi with their set up and their set up no longer worked.

@johnny5126 I am new to Vice having only installed it over the weekend.

The video tutorial above that I used to map my joystick encouraged me to Save current settings, Save hotkeys and Save joystick map each time I made a new mapping.

I followed this advice and when I looked at the Vice config files in /opt/retropie/configs/c64, I noticed that changes were only being made to sdl-joymap-C64.vjm and not sdl-hotkey-C64.vkm which was the same as when first created.

For your maps to the virtual keyboard, for example, you should choose Save joystick map for them to persist. You can check this by looking at sdl-joymap-C64.vjm and you should see a line like 0 1 0 5 Virtual keyboard.

@chuckyp said in Games on USB-Drive are not refreshed:

@clyde not trying to make things more difficult. Just giving another option in-case he can’t get the official method to work.

And I mistook you for the TO, that's where my last paragraph about helpful details came from. :*)

@edmaul69

Pi2Scart Hat

https://pcsx2.net/getting-started.html
https://dolphin-emu.org/docs/faq/

@clyde worked like a charm... now just have to fine tune it

Thanks

I'd love to be able to use the attractmode with OSMC, but I think it isn't possible

I use OSMC for KODI and installed RetroPie via RetroSMC, which now works perfectly with Debian Stretch now that RetroPie has been worked on for Stretch

I've even tried custom scripts I found that add the attract options to emulationstation so you can switch between the different modes via the emulationstation menu but that doesn't work either as the modes don't appear on the emulationstation menu. At least not with OSMC as no menu options appear and I've never seen the 'Configure Splashscreen' option either with OSMC

@turnerl Because this is the easiest way to transfer your ROMs to the Pi system. Since this is a gaming dedicated system, it makes sense to make this operation as easy as possible.

To follow up, I purchased a Logitech F710 tonight, and what I’ve discovered is that the issue seems to be related to xinput generally. When I switched xinput off for the 710, everything suddenly worked as it should. Previously, both controllers on xinput had another issue I forgot to mention above, which was when I did the controller button configuration process, things went wonky when I got to the triggers.

Pressing the triggers would actuate twice, or sometimes not at all, forcing me to restart the config process. Switching the Logitech off of xinput fixed this issue as well as the lag/freezing problem. Obviously for now, my issue is resolved, strangely by doing the opposite of what the wiki tells me. It would be nice to be able to make xinput work properly, but unless and until that happens, I do at least have a working controller.

So... doesnt matter. i use now my gaming latop and emulationstation...

@groviar Well I know this is a super late response but here goes. I have successfully played many FDS titles from no-intro on current retropie software. I don't know how relevant this is to you today. Also atari lynx tends to require headered roms to work at least with beetle-lynx.

@hurkgt18 No, see https://retropie.org.uk/docs/Nintendo-Entertainment-System/

@jono Thanks for reaching out. I've had some time in the last week or so to tinker with settings. I will definitely try what you've outlined and get back to this thread. BTW- I've read that the latest update to RetroPie breaks the tank stick config. Has anyone heard this as well?

I was trying to accomplish the same thing, but couldn't find anything specific. I found a general solution, but it's a bit ugly and it would be better if lr-mgba could add a turbo button enable/disable core option (similar to fceu). I know this is an old thread but hopefully it helps someone.

Note: If you have a controller without L3 or R3 stick buttons, you can just map all the turbo functions to those buttons from the RetroArch menu and you won't need to do any of this.

Buttons can be completely disabled by changing them to "nul" in the joypad-specific files in /opt/retropie/configs/all/retroarch/autoconfig but that would affect all cores. You can make the change core-specific by making a copy of those file(s) and putting a joypad_autoconfig_dir line in your gba retroarch.cfg:

First, open the RetroArch menu while lr-mgba is running and map the turbo A and turbo B buttons to L2 and R2 (the same as turbo L and turbo R default mapping). This way you'll only need to disable those 2 buttons.

Then make a copy of your joypad configs:

cp -R /opt/retropie/configs/all/retroarch/autoconfig /opt/retropie/configs/gba/retroarch-joypads

In each of the .cfg files in the new /opt/retropie/configs/gba/retroarch-joypads directory (if you have more than one type of joypad), change these lines to disable the L2 and R2 buttons:

input_r2_btn = "nul" input_l2_btn = "nul"

Then add to /opt/retropie/configs/gba/retroarch.cfg

joypad_autoconfig_dir = "/opt/retropie/configs/gba/retroarch-joypads/"

You can comment out that line and re-map turbo A and turbo B to change back to the default behavior later. Be careful not to set any buttons you need to navigate the RetroArch menu to "nul" because it disables them there as well.

@barbudreadmon So should I do a source update?