[laoracc]

Try putting the 8 in quotes, and change the enable hotkey button to something else. I don’t know if your setup would work, ie – hotkey + functionality on the same button, but it would almost certainly prevent you from mapping any other hotkey functionality (like menu/save/load/etc).

[laoracc]

You should be able to look in /opt/retropie/emulators/RetroArch/configs for the controller that you’ve setup (USB 2-axis joypad, in my case). As mentioned, /opt/retropie/configs/all/retroarch.cfg will be the main file that is consumed by every emulator that is run by RetroArch, with the ./configs/<console>/retroarch.cfg file being a per-emulator basis.

Just to clarify, you’ve run the ~/RetroPie-Setup/RetroPie-Setup.sh script to setup your controller? You’ve taken note of which values were associated with the DPad during this config, and matched them with the /opt/retropie/emulators/RetroArch/configs/<>.cfg file to confirm they’re the same?

What about going into the RetroArch Menu (input_menu_toggle_btn), and confirming that 1) it’s using the correct controller file, and 2) that the input settings match up? You’ll want to see (auto) for any input that won’t need the hotkey to trigger.

[laoracc]

I was under the impression your typical phone charger, micro USB, power supply would be enough to support Xbox controllers (someone definitely correct me if I’m wrong here; my receiver’s in the mail).

WRT your concerns about keeping it on all the time; I’d suggest getting automated backups in place. Once you’ve finished configuring your environment to your liking, backup your SD card into an image. If your FS becomes corrupted this will be an easy install. It won’t cover all the progress that’s been made on your save games however. For this, I’ve created a step-by-step on how to setup automated nightly backups which will sync your save states with a google drive account. You can take a look, here:

Automate Nightly Backups of your RetroPie Saves by Syncing to Google Drive
byu/Laoracc inraspberry_pi

I’ve also put together a DIY for the RetroPie setup, here.

[laoracc]

If anyone’s interested in including your saved games with your backups and don’t want to go manually searching for them (or even if you want an automated nightly backup for them), I’ve put together a step by step for syncing them with google drive. You can take a look, here.

[laoracc]

What console/game were you using to test, mystic?

I tried both the SNES and Genesis, and realized there was barely any change – but when I went to try an atari game, there was a clear difference. This would indicate to me that it’s a hardware constraint (since it’s easier to emulate and then increase the frame rate on Atari than SNES/Genesis). Did you notice anything different?

[laoracc]

jp24s,

Are you sure you used the correct button values in the retroarch.cfg? You’re not just copy-pasting Zoot’s config, right? I have tried two different controller brands (both 2-axis SNES-type controllers), and they each had different button values for the same button (ie – ‘select’ was ‘8’ on one, and ’10’ on another). Make sure you go into

/RetroPie-Setup/retropie_setup.sh

and run the Retroarch config to find out what values correspond to what buttons.

[laoracc]

Looking through this thread – are we sure that the hold and toggle buttons don’t work? I tried using input_toggle_fast_forward_btn , and I’m fairly positive it was successful, however the speed increase was so low it’s hard to tell that it did much of anything. That said, I didn’t see any increase when messing with the fastforward_ratio property. This makes sense, I think, as it is set to “-1” which indicates it will attempt to run at the max FPS allowed.

My question is this: Is the Pi not capable of increasing the frame-rate high enough to see a noticeable effect when using fast forward? Would overclocking the CPU/GPU help (I expect it would, but would we really be able to pull 2x/3x on FF)?

[laoracc]

As this was the first hit on google, hopefully noone gets upset that I’m necro’ing this thread.

To answer a few questions on here (that may/may not have been answered already above):

The GBA Bios is proprietary, so it’s of the user’s own accord to find it (just like ROMs). If you happen to have access to a bios already, with the newer versions of RetroPie (2.0+) you can find the location to place the bios at:

\opt\retropie\emulators\gpsp\raspberrypi\

Note, if you’re using Samba to connect to the Pi (which would be how you likely got your ROMs onto it), you won’t have access to this location unless you modify the smb.conf file at /etc/samba/smb.conf. An easier ‘one-time’ method, as described above, is to place the bios in the roms folder, ssh into the Pi, and cp it to the location above. However, here’s what you can add to the smb.conf file to provide yourself access to other parts of the Pi through Samba (this would also be done by ssh’ing into the Pi, and is useful if you plan on doing other modifications):

[root]
comment = root
path = /
writeable = yes
guest ok = yes
create mask = 0777
directory mask = 0777
force user = pi

Now you should see a ‘root’ folder pop up along with the roms folder. Note that this will provide you read access, but not write access, as all of the files and folders outside of /home/pi are owned by root. To give yourself write access, you can use the ‘chown’ (short for change owner) command:

sudo chown -R pi /opt/retropie/

This will give you write access, and let you drag + drop the bios into the respective folder. I would suggest you change the owner back to root when you are done (just change ‘pi’ in the command above, to ‘root’), for security purposes.

EDIT: I forgot to mention to not run this on /etc/ . If you do, you’ll change the ownership of the /etc/sudoers file, which will prevent you from running sudo. This will place you in a rather annoying catch-22 (which you’ll either need to reboot into recovery mode for, have a root account password created prior, or running pkexec on /etc/sudoers to change ownership back)

EDIT2: Before you recursively chown your /opt/retropie directory, you may want to take note of the ownership of the directories within (ls -l). For example, /opt/retropie/configs/ should probably be owned by the pi user (or atleast have write access) as this is where your controller configs reside, and to write new ones (through the RetroArch menu, for example), write access will of course be needed.

[Author]

Posts