[labelwhore]

[quote=117000]Hi can you explain if you install the 3.5 jessie image how do you launch kodi from ES ?

Thanks

labelwhore wrote:

I’m just curious, what’s the advantage of using a dual boot setup for this, vs using the retropie Jessie image and installing Kodi to launch from ES?

[/quote]

Install Kodi from the restropie_setup script, then launch it from the ports menu. Alternatively, you could create a kodi folder in the roms folder like any of the emulators, move the kodi launch script from ports into the new folder, then edit es_systems.cfg to add a kodi section. (the setup script may actually add the new section in ES for you now.)

[labelwhore]

I have a really aggressive overclock on my pi that gets most PSP games running nearly perfectly. I do have a cheap sd card though, I do see some sub-second pauses in quite a few games, but they’re still very much playable. I’ve tested an absolute ton of titles and have found over 100 games that work well. My psp games are on an HDD.

Here’s what I’m using, these are guaranteed to void your warranty, don’t blame me if you blow up your pi with these:

gpu_mem_256=128
gpu_mem_512=256
gpu_mem_1024=384
gpu_mem=384
arm_freq=1100
core_freq=550
sdram_freq=500
over_voltage=4

force_turbo=1
avoid_pwm_pll=1
v3d_freq=450

My pi has a heatsink kit like this. I also have a massive case fan. (140mm I think) Don’t try these without great cooling.

[labelwhore]

I think you can simply install lr-mame2003 from source and it will pick up any recent commits.

[labelwhore]

I’ve had some similar issues with flaky micro SD adapters. Perhaps try a different one.

[labelwhore]

I just popped in to say good luck. Sorting out audio issues has been the bane of my linux experience. It’s not an easy nut to crack.

I’ve been messing around with adding background music to ES. I have to do some funky workaround with MAME. I’m not exactly sure why, so all I can really do here is confirm that MAME is in fact handling audio differently than most of the other emulators.

I do believe that caver01 is on the right track though. The secret sauce is in fixing the Alsa issues. Maybe remove Alsa completely, if possible, and try to set it up fresh?

[labelwhore]

Try looking in /home/pi/.kodi

…At least I think that’s where the kodi folder is. I’m not actually anywhere near my pi, though so I can’t double check.

nvm, I was beat to the punch

[labelwhore]

It says on the rpi forums that uae4arm is the newest version. So we already have a newer version than aue4all2

https://www.raspberrypi.org/forums/viewtopic.php?f=78&t=80602&sid=4ae64aa06ad0863188c2b5d5792c0671&start=150

…please also consider to switch to chip’s uae4arm, as this
is the newer version, with jit compiler etc., that gives
a great speedboost. :)

good luck and all the best!

and also this:

custom controls are broken in uae4all2, so don’t
expect them to work, sorry.
maybe uae4arm ported by chips, which can be found here
on the forum, has fixed that, but i think it’s
still broken there too on the rpi.
in general it’s advised to use uae4arm, as this is the
successor of uae4all2 and under active development.

[labelwhore]

Are they the correct romset for mame4all-pi?

https://github.com/retropie/RetroPie-Setup/wiki/Managing-ROMs

[labelwhore]

I think you’re ok OP. You’re not actually selling retropie, just the hardware to run it on.

[labelwhore]

Try a different FBA emulator. I have found that with some FBA roms in some emulators you can’t insert a coin no matter what, even after reassigning the hotkey. Particularly Capcom roms. However, if you use the same rom in a different emulator, it works fine. With the right fba bios some games will run in nearly any of the fba emulators.

[labelwhore]

There are some manual steps to get dreamcast working properly. Scroll down towards the bottom of the wiki and you’ll see the correct settings for xbox 360 controllers.

https://github.com/retropie/RetroPie-Setup/wiki/Dreamcast

[labelwhore]

Using --mouse or the first way with --alt-config /usr/local/mouse.cfg? The --mouse is a default mouse mode that’s built into the drivers and doesn’t actually use the .cfg file. Maybe try the same thing but using the cfg file.

I added mappings for all of the buttons on the controller but only the mouse related mappings seem to work in kodi. I never figured out why, but I believe it has to do with how kodi handles joysticks. I think kodi needs to be rebuilt for everything to work 100%. I’m not sure I’m up for that task.

[labelwhore]

You’ve still got a double quote in there right after xboxdrv. If you’ve removed the first one, make sure to remove the 2nd one as well.

Functionally, the quotes shouldn’t make a difference unless there was a space in the file path. The quotes basically just tell linux to ignore formatting so that special characters can be passed between the quotes.

[labelwhore]

It sounds familiar, I don’t remember which game though. Is one of the .bin files a lot larger than the others? If so, try just running the biggest file.

[labelwhore]

There are some conversion tools you may need for some psx .iso and .bin files. Unfortunately the only place I know to find it is on a rom site, so I can’t give out the link here. It’s to convert the .ecm games. There will be a file named like blah.bin.ecm for those games. Look for ecm tools on google.

You only need one file for psx games, you don’t need the .cue file.

[labelwhore]

I just meant to point out that it couldn’t simply be a Jessie issue. Something else is at play here.

[labelwhore]

I just ran home for lunch to check on a couple things. It looks like I missed a step in the wiki. I believe the cfg files need to be owned by the pi user. So to fix that, try this:

sudo chown pi:pi /usr/local/mouse.cfg

[labelwhore]

edit: wrong thrad

[labelwhore]

The behavior you’re describing makes it sound like maybe xpad is picking up the xbox controller instead of xboxdrv starting correctly, which points to an issue in the line we’re editing. Meaning xboxdrv isn’t starting correctly, hence the flashing lights.

I would double check that the mouse.cfg file is in the location specified so if you followed the wiki to a “T” it should be in /usr/local/.

If all else fails, it looks like there might be another way to do this. I just looked over the xboxdrv manual real quick. It looks like --mouse might do almost the same thing we’re trying to achieve here. In that case, the line would look like this:

/opt/retropie/supplementary/xboxdrv/bin/xboxdrv” –daemon –id 0 –led 2 –deadzone 4000 –silent –trigger-as-button --alt-config --mouse –next-controller –id 1 –led 3 –deadzone 4000 –silent –trigger-as-button –dbus disabled –detach-kernel-driver &
exit 0

Another possibility is to try replacing --alt-config with --next-config. I’m not completely sure what the difference is between the two tags.

[labelwhore]

I use textpad too. save the file, on the save as dialog, towards the bottom, there’s a drop down that says File Format. Make sure that is set to UNIX then save. That’s most likely the issue, IMO.

[labelwhore]

Did you simply copy the file that was linked to in the wiki? or did you create a new one with the same content? if you created a new file, did you edit it in windows? If that’s the case, double check that you saved the file as a UNIX file, and not PC.

As long as the mouse.cfg file is in the right place (ie., the same path that’s called out in the edit you just made.) and is a UNIX file, then it should work.

One thing you might try is changing permissions on the mouse.cfg file.

Try running this: sudo chmod +x /usr/local/mouse.cfg

That will ensure that the mouse.cfg file is executable.

[labelwhore]

It’s the command line that starts the emulator. Basically, ES is just a nice looking interface that runs things from command line for you.

To break it down the runcommand.sh script does a handful of things, it logs errors and does some cleanup after emulators quit, gives you that little interface to switch emulators and settings, and probably some other things I’m not aware of. The next piece is the actual command line that you would run if you were to start the emulator from command line directly. The part before the equal sign is just the name of the emulator that appears if you hit a button before the emulator were to start.

So what we’re doing is simply adding another command that always runs after you exit the emulator. From the command line you can run multiple commands one after another by stringing them together and separating them by &&. The %ROM% is just a variable that gets swapped out with the path to the rom that’s being started.

[labelwhore]

Wow guys, great work! I definitely want to try this out to get Dragon’s Lair on my Pi. There’s definitely a gaping hole where that game should be on my pi. lol

[labelwhore]

I’ve got a better idea. If you need this to run every time you quit an emulator, then simply modify the launch commands in your /opt/retropie/configs/{system}/emulators.cfg files.

So in those files you’ll see some lines like kind of this
emulator-name=”/path/to/runcommand.sh command/line/to_start/emulator %ROM%”

All you need to do is add this && moonlight quit <IP> between the %ROM% and the last “. so they’ll look something like this:
emulator-name=”/path/to/runcommand.sh command/line/to_start/emulator %ROM% && moonlight quit <IP>”

If you don’t actually need that to run every time, it’ll produce an error message when you close the emulator and moonlight was not running. To supress that error messag you could modify the line like this instead:

emulator-name=”/path/to/runcommand.sh command/line/to_start/emulator %ROM% && moonlight quit <IP> 2&>1 >/dev/null”

[labelwhore]

For what it’s worth, I have a bunch of .sh scripts I launch from within ES. I don’t use runcommand for them and they work fine. The launch command in es_systems.cfg is simply bash %ROM%. I’m on retropie 3.3 Jessie.

[labelwhore]

Yep, there’s no reason why not.

So with your setup, you’ll just need the --alt-config /path/to/mouse.cfg for the 1st player controller.

so like this:

/opt/retropie/supplementary/xboxdrv/bin/xboxdrv” –daemon –id 0 –led 2 –deadzone 4000 –silent –trigger-as-button --alt-config /usr/local/mouse.cfg –next-controller –id 1 –led 3 –deadzone 4000 –silent –trigger-as-button –dbus disabled –detach-kernel-driver &
exit 0

[labelwhore]

Well, nevermind then. :) I didn’t think hotswapping was supported.

[labelwhore]

Cool, thanks! Keeping it up to date isn’t an issue. I’m not adding any more emulators at this point, so I just want it to stay the way it is while I’m tweaking things. :P

[labelwhore]

Power output on the Pi’s USB ports is limited by software AND hardware.

There is a hardware hack that might be able to get this to work. It also could brick your pi. At ~$35 though, I think it’s worth experimenting.

More Power For Raspberry Pi USB Ports

I’ve never actually done thins, but am considering it for another project. If anyone goes through with it, please let us know it it works.

from that article a key piece of info:

There is a reason the Raspberry Pi foundation set the current limiting of the USB ports so low. The Pi was originally intended to run off of a micro USB phone charger. There aren’t many phone chargers out there that will supply more than 1A, and the CPU and related peripherals will take half of that. If you’re going to change the /boot/config.txt file, you’re going to need a beefy power supply. Increasing the current limiting of the USB ports to 2A will require an even bigger, beefier supply.

Given that, you may need to make some more power mods to your pi, such as modding it so that you can use a standard wallwart type power supply (the type with a with a barrel plug). That would open up your options in terms of the power supply itself.

[labelwhore]

no problem! This was annoying the hell out of me over the weekend until I found the fix.

[labelwhore]

[quote=117175]i think this sort of thing would only be solved by retroarch/libretro itself. you should ask on the forums but it looks like people have already asked and it’s a no: http://libretro.com/forums/showthread.php?t=5041

you could also log it as a request on their github: https://github.com/libretro/RetroArch/issues

i think you could actually use a physical switch if you were so inclined. you’d need something that switches from one USB device to another, entirely breaking the circuit. i think things like this already exist for printers. might just work??

[/quote]
You’d still need to stop the drivers and start the correct ones. I think my proposed solution via the gpio is probably the best option. Although, you’d probably be able to do all of that without rebooting, it would just require more code.

[labelwhore]

Alternatively, you could make controllers 3 and 4 (ports 2 and 3) the default controllers for specific emulators via retroarch.cfg for those emulators.

^^ there’s more than one way to skin a cat. :P

[labelwhore]

[quote=117172]It would be great if we could flip a physical switch on the outside of the cabinet to activate a software switch – If not that then a menu setting within the retropie settings would do just fine as well!

[/quote]It wouldn’t be hard to do just that, assuming you can start the arcade joystick drivers from command line. Just use a python script that starts via /etc/rc.local and evaluate the state of a switch connected to the gpio and start one driver or the other based on that evaluation.

Here’s a little info on working with the gpio. Obviously, you’d want a toggle switch here rather than a tactile switch.

http://razzpisampler.oreilly.com/ch07.html

[labelwhore]

In the retropie-setup script it’s under install individual emulators. I think it’s the 3rd option. Choose the emulator you’re having trouble with, then install from binary.

[labelwhore]

This happened to me over the weekend with several different systems/emulators while I was adding overlays. SNES was one of them. The only fix I found was to reinstall the emulator from binary. That would work and leave all my changes in place.

Annoying as hell, but the workaround isn’t bad.

[Author]

Posts