[trimmtrabb]

cool, think i’m going to get one can’t go wrong for £14! What are your plans, are you making a portable unit?

[trimmtrabb]

Looks good for a small screen, thanks for the photos. Have you tried adjusting the aspect ratio, looks a bit stretched on the Mario game?

[trimmtrabb]

It could be Emulation Station isn’t picking up any roms where it expects to find them, so it’s not displaying any emulator pages, check the paths match in es_systems. You could also try putting a couple of roms on the SD card to see if ES picks them up. Also there might not be enough video ram allocated, double check your config.txt incase you have made a mistake.

[trimmtrabb]

Thanks for the guide! Been thinking of getting one of those lcd screens, what’s the quality like?

[trimmtrabb]

to check compatibility of roms:

PiFBA: http://code.google.com/p/pifba/source/browse/FBAcapex_src/gamelist.txt?spec=svn018b31d990231eccae5c57690cb5a4d55b6fa0e2&r=018b31d990231eccae5c57690cb5a4d55b6fa0e2

mame4all-pi: http://code.google.com/p/imame4all/wiki/GameList

[trimmtrabb]

did you edit es_systems to the new rom paths?

[trimmtrabb]

I had the same problem, try roms from another source and check the rom compatibility, not all roms are supported

[trimmtrabb]

Sorry I forgot you need to create a folder cfg in the mame4all-pi directory or it won’t save. Hope you sort your tv problem out!

[trimmtrabb]

[quote=6150]Hello, I followed your guide to install mame4all-pi and it worked just fine, thank you. Performance is much better now!

However, I have 2 problems:<br>
1. The installation somehow changed the resolution of both emuluationstation and the emulators itself so that now, they are “boxed”, meaning that the screen is only a box within my TV. They are still displayed in the correct aspect ratio (16:9 for emulationstation, 4:3 for emulators/games) but not fullscreen anymore. How can I change that back to what it was before??<br>
2. How can I use my gamepad in mame4all? It works fine with every other emulator and in emulationstation but not in mame4all.

thank you!!
[/quote]

Hi, to configure your gamepad connect a usb keyboard and press tab when you run mame4all-pi, this will bring up the GUI and you can map your buttons in there, including GUI keys (back/exit is the exit emulator key) Also check out mame.cfg for other options.

Regarding the resolution I have no idea why that has happened, installing mame4all-pi shouldn’t mess with any settings like that. Double check your config.txt, or it could be a setting on your tv.

[trimmtrabb]

in your es_systems you’ve got the rom path wrong, should be

PATH=/home/pi/RetroPie/emulators/mame4all-pi/roms

reboot and they should show up. change the rom path back to how it was originally in mame.cfg and you should be good to go

[trimmtrabb]

can you post the contents of your es_systems.cfg? Also double check that the paths are correct they may have changed.

[trimmtrabb]

Install mame4all-pi via the RetroPie setup script (Option 2 “Source based installation” then select only mame4all-pi) Then edit es_systems:

sudo nano /home/pi/.emulationstation/es_systems.cfg

And replace this:

DESCNAME=MAME 
NAME=mame 
PATH=/home/pi/RetroPie/roms/mame EXTENSION=.zip .ZIP 
COMMAND=/home/pi/RetroPie/emulators/RetroArch/installdir/bin/retroarch -L /home/pi/RetroPie/emulatorcores/imame4all-libretro/libretro.so --config /home/pi/RetroPie/configs/all/retroarch.cfg --appendconfig /home/pi/RetroPie/configs/mame/retroarch.cfg %ROM%" # alternatively: COMMAND=/home/pi/RetroPie/supplementary/runcommand/runcommand.sh 1 "/home/pi/RetroPie/emulators/pifba/fba2x %ROM%" PLATFORMID=23

with this:

DESCNAME=MAME
NAME=mame
PATH=/home/pi/RetroPie/emulators/mame4all-pi/roms
EXTENSION=.zip .ZIP 
COMMAND=/home/pi/RetroPie/emulators/mame4all-pi/mame %BASENAME%
PLATFORMID=23

Then reboot. Roms need to go in /home/pi/RetroPie/emulators/mame4all-pi/roms (you need to create the directory)

[trimmtrabb]

There’s no performance difference as long as you set the video ram to a maximum of 128mb, even then the only emulator that really needs that much is the Playstation one. 96mb should be fine for everything else.

[trimmtrabb]

Firstly if you haven’t already you should change the default emulator in RetroPie to mame4all-pi as it has much better performance. Search the forum on how to do this. Then the romset you need is 0.37b5

[trimmtrabb]

It could either be a power issue or an issue with the gamepad itself. I think we can rule out power as the pad will be drawing well under the limit the Pi can supply. Do you have another power source you can use to test? Try using your xbox pad and see if you have the same problem, if you do that would point to the power supply being the issue.

Looking up on Google it looks like somebody else has had problems with this pad so perhaps it is faulty: http://www.racketboy.com/forum/viewtopic.php?t=24887

[trimmtrabb]

Yes, James Pond 2 was a great game :-)

If you want to use an Xbox 360 wired pad this thread may help you setting it up: https://www.petrockblock.com/forums/topic/installation-problem/

I’m not sure why your SEGA pad is playing up, is there any pattern to the pad not responding and making any changes to the system at all, swapping usb ports etc? When it does play up try running lsusb in the terminal to see if it is still listed.

[trimmtrabb]

The free version of Paragon Partition Manager doesn’t support ext4 but the home version does, free trial here: https://www.paragon-software.com/home/pm-personal/download.html

[trimmtrabb]

Sounds ok, any other usb devices plugged in? Can you test the gamepad on a PC to rule out the gamepad being a problem

[trimmtrabb]

strange, what power supply are you using?

[trimmtrabb]

what axis does the d pad show as?

[trimmtrabb]

Try using Picodrive instead, info here: https://www.petrockblock.com/forums/topic/exiting-sega-master-system-emulator-osmose-from-controller/

[trimmtrabb]

what output do you get from jtest when pressing the dpad?

[trimmtrabb]

Not sure what’s gone wrong but you could try using the RetroPie image to get up and running

[trimmtrabb]

Hi, install jtest:

sudo apt-get install joystick

And then run:

jstest /dev/input/js0

If the controller is recognised you should be able to test the buttons.

[trimmtrabb]

Nice work, thanks for sharing :-)

[trimmtrabb]

I think Emulation Station is expecting input from js1, try deleting /.emulationstation/es_input.cfg and reboot to reset the ES controls

[trimmtrabb]

Try removing the other pad from that config so there’s just id 0

[trimmtrabb]

Hi, did you install xboxdrv via the setup script or manually? I’m not sure exactly what the script configures but if you run sudo nano /etc/rc.local check the last line reads:

xboxdrv –trigger-as-button –id 0 –led 2 –deadzone 4000 –silent &
sleep 1

[trimmtrabb]

can you post the contents of your es_systems.cfg

[trimmtrabb]

Ok, can you copy and paste the contents of your retroarch.cfg and es_systems.cfg

[trimmtrabb]

Ok, so now you can successfully configure the pad for Emulation Station and navigate the menus but it fails after reboot, correct? You are not having problems with over-responsive buttons anymore?
I have no idea why the pad is not responding after reboot, could be power issues. Try unplugging any other usb devices.

Can you confirm the pad functions correctly with jtest:
jstest /dev/input/js0

Regarding the input config menu (configures controls for the Retroarch emulators), the script does not work, to manually configure controls see here:

Input configuration script fails, bindings are off

[trimmtrabb]

N64 emulation really pushes the limits of what the Pi is capable of, only a few titles run close to playable speed. 2d based games are the limit really, although quite a few Playstation games will run nicely.

[trimmtrabb]

Run: rm /home/pi/.emulationstation/es_input.cfg and reboot then press some buttons on your PS3 pad to finish the ES config. Es_input should then list your pad which you can edit to the correct values.

Here’s mine for example:

<?xml version=”1.0″?>
<inputList>
<inputConfig type=”keyboard” />
<inputConfig type=”joystick” deviceName=”Xbox Gamepad (userspace driver$
<input name=”a” type=”button” id=”0″ value=”1″ />
<input name=”b” type=”button” id=”1″ value=”1″ />
<input name=”down” type=”hat” id=”0″ value=”4″ />
<input name=”left” type=”hat” id=”0″ value=”8″ />
<input name=”menu” type=”button” id=”9″ value=”1″ />
<input name=”right” type=”hat” id=”0″ value=”2″ />
<input name=”up” type=”hat” id=”0″ value=”1″ />
</inputConfig>
</inputList>

Use jtest to determine buttons:

sudo apt-get install joystick

then:

jstest /dev/input/js0

[trimmtrabb]

I got the command wrong, apologies. Try this via SSH:

nano /home/pi/.emulationstation/es_input.cfg

[trimmtrabb]

if you edit your es_systems.cfg (nano /home/pi/.emulationstation/es_systems.cfg) and scroll down to the Megadrive section you will see the supported rom filetypes. Try adding .sms and .SMS to that line (roms need to be in the Megadrive folder) and Emulation Station should pick them up on reboot.

I’m assuming Picodrive is installed on your setup by the way, it should be the default emulator in es_systems, if not you can install it via the setup script.

[Author]

Posts