@batesman so i tested and it doesnt work any different as i thought. Sorry to waste your time. However this is good stuff to use because you can manipulate both analogs and the dpad to do whatever you want. With this method for using the analog stick as a dpad you could program the dpad to a whole new set of buttons that arent even related to direction like how first person shooters and other games are these days.

Thank you. I got it updated and it worked after an ES restart.

Yeah, I'm not sure what to do at this point. I've completely deleted the emulator and any files associated with it and reinstalled it, and I still get the same issue. I've tried changing the number of devices it's looking for in reicast.sh, I've checked and double checked the controller configs for both my PS3 and Xbox controllers to make sure they were set and named correctly and pointed at from emu.cfg. I've deleted my configs and reconfigured each controller at least twice to make sure that wasn't the issue. Verified both bios files and redownloaded again for good measure. Downloaded a gdi version of the same game just to see if cdi was the issue. I'm out of ideas on what to try next.

I have two different generic receivers, both of which work fine with RP. No need to spend more money on a genuine microsoft receiver :)

@mickabrig7

I have already tried to port this natively, there is just not enough RAM to run it...
(BTW Undertale needs OpenGL, which is only compatible with the stock Raspbian image, not the RetroPie image)
You can see my failed attempt here: https://retropie.org.uk/forum/topic/2704/undertale-for-retropie-raspberry-pi

@Mobile.Rodri said in MAME Savestates not working in Retroarch:

@illuminerdi I was able to save state using Lr-mame2003. I tried several games and all worked. I can try a specific game but it seems ok. I forgot to get my version, I'll double check when I get to the train, but it's relatively recent. I updated right around Christmas.

It worked for me too with Neo Geo games with the emulator you mentioned. I don't use them when I play arcade games, you basically have unlimited coins in most games one coin is equal to 1 credit/life. You beat the majority of the games within a hour.

I'll give it a shot. Thank you.

Cheers for the prompt reply! Feel free to delete this thread as it's unnecessary :)

Unfortunately there seems to be no deadzone option similar to the one in standalone mupen64plus, so I had no option but using xboxdrv.

The good news is, xboxdrv is not that hard to use if you follow mediamogul's excellent Advanced Controller Mapping Guide.

After a few tries I had a working base configuration, but the joystick output was still too low. After mediamogul's suggestion and some trial and error I got a configuration which works really nice for me (real N64 Controller and HuiJia USB GamePad adapter). What's nice about xboxdrv is, that you are able to rename your controller, which makes keeping track of multiple controllers with the same name quite easy.

This is my configuration:

sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv \ --evdev /dev/input/event2 \ --silent \ --detach-kernel-driver \ --force-feedback \ --deadzone-trigger 15% \ --deadzone 15% \ --device-name "N64 Player 1" \ --evdev-absmap ABS_X=x1,ABS_Y=y1,ABS_RZ=x2,ABS_Z=y2,ABS_HAT0X=dpad_x,ABS_HAT0Y=dpad_y \ --evdev-keymap BTN_THUMB=a,BTN_THUMB2=b,BTN_BASE=lb,BTN_BASE2=rb,BTN_BASE3=tl,BTN_BASE4=start \ --ui-axismap lt=void,rt=void \ --ui-buttonmap tr=void,guide=void,back=void,x=void,y=void \ --calibration x1=-16384:0:16384,y1=-16384:0:16384 \

I hope this helps if someone else has trouble using real Nintendo 64 controllers!

I wasn't able to map the hotkeys on the keyboard which is configured as a controller, but since I will use pyAutoGUI and scripting for GPIO inputs, I that's not a big deal.

The keycodes found in mupen64plus.cfg relate to ascii characters, and so I remapped the functions I plan to access later via GPIO to keys I won't need.

Here is simple overview I used to figure out key-values: Ascii Table
You have to look for the decimal values.

@jyo I dont know, but as i said you should open a new topic with details of your build etc.

I suspect it would be pulling Pi2 compatible files rather than 0 though, if it's in a Pi2 at the time...

@obsidianreq You didn't specify the emulator or version of retropie. There are two n64 emulators, and multiple video plugins for mupen64plus). Which one ? (check runcommand menu).

You didn't mention the hardware. You just said "x86 system". Which is quite generic. 32 or 64 bit ? which os ?

To close this issue, a bug was found in Picade HAT software which has now been fixed. See http://forums.pimoroni.com/t/picade-hat-joystick-not-detected-w-out-usb-keyboard-plugged-in/3704/30

@messyraverbaby

Okay, whew! that makes a bit more sense. Honestly, if it's a 192.168.x.x address, you are safe posting it since it's just an internal address so none of us can get to it.

The first thin to try is to use the same ftp client and try to connect to "retropie" instead of "192.168.1.100" (example IP address). If you don't set a static IP address, the Pi's address can change from time to time. There isn't really a problem just using the name retropie instead of an IP. If it stops connecting at some point, it's usually after a power failure and rebooting the router can clear it up.

If you would like to look further into say setting up a static IP address can you please let us know what type of router you have? I can probably dig up an online tutorial on how to get in and change stuff like that for you.

@cortex91 I am using 4.1 but I am still having this problem.