Solved it.
I opened the config TAB menu of the MAME emulator.

The mapping was messed up for some reason.
Here is how it looked like for the first 4 buttons of Player 1

P1 button 1 = LCTRL or RetroPad1 B (This one is correct)
P1 button 2 = LALT or RetroPad1 Y (This one is also fine)
P1 button 3 = SPACE or RetroPad1 X (This one is supposed to be mapped to LSHIFT)
P1 button 4 = LSHIFT or RetroPad1 A (This one is supposed to be mapped to SPACE)

Buttons 3 and 4 are rightfully mapped as RetroPad X and A, but for some reason, the first values (SPACE and LSHIFT) were switched.
What I did is to edit the value by hand with the keyboard.

If you compare the mapping for the X and A buttons with the MAME retroarch.cfg you will notice the difference.
input_player1_a = "space"
input_player1_x = "shift"

Have no clue why this happened, but it works now. :)

@guyute74 I popped the card out of my 2 and put it in my 3 and it worked great.

The only caveat would be if you have your Wifi filtering by MAC address you'll need to add the MAC address of the new Pi 3, but that's more of an infrastructure thing than anything to do with RetroPie or your Pi 3.

@BuZz Thanks for trying to get it fixed.

srry i thought it was, my bad :B

@ChristopherLeo installing from source is a waste of time. Always use binaries. Very rarely will you ever need to build from source

@TubeAlloy All good following disabling of plymouth, thanks again

@johncfigueroa https://github.com/RetroPie/RetroPie-Setup/wiki/lr-mame2003#mame-menu

@dankcushions For info, I just installed Recalbox and tried doing the same with Bubble Bobble (using the autosave/autoload config), and in this caase it just won't load anything.

@naddel81 said in Flickering in some games - Motion blur?:

That flickering is supposed to even burn into some N3DS Screens

This almost has to be isolated to specialty screens. In most cases an intermittent image only helps to prevent burn-in. Granted, it's a bug and some sort of fix would be ideal, but I have to wonder if this issue would produce any screen damage to conventional displays.

OK, thanks. Guess I have to bear those glitches then.

@barretta no Prob :3

@AndersHP said in Logitech Z623 in a bartop - too much?:

I have a HDMI-> VGA and Jack adapter

That should be good. You're using the adapter to convert from digital to analog instead of the Pi itself. If you're not hearing noise now, then you shouldn't have too much to worry about inside the cabinet.

As far as the speaker size, I see what you mean. I did some looking around online and many bartop arcade cabinets use a 3" speaker, which generally sounds pretty terrible. Going with a 2.1 solution may work well, but that Z623 sub is BIG.

Height: 11.2 in (284 mm)
Width: 12.0 in (305 mm)
Depth: 10.5 in (266 mm)
Weight: 15.4 lbs (7000 g)
alt text

@Pyjamarama said in UAE4Arm XBOXDRV - Mouse in Pad - F12:

I have put them in the opt/retropie/configs/amiga/emulators.cfg

uae4all = "/home/pi/RetroPie/roms/amiga/+Start\ UAE4All.sh" default="uae4arm" uae4arm="/home/pi/RetroPie/roms/amiga/+Start\ UAE4Arm.sh %ROM%" --ui-axismap x1=REL_X:10,y1=REL_Y:10 \ --ui-buttonmap y=BTN_LEFT,x=BTN_RIGHT,back=KEY_F12 \

but it does not do anything. I must be doing something wrong...

It requires a bit more effort unfortunately.

Take a look at my solution that by the way enables per-game joypad mapping config.

The +Start UAE4Arm.sh script has been modified to look for a file with the same name as the .uae config, but having .script extension. The .script file can contain things you might want to get executed before launching the game and after it is closed.

/opt/retropie/configs/amiga/emulators.cfg uae4arm line:

uae4arm="/home/pi/RetroPie/roms/amiga/+Start\ UAE4Arm.sh %ROM%"

/home/pi/RetroPie/roms/amiga/+Start UAE4Arm.sh

#!/bin/bash pushd "/opt/retropie/emulators/uae4arm" config=$1 script=$(echo $config | awk -F\. '{print $1}').script if [ -f "$script" ]; then /bin/bash "$script" "before" fi if [ -n "$config" ]; then ./uae4arm -f "$config" else ./uae4arm fi if [ -f "$script" ]; then /bin/bash "$script" "after" fi popd

Now the fun part - an example specific for Slam Tilt (and my pad) - Slam Tilt.script:
(note: my config name is Slam Tilt.uae)

#!/usr/bin/env bash case $1 in "before") sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv \ --evdev /dev/input/event0 \ --silent \ --detach-kernel-driver \ --force-feedback \ --deadzone-trigger 15% \ --deadzone 4000 \ --device-name "Media-Tech Wireless Pad" \ --evdev-absmap ABS_X=x1,ABS_Y=y1 \ --evdev-keymap BTN_SOUTH=a,BTN_EAST=b,BTN_NORTH=x,BTN_C=y,BTN_WEST=lb,BTN_Z=rb,BTN_TL=tl,BTN_TR=tr,BTN_TL2=guide,BTN_SELECT=back,BTN_TR2=start \ --ui-buttonmap tl=KEY_SPACE,tr=KEY_SPACE,lb=KEY_A,rb=KEY_L,a=KEY_ENTER,b=KEY_S,x=KEY_Y,start=KEY_F1,guide=KEY_ESC,back=BTN_LEFT,y=KEY_UP \ --ui-axismap y1=KEY_DOWN,x1=KEY_LEFT \ & ;; "after") sudo pkill -9 xboxdrv ;; *) echo "Need a paramter: 'before' or 'after'" esac

Obviously, you should tune the absmap, keymap, buttonmap and axismap lines to suit your needs (/opt/retropie/supplementary/xboxdrv/bin/xboxdrv --help-all and evtest /dev/input/event0 are your friends).

@Darksavior check the instructions made by joolswills in the comments here:
https://github.com/RetroPie/RetroPie-Setup/pull/1602

Maybe it get some improvements in the future, but you can change it currently.

Thanks I've tried remotting via putty into the SSH with the path you supplied but keep getting "permission denied"
I have also enabled SSH access via retro config on putty and retro Pi

Also can't seem to pull the data via emulation station.

Network mount of just the roms folder worked perfectly for Odyssey. Very nice call.

I was hoping it would somehow also fix the TGCD issue too but no dice unfortunately. Any thoughts there?

@Luca1 said in Retropie install missing emulators:

1 & 2 buttons seem to be mapping to 2 buttons on my arcade cab fine

Well, that's half the problem. As for the joystick, the software might be expecting to find an axis and isn't seeing one. I took a brief look at the Xin Mo controls and it appears to present itself as a keyboard with each button activating a key press. My arcade control system does the same thing, but I only use it for MAME.

If you're really intent on getting the arcade controls to work, you may have to find mapping software capable of mapping keyboard keys to a virtual controller. I've been looking for a similar solution for a while and keep coming up short. I know that xboxdrv can't do it and I'm pretty sure you can't do it in Joymap. You might want to look into Linux Joystick Mapper. There are also a few people on the forums here who have contributed to the development of UAE4ARM, so it's possible that they might find their way here and have some input as well.