SO this issue is related to running roms from a USB device as opposed to the default location on the SD card? Then yes, you may well need to re-point the paths as you have done.

I’ve kept mine simple and run all roms from SD.

Not seen anybody using the DS4. Does it detect the input when you run the configure USB controller option?

Hey there Diskonekted,

i was wondering how you managed to connect the Xbox One controller to the pi?
When i connect the controller to the Pi’s usb port with a micro USB, the controller’s light does not come on? so with no power i cannot enter key bindings in the emulation station menu.

Any help would be appreciated.

Does anybody notice a slight input lag when playing SNES compared to a normal console experience ? Mario is jumping but a little slower than my memories. Does it come from the emulation or can the controller be in cause ? (mine are bought from Aliexpress – ok material but i’m sure they won’t last long).

Links in case someone is interested :
http://www.aliexpress.com/item/1-x-Retro-Super-for-Nintendo-SNES-USB-Controller-for-PC-for-MAC-Controllers-SEALED/2051991309.html
http://www.aliexpress.com/item/USB-for-NES-Classic-Controller-for-Windows-PC-and-Mac-Classic-Style-White-Wholesale/32213747217.html

i’ve used the following link to setup roms on USB.

http://electricgardener.net/2014/04/03/retropie-moving-games-usb-stick/

It seems to work….. the only issue I am having is scraping gambits within rom directory using Floob’s method.

Need to scrape in original rom directory…. then copy everything across.

@mfkl90

Try this:

sudo nano /etc/usbmount/usbmount.conf

Find the line:

FS_MOUNTOPTIONS=""

Change it to:

FS_MOUNTOPTIONS="-fstype=vfat,flush,gid=plugdev,dmask=0007,fmask=0117"

Let me know the result.

MrBrsnes

Hi.

unfortunately i can’t give you any clue about your problem ..
but i was wondering if you are using these PSX to USB Adapters

because i had a similar problem with them.

cheers!

phil

EDIT: image doesn’t seem to show up: http://www.i-love-pc.com/images/products/g456.jpg

In case anybody is interested, I figured out that it’s actually quite easy to switch video plugins. mupen64plus has a –gfx switch that allows you to specify which plugin to use. Retropie 2.5 comes with two customized plugins, which happen to also be the plugins used in ouya, which is why ouya users also face the mario kart 64 issue. These plugins are named gles2n64 and gles2rice.

In retropie 2.5 gles2n64 is the default plugin used by mupen64plus. It actually looks quite a bit nicer – at least for composite video out – than gles2rice, which I believe used to be the default in previous versions. The problem is that gles2n64 tends to lock up on a lot of roms, and in the case of mario kart 64, it can only display one of the players’ screens.

In order to use the gles2rice plugin only for certain n64 roms, I created a separate folder in the roms directory. Then I created a new system in es_systems.cfg, and specified that plugin using the –gfx switch within the command tags. Note that you also have to explicitly set the gles2n64 plugin using the –gfx switch within the command tags of the original system, or the other system will cause gles2rice to be written into the main mupen config file as the default plugin. I’m guessing there’s a more elegant way to accomplish this, so sorry if I’m leading anybody astray, but it was the best I could do with the knowledge I have. I know you can also edit plugin settings on a per-game basis via config files too.

Below is the relevant config code for using my method. The path to the roms directory has also been changed from the default because I keep all my roms on a usb stick, so you can’t just copy and paste this into your /etc/emulationstation/es_systems.cfg file. Also, I added a “sudo” before the commands as I also store save data on the usb stick, and if the commands aren’t run as root, mupen can’t write to the fat32 formatted usb stick. I’ve also read that running as root can give performance gains.

  <system>
    <fullname>Nintendo 64</fullname>
    <name>n64-mupen64plus</name>
    <path>/media/usb0/r0ms/n64-mupen64plus</path>
    <extension>.z64 .Z64 .n64 .N64 .v64 .V64</extension>
    <command>sudo /opt/retropie/supplementary/runcommand/runcommand.sh 1 "/opt/retropie/emulators/mupen64plus/bin/mupen64plus --gfx mupen64plus-video-n64 --configdir /opt/retropie/configs/n64 --datadir /opt/retropie/configs/n64 %ROM%" "mupen64plus"</command>
    <platform>n64</platform>
    <theme>n64</theme>
  </system>
  <system>
    <fullname>Nintendo 64</fullname>
    <name>n64-mupen64plus</name>
    <path>/media/usb0/r0ms/n64-mupen-rice</path>
    <extension>.z64 .Z64 .n64 .N64 .v64 .V64</extension>
    <command>sudo /opt/retropie/supplementary/runcommand/runcommand.sh 1 "/opt/retropie/emulators/mupen64plus/bin/mupen64plus --gfx mupen64plus-video-rice --configdir /opt/retropie/configs/n64 --datadir /opt/retropie/configs/n64 %ROM%" "mupen64plus"</command>
    <platform>n64</platform>
    <theme>n64</theme>
  </system>

Now I’m going through all my roms, and when I find one that doesn’t work with the default plugin, I simply move it over into the alternate folder (specified with the above config code) and relaunch emulationstation. Now there are two nintendo 64’s listed in emulation station, one for the default plugin, and one for the rice plugin. Of course, some roms don’t work with either plugin, but sometimes I get lucky. Majora’s Mask and Banjo Kazooie are two notable examples of roms that only work with the rice plugin for me.

I haven’t been able to test 2 player mario kart 64 with the rice plugin as I need my friend to come back over with his controller (unless I can figure out how to specify player two as using the keyboard), but I’m hopeful it’ll work, as it seems to work for ouya users based on the reddit thread in my previous post.

All in all, n64 games run much better on my raspberry pi 2 than they did on my b+. And I finally have working doom, duke nukem 3d, and quake III arena. I’ll post my overclock and memory split settings as well. It’s been pretty stable at these settings, but if I try to go up to 1140 the pi seems to freeze up and I get locked out. And I believe it was also the cause of sd card corruption, which is why I store roms, save data, and backups of config files on a usb stick now.

gpu_mem=64
arm_freq=1100
core_freq=500
sdram_freq=500
over_voltage=6

UPDATE: I got two player mario kart 64 to work with the rice plugin! I had to tweak some settings in /opt/retropie/configs/n64/mupen64plus.cfg to get it to work. With the default config both players’ screens just freeze before the race even starts. This seems to have to do with when the screen is redrawn. Under the “[Video-Rice]” section of the file I changed the following parameters. This also had the effect of making things look nicer too (smoother frame rate)

ScreenUpdateSetting = 7
...
SkipFrame = False
SkipScreenUpdate = False

Edit: Lowered gpu memory to 64 for better performance.

So initial report is that it seems promising! When the system boots up it automatically detects the XbOne controller and I run through the basic left-right-up-down setup and can navigate through the menu options.

I haven’t transferred across any ROMS yet, but will do so soon. I tried the shareware games that were already packaged with the build and both Doom and Quake seemed unresponsive to controller input, so a problem there.

I haven’t run through the configuration mentioned here, as I figured this is only for the 360 controller (as the article name suggests), but will jump into the system config soon to have a look at some things.

I’ll note that I don’t have “wired XbOne” controllers per se; these are just the normal wireless ones that I’m using with the USB cables, so when shutting the RetroPi system down, these automatically sense a loss of connection and search for the Xbox One wirelessly. This isn’t so much of a “problem” when turning off the Retro, but can be an issue when rebooting it, as I noticed some funky modprobe errors when doing this, as the system (presumably) notices that there are problems sending input the the controller (naturally as it has a Xbox One and a RetroPi trying to direct it).

I’ll note that the system build info shows it’s using kernel 3.18.5, so this is probably the same Debian build as Raspbian, just cut down and tailored for RetroPi.

More troubleshooting soon!

Having the exact same issue with a Xin-Mo Dual USB controller, my Pi knowledge is certainly lacking a little but this seems quite manageable, if it isn’t too much trouble and seeing only as it was mentioned would it be too much hassle for you to post the updated compiled Kernel feederchain?

Cheers

The power switch will only work with a single power supply attached to the ControlBlock. For what I experienced, the micro USB cable can also have an impact: In my case I had to used a very cheap one that seems to lead to quite a high voltage drop. There are also some posts about this in the official RPi forum, e.g., at http://www.raspberrypi.org/forums/viewtopic.php?p=370520#p370520.

What does sudo i2cdetect -y 1 give as output? This checks for I2C devices …

Hey there,

I am looking for the exact same solution. Any help is very welcome. I’ve got this problem not only with the PSX roms, also with SNES.

I have already added the following to my retroarch.cfg file.

I am using my 16GB SD card with NOOBS (Openelec & Retropie) on my RPi2. I have copied all my roms onto my fat32 USB stick to safe some space on my SD card.

Is there a chance to active saving/loading here? Or can I change the path where the savee games can be located? It would be ok to have them on the SD card if necessary.

Thanks in advance.

Kind regards,
MrBrsnes

EDIT: I’ve found this: – So I’ll give it a try later and let you all know.

This may help – its how I use an iBuffalo USB with N64

http://smartretro.co.uk/forums/viewtopic.php?f=3&t=22

2a is fine. You don’t have another USB power supply/charger around to test ?
did you try without the usb devices connected ?