[herbfargus]

By default select+right shoulder is save, select+left shoulder is load

They’re called hotkeys and there is a a setting for it in the auto configs that were created when you first configured your controller (if you’re on retropie 3 rc1)

[herbfargus]

Retroarch has netplay integrated already. I haven’t tested it myself yet, but it is there.

[herbfargus]

That isnt running too hot… You could get some small heat sinks just in case. How many systems/ROMs do you have set up? After around 15 or 18 systems ish emulation station started to freeze on me as well, I removed a few systems and it worked fine again.

[herbfargus]

Ah thanks for the clarification- I didn’t have access to my pi so I wasn’t sure on the filepath. I’ve ammended my post. Glad you got it sorted!

[herbfargus]

This is a general WiFi dongle list:

http://elinux.org/RPi_USB_Wi-Fi_Adapters

I use one that came as part of a canakit but there are lots that work.

[herbfargus]

I haven’t tried the ROM syncing thing so I wouldn’t know about that but the wireless adapter you’re having problems with is known to have problems… You might have better luck just buying a new one, or you can attempt to install the drivers it needs

http://smartretro.co.uk/forums/viewtopic.php?t=50

[herbfargus]

personally I don’t have any problem with it, the licenses allow for modifications as far I understand them, as long as you’re not providing the image with roms/bios files or illegal kodi addons. (I’ve actually been meaning to try out this image myself)

but its not up to me as buzz/petrockblog are really the main ones who maintain the code/ distribute the image.

Just know that we won’t be able to provide support outside of the officially released retropie image.

also in reference to wicd-curses, you’re correct- we have removed it entirely for cpu scaling issues and replaced it with a simple dialog terminal gui. The new wifi menu will be the default with the retropie 3 stable release.

[herbfargus]

there is a file called es_input.cfg that can be added manually (file path is /home/pi/.emulationstation I believe.):

This is for an xbox controller and a keyboard

You just have to modify the device name and buttons to match your own controller. you can type lsusb to see what your devicename is

<?xml version="1.0"?>
<inputList>
    <inputConfig type="keyboard" />
    <inputConfig type="joystick" deviceName="Xbox Gamepad (userspace driver)">
        <input name="a" type="button" id="4" value="1" />
        <input name="b" type="button" id="5" value="1" />
        <input name="down" type="button" id="1" value="1" />
        <input name="left" type="button" id="2" value="1" />
        <input name="menu" type="button" id="13" value="1" />
        <input name="pagedown" type="button" id="11" value="1" />
        <input name="pageup" type="button" id="10" value="1" />
        <input name="right" type="button" id="3" value="1" />
        <input name="select" type="button" id="8" value="1" />
        <input name="up" type="button" id="0" value="1" />
    </inputConfig>
    <inputConfig type="keyboard">
        <input name="a" type="key" id="13" value="1" />
        <input name="b" type="key" id="8" value="1" />
        <input name="down" type="key" id="274" value="1" />
        <input name="left" type="key" id="276" value="1" />
        <input name="menu" type="key" id="109" value="1" />
        <input name="pagedown" type="key" id="281" value="1" />
        <input name="pageup" type="key" id="280" value="1" />
        <input name="right" type="key" id="275" value="1" />
        <input name="select" type="key" id="108" value="1" />
        <input name="up" type="key" id="273" value="1" />
    </inputConfig>
</inputList>

[herbfargus]

yeah that may be why- its definitely not the most ideal yet.

yeah change this line here: do_start to do_start &

The only caveat is when emulationstation loads, it loads, so it will cut off your video whenever it loads up.

[herbfargus]

Yeah I really need to find a better scripted option than all these manual edits… I’m still working on that. Its weird its giving you an error but still loading the video, and outside of the boot text I talked about in my video I don’t know how to hide the rest of the text.

[herbfargus]

I’m hoping we can get a central repo for themes and artwork so we can have something more complete:

https://github.com/RetroPie/RetroPie-Setup/issues/929

[herbfargus]

Sounds good, thanks for your contributions :) in the mean time I’ve created two new sheets on the compatibility list for vanilla mupen64plus and lr-mupen64plus if people are feeling ambitious.

[herbfargus]

As far as I understand it, the mupen64plus-testing has optimised configs for the games that perhaps the others don’t have. I could be mistaken though. Gizmo is the one who would know the most about it as its his repo. I’m not sure about the long term plans for integration with the main mupen64plus core but I’m guessing once configs are sorted out then maybe it would be integrated?

I guess it just depends on how thorough people want to be with their testing. I don’t have as much time for testing as I’d like to have. I’m all for being thorough as long as it is easy to understand. Perhaps for now we can start with mupen64plus-testing (I’ve ammended the column title to say best video plugin) but we could duplicate the page and add another sheet for the regular mupen64plus emulator and another sheet for the lr-mupen64plus emulator as well if you’d like.

And these are all just assuming that there are no config changes- there are a whole bunch of settings within the configs that may be able to be altered in order to get the games to be more playable and those could be a whole other set of sheets… it can get complicated pretty fast :P

[herbfargus]

Providing ROMs with an image is illegal and that will never happen.

That video is also outdated as there have been vast improvements in retropie 3. Retropie is the easiest to set up it has ever been.

The raspberry pi isn’t an xbox- it was designed to do many things, so it will take a little bit of learning in the terminal- which isn’t a bad thing- I’ve turned my pi into a timelapse camera, media server, etc. You can’t do those things with an Xbox…

[herbfargus]

you can get some games to be playable with the playstation 1 on the rpi 1 (typically with overclocking) but it’s definitely hit and miss. its about the apex of what it can handle.

[herbfargus]

processing power on the Raspberry Pi 1 isnt good enough to run the n64- it barely runs with a Raspi 2 as it is. I usually just stick with my pc for n64 emulation. You can check out the compatibility list on this thread if you want an idea of which ones sorta work on the Rpi 2.

N64 Compatibility List!

[herbfargus]

if you have a controller plugged in it overrides the keyboard nul binding so you can press select (or whatever your hotkey is) and esc and it will exit. or you can just press select+start to exit directly with your gamepad.

[herbfargus]

There seem to be endless configs to tweak for n64, so it can be tedious at times. I’ll verify things as I test as well. Thanks for all your work on this.

[herbfargus]

I figure as long as is reasonable to wait. Even if it takes a bit you can always make a note of it and leave it to the user to decide if its worth their time to wait that long for their game to load.

[herbfargus]

It could have something to do with it not registering the characters of your gamepad Id properly in emulationstation- when I run my virtual gamepad as an app and try and configure it with emulationstation it shows up with text characters emulation station can’t reconcile so it just doesn’t work, but idk- it could be something else entirely.

[herbfargus]

I had some knock off n64 controllers and the axis buttons were really finicky so when I would press up it would press up and right- i had to be real careful with each button press to make sure I only got the one I needed otherwise it would say it was taken already. Its possible yours may be similar. (It was actually the same controller name too- dragonrise generic USB.)

[herbfargus]

That’s odd. Sometimes its get weird with updates. You could try a full binary install and see if that fixes it… May want to make a backup first just in case.

[herbfargus]

You mean kinda like all the controllers on this page?

https://github.com/RetroPie/RetroPie-Setup/wiki/RetroArch-Configuration

[herbfargus]

Ps3 controller issue is known- none of the main devs have a ps3 controller to test with so its hard for them to solve it without one.

And the zip issue is also known. I usually just extract all my zipped roms (minus the mame and FBA ROMs as those need to be zipped) not sure if its retroarch or specific to retropie. If you’re concerned about space you can mount external harddrives/USB sticks , use NAS, or upgrade your SD card to a 64GB micro SD.

[herbfargus]

How many emulators do you have on your system? It will do that if you have a lot of emulators- its a bug with emulationstation/RPI not having enough processing power.

[herbfargus]

There are capture cards that will essentially pull the video output from your TV (but those can be expensive) otherwise I haven’t looked that hard past tightvnc (which I got the same results as you). Floob may know since he makes some good videos of his gameplay

[herbfargus]

I’m not sure as I don’t have an xbox360 controller,- I’m hoping once we’re able to get the official kodi 15 repo added to the source that we can compile it with cec and joystick support so people don’t run into these issues and can utilise their gamepads with kodi’s joypad configs.

[herbfargus]

#!/usr/bin/env bash

# This file is part of RetroPie.
# 
# (c) Copyright 2012-2015  Florian Müller ()
# 
# See the LICENSE.md file at the top-level directory of this distribution and 
# at https://raw.githubusercontent.com/RetroPie/RetroPie-Setup/master/LICENSE.md
#

# http://www.gtkdb.de/index_36_2176.html
rp_module_id="kodi-15"
rp_module_desc="Install Kodi 15 (Must install the other Kodi first!)"
rp_module_menus="4+"
rp_module_flags="nobin"

function depends_kodi-15() {
    apt-get remove -y kodi kodi.bin
}

function sources_kodi-15() {
 wget -O- -q http://steinerdatenbank.de/software/kodi-15.tar.gz | tar -xvz
 cd kodi-15
 ./install
}

function configure_kodi-15() {
    echo 'SUBSYSTEM=="input", GROUP="input", MODE="0660"' > /etc/udev/rules.d/99-input.rules

    mkRomDir "ports"
    cat > "$romdir/ports/Kodi.sh" << _EOF_
#!/bin/bash
startkodi
_EOF_

    chmod +x "$romdir/ports/Kodi.sh"

    setESSystem 'Ports' 'ports' '~/RetroPie/roms/ports' '.sh .SH' '%ROM%' 'pc' 'ports'
}

Save it as kodi15.sh and place it in /home/pi/RetroPie-Setup/scriptmodules/ports/

Then open up your setup script and install it from the experimental menu.

An official release is still pending on the raspbian repo being updated.

[herbfargus]

well just to confuse you even more we just replaced wicd-curses in the code with a simple wifi script that doesn’t cause the same cpu scaling issues. if you update you setup script you can use the wifi script under the setup option- or you can just wait a bit until 3.0 stable is released sometime soonish and do a fresh build from there and the wifi option will be in the retropie menu in emulationstation.

[herbfargus]

For roms that don’t work, just mark them as unstable in the dropdown and in the notes column just state doesn’t work on either plugin (assuming its unstable on both)

Should I have two columns for the plugins? or should I just leave it with the one column and have people choose which plugin works the best? (I think how it is right now is probably simplest)

as far as beta roms go- you can test the regular version and the beta version and see if there is any difference. If there is, then just add another row for the beta rom and mark them accordingly.

Thank you for your contributions :)

[herbfargus]

By all means!- that’s what its for. I made it editable for anyone to change as they have things to offer.

I created the template so the results would be consistent (the drop down menus only allow for certain responses and color code themselves accordingly when chosen) but I also left a notes column for anything extra that may need to be noted. If you feel like there is anything else that needs to be added or can be improved I’m open to new ideas.

On the mame compatibility lists I had 3 options. Ok, has issues, doesn’t work. Would it make more sense to have those three on this list as well or should I just keep it to stable and unstable?

[herbfargus]

Its a hardware issue with a 3.5 mm jack- isn’t related to retropie. I had the same issue with mine, I just stick with HDMI. There may be ways to quell it with external hardware/sound cards etc. But I never was able to figure it out. Its something that’s been discussed on the raspberry pi forums

https://www.raspberrypi.org/forums/viewtopic.php?f=38&t=10538&start=25

[herbfargus]

Yeah I made a quick video on how/where to install new emulators:

In the video I think its in experimental but it was just moved to the stable emulators. Its called lr-bluemsx.

[herbfargus]

A wired connection would help. You don’t even have wicd-curses installed which is why it gives you the error- its trying to install it but you’re not connected to the internet. Have you tried connecting with wicd-curses- it can make things a bit easier at times. (Granted you’ll need a wired connection to install it first.)

[herbfargus]

It is possible but perhaps unlikely. If you wish to remove any doubt you can remove wicd-curses with sudo apt-get remove wicd-curses and then just set the configs manually in interfaces.

[Author]

Posts