[dankcushions]

mame 2003 uses mame .78 so I would try and rebuild from that if possible. I think that dat should work (I created it:)). did you download it from https://github.com/RetroPie/RetroPie-Setup/wiki/Managing-ROMs ? that’s where I personally upload to.

I’ll double check later tonight I uploaded the right one!

[dankcushions]

those cpu warning messages are a red herring – see https://github.com/libretro/RetroArch/issues/2574

you likely have some other error. please post the contents of /tmp/runcommand.log after recreating this issue

[dankcushions]

dispmanx is a ‘bare metal’ driver (sort of), so you may get better performance (not noticeable in my case, as all the cores seem to be CPU-bound), but it has been shown that it gives better input latency: https://www.petrockblock.com/forums/topic/best-possible-input-lag-with-retroarch/

i have been experimenting with dispmanx, but it has some issues. see: https://github.com/libretro/RetroArch/issues/2562)

[dankcushions]

oh- a pi1! that explains it :) sorry, assumed you were using a pi2!

[dankcushions]

looking great :) a drop shadow effect around the logos might look cool? after seeing it in mario maker i kinda love it!

[dankcushions]

sounds like some other problem. those cores should run fine with no overclock.

are you using shaders? are you getting the rainbow/voltage symbol in the corner? i’d get rid of all your overclock settings. maybe restore from a new image, even.

[dankcushions]

looks like you accidentally triggered https://github.com/RetroPie/RetroPie-Setup/wiki/runcommand and possibly changed the default snes emulator? if you trigger it again, select lr-snes9x-next as the default emulator – that should bring everything back to normal.

[dankcushions]

roms not saving won’t have anything to do with the exit emulator button – what roms do you mean? what emulator?

setting up the hotkeys, again, it depends on the system, emulator, etc. it’s all in the wikis but maybe we can direct you to the right bit.

[dankcushions]

yes. you’ll probably have to rebind the buttons to make it a bit more sensible, but i have done it

[dankcushions]

we’ve spent quite a bit of time creating streamlines mame/fba romset xmls that don’t include clones/non-working/adult/gambling/etc games, for each of the mame/fba emulators. have a look here: https://github.com/RetroPie/RetroPie-Setup/wiki/Managing-ROMs (second half of this page)

[dankcushions]

seems decent! if it’s popular, the community will come.

i wonder if it’s so cheap because it’s a bit of a loss-leader for revenue they hope to get from add-ons or android store sales? the raspberry pi organisation don’t really see any revenue after the initial sale, so it has to be all-in.

[dankcushions]

what mame emulator? there’s many available on 3.2.1. with anything that is retroarch-based (lr-…), you use select + X to bring up the menu.

[dankcushions]

this looks great! one thing to be mindful of if anyone doesn’t already know – any metadata changes are not saved unless you ‘exit emulation station’ or press f4 – shutting down or terminating does not exit ES cleanly.

[dankcushions]

i think with retroarch the ideal scenario would for it to map these options as core options, but both mame2003 and mame2010 are pretty ‘beta’ – a proof of concept, really. they don’t appear to be seeing much development so i’m not hopeful :(

libretro/retroarch seem to be focussing most on the latest mame core https://github.com/libretro/mame, but who knows if that one is viable on ARM/the pi. i think we might be stuck with these older, less supported cores.

[dankcushions]

yeah i think all the configuration is just handled by retroarch, and saved in retroarch.cfg or in the retroarch-core-options.cfg. i think most stuff you’d care about for mame setup is handle by the retroarch settings. the only thing i can think that isn’t is core input remapping, which is important for mame as you’re not going to find one controller setup that works for every game (another issue is logged for this), yet you still want the RGUI to use the same buttons on retropad.

it’s weird we can even access that mame tab menu at all given that it doesn’t seem to save anything from it! i would expect it to be disabled in retroarch.

[dankcushions]

apparently this is now fixed (thanks to jools and stefan)! update retropie-setup, install individual emulators, and grab the latest mupen64plus binaries.

[dankcushions]

regarding the internal mame settings not saving: https://github.com/libretro/mame2003-libretro/issues/11

[dankcushions]

normally with mame you have all the files required for each game within the games zip (a ‘merged’ set) – there’s no other bios files needed. if they’re in the .zip file, they don’t show up as anything additional in emulationstation – just one entry for each .zip (game). this is also how the scrapers will expect to find the roms, for chksum etc.

eg, for mame 2003, your ~/roms/mame-libretro/ folder should have fantjour.zip with 12 files in it:

	<game name="fantjour" cloneof="gokuparo" romof="gokuparo">
		<description>Fantastic Journey</description>
		<year>1994</year>
		<manufacturer>Konami</manufacturer>
		<category>Shooter / Flying Horizontal</category>
		<nplayers>2P sim</nplayers>
		<verAdded>.67</verAdded>
		<rom name="300a01.34k" merge="300a01.34k" size="131072" crc="d5fa95f5" sha1="c483aa98ff8ef40cdac359c19ad23fea5ecc1906"/>
		<rom name="321_b06.9c" merge="321_b06.9c" size="131072" crc="da810554" sha1="f253e1aa137eecf283d8b083ef2b3b049e8366f4"/>
		<rom name="321_b07.7c" merge="321_b07.7c" size="131072" crc="c47634c0" sha1="20e4105df5bbc33edd01894e78f74ed5f173576e"/>
		<rom name="321b09.30g" merge="321b09.30g" size="1048576" crc="94add237" sha1="9a6d0a9727e7fa02d91ece220b145074a6741a95"/>
		<rom name="321b12.13g" merge="321b12.13g" size="524288" crc="5f9edfa0" sha1="36d54c5fe498a4d0fa64757cef11c56c67518258"/>
		<rom name="321b17.9g" merge="321b17.9g" size="2097152" crc="b3e8d5d8" sha1="6644a414e7f0e69ded9aa1bf892566002cebae26"/>
		<rom name="321b18.7g" merge="321b18.7g" size="2097152" crc="2c561ad0" sha1="6265054072ba1c2837dd96e0259b20bc50457160"/>
		<rom name="fj-jap.17h" merge="fj-jap.17h" size="2097152" crc="437d0057" sha1="30c449200e0510dc664289b527bade6e10dbe57a"/>
		<rom name="fj-jap.25g" merge="fj-jap.25g" size="2097152" crc="c6e2e74d" sha1="3875a50923e46e2986dbe2573453af5c7fa726f7"/>
		<rom name="fj-jap.28g" merge="fj-jap.28g" size="2097152" crc="ea9f8c48" sha1="b5e880015887308a5f1c1c623011d9b0903e848f"/>
		<rom name="fsus27b.bin" size="524288" crc="b2cfe225" sha1="7fd43acb1dd853a7980e7fcf48971ae28175e421"/>
		<rom name="fsus31b.bin" size="524288" crc="afaf9d17" sha1="a12214c6e634862d6507f56719b55d4a23a0ef0f"/>
	</game>

and since fantjour is a clone of gokuparo, you’ll also likely (or possibly not, as it seems they haven’t been properly merged in the xml i’m looking that) need that zip with another 12 files:

	<game name="fantjour" cloneof="gokuparo" romof="gokuparo">
		<description>Fantastic Journey</description>
		<year>1994</year>
		<manufacturer>Konami</manufacturer>
		<category>Shooter / Flying Horizontal</category>
		<nplayers>2P sim</nplayers>
		<verAdded>.67</verAdded>
		<rom name="300a01.34k" merge="300a01.34k" size="131072" crc="d5fa95f5" sha1="c483aa98ff8ef40cdac359c19ad23fea5ecc1906"/>
		<rom name="321_b06.9c" merge="321_b06.9c" size="131072" crc="da810554" sha1="f253e1aa137eecf283d8b083ef2b3b049e8366f4"/>
		<rom name="321_b07.7c" merge="321_b07.7c" size="131072" crc="c47634c0" sha1="20e4105df5bbc33edd01894e78f74ed5f173576e"/>
		<rom name="321b09.30g" merge="321b09.30g" size="1048576" crc="94add237" sha1="9a6d0a9727e7fa02d91ece220b145074a6741a95"/>
		<rom name="321b12.13g" merge="321b12.13g" size="524288" crc="5f9edfa0" sha1="36d54c5fe498a4d0fa64757cef11c56c67518258"/>
		<rom name="321b17.9g" merge="321b17.9g" size="2097152" crc="b3e8d5d8" sha1="6644a414e7f0e69ded9aa1bf892566002cebae26"/>
		<rom name="321b18.7g" merge="321b18.7g" size="2097152" crc="2c561ad0" sha1="6265054072ba1c2837dd96e0259b20bc50457160"/>
		<rom name="fj-jap.17h" merge="fj-jap.17h" size="2097152" crc="437d0057" sha1="30c449200e0510dc664289b527bade6e10dbe57a"/>
		<rom name="fj-jap.25g" merge="fj-jap.25g" size="2097152" crc="c6e2e74d" sha1="3875a50923e46e2986dbe2573453af5c7fa726f7"/>
		<rom name="fj-jap.28g" merge="fj-jap.28g" size="2097152" crc="ea9f8c48" sha1="b5e880015887308a5f1c1c623011d9b0903e848f"/>
		<rom name="fsus27b.bin" size="524288" crc="b2cfe225" sha1="7fd43acb1dd853a7980e7fcf48971ae28175e421"/>
		<rom name="fsus31b.bin" size="524288" crc="afaf9d17" sha1="a12214c6e634862d6507f56719b55d4a23a0ef0f"/>
	</game>

[dankcushions]

sorry – i’m probably off on threaded video – that’s a retroarch setting and this isn’t a retroarch emulator! however there does seem to be some sort of audio issue with mupen64plus – https://github.com/RetroPie/RetroPie-Setup/issues/1124

[dankcushions]

this is a great idea! love the main image! agreed about centring it, though.

on the game page i’d left-align the game list and something bugs me about the grey borders – make it look too cramped maybe? just my immediate reaction though!

[dankcushions]

old video but might help with your flashing 360 controller!

yep, scraper needs to be online to work – how did you connect the pi to your laptop? i have mine connected with a network cable into the back of my router, but a wifi dongle should work also.

[dankcushions]

the mode key might work, but it might be used for internal functions of your controller (eg, mine has a ‘turbo’ button) and not be usable by the pi.

maybe re-run the controller configuration and bind C button to select? if that works then it looks like there’s an issue with not binding a hotkey, as i would expect that to just disable hotkey functionality, rather than bind it to single buttons.

not sure about your xbox issue, sorry! looking at https://github.com/RetroPie/RetroPie-Setup/wiki/Setting-up-the-XBox360-controller, once you’ve installed the driver i would follow step 1, but you’ll only need 1 entry if you have only 1 controller

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

(probably best to have someone who has the controller confirm first!)

[dankcushions]

it almost seems like your hotkey is configured incorrectly, as all of these functions should normally be only triggered when the hotkey is held AND those buttons are pressed.

when you run the controller configuration thing in emulation station, what do you use for ‘select’? that is the default hotkey, and i’m guessing the megadrive controller clone doesn’t have a select button? perhaps there’s an issue with NOT having a hotkey defined…

[dankcushions]

i have the same issue, so giving you a bump! seems to happen in mario kart 64 also.

i’ve not tried it, but you might want to try turning off video_threaded in retroarch.cfg – i think it’s bad news for performance but it might ensure the sound stays in sync??

[dankcushions]

welcome :)

first off, do i store games on the sd card or off a usb storage device?
either – SD card by default

if i can store them on card, will the emulators deal with zip or rar files or do they need to be unzipped? this would largely determine how big a card i get.
some emulators work with zip files, others don’t.

also, what controller works with this?
i think pretty much any USB wired controller will work.
will a wired 360 work?
yep!
is anyone trying to get the steam controller to work?
have a look here – https://www.raspberrypi.org/forums/viewtopic.php?f=78&t=125804 – not sure if that means it works with retropie but i’d have thought so

[dankcushions]

yeah if you use these settings your performance will be worse for some games. i have a pretty aggressive over clock and haven’t managed to get great performance with these settings.

[dankcushions]

the game you have on the screen at the moment appears to be 1942, or something like that? those games are done at a vertical orientation (originally a TV on it’s side, i think).

that said, if you’re using lr-mame2003 or lr-fba-next, go settings > video > change the ‘aspect ratio index’ to the one with “(1:1 PAR)”. one of these (i forget which) has a default aspect ratio setting that makes all these vertical scrolling games look messed up.

the games will still have big black borders, but not as bad as in your shot :) and it’ll be as they should look. if you don’t like the borders still you can mess about with the aspect ratio setting and stretch the games further :)

[dankcushions]

this is a known issue with retroarch. see:
https://github.com/libretro/RetroArch/issues/2230
https://github.com/RetroPie/RetroPie-Setup/issues/1072

[dankcushions]

/opt/retropie/configs/all/retroarch-core-options.cfg

:)

[dankcushions]

when you remap the controls in the GUI it should start working? is it that your ‘insert coin’ button (usually select) isn’t working, so you can’t actually get control of the games in the first place?

anyway, if you do need to remap to get it working, the default save-as config file name (libretro.cfg) is not the one it uses. it should be named retroarch.cfg

so, you can either go into /opt/retropie/configs/mame-mame4all/ and rename libretro.cfg to retroarch.cfg,

or, you can go into /opt/retropie/configs/all/retroarch.cfg and change the ‘save config on exit’ (forget what it’s called) option to ‘true’, and then remap again (don’t need to save – just exit the emulator and it will save in your existing mame-mame4all/retroarch.cfg)

[dankcushions]

so i’ve just downloaded the latest retropie_setup script (with the updated retroarch.sh) and rebuilt retroarch from source. dispmanx appears as a video driver in the RGUI, and if i select it and restart the game it works, but…
– it has what appears to be the video_smooth option set to true, regardless of the config setting (possibly the smoothing/scaling is hard-coded to the driver??)
– it crashes when you go into the RGUI menu unless you turn off video_threaded to false (and also do the same, or comment out the same entry in /all/retroarch.cfg) – does this happen for anyone else?
EDIT: i seem to get these display crashes in all cores and with video_threaded = “false” :( just need to load the RGUI to trigger after a few seconds.

this is all in FBA-next running neogeo games, btw.

[dankcushions]

the latest version of fba-next is only for the dipswitches in the core options – you can switch to AES/unibios in RGUI in your version FYI. it’s in the core options menu.

[dankcushions]

[quote=111138]
2) Ah, so the latest version of fba-next lists all the service mode options under Core Options? That sounds ideal. You said I can update the emulator through the RetroArch GUI? You mean the one that comes up with Select + X? I wasn’t aware that you could update an emulator through that interface. I think I can also update individual emulators through the Retropie Setup menu, right?

[/quote]
you can! i would do it via the retropie-setup menu – i’m not sure if it’ll work properly through the RGUI. also, you need to update from source, as this change isn’t in the binaries yet. it’s an option when you do the ‘update individual emulators’ thing (and it takes about 1hour!) – probably a good idea to back up first if you can.

i still haven’t full tested with it but i think it’ll do what you want it to do – i can experiment later tonight and report back!

[dankcushions]

1) i think you need to tap X rather than hold it. i just mash it until the menu appears.

2) two ways – change the core options to use the unibios and access dipswitch settings via a button combo during the neogeo logo, or update to the latest version of the emulator which puts all the dip switches in the core options in the RGUI (which is better as you can save your setup to a .cfg for that game). both of these mean you need to go into the retroarch GUI – do you know how to do that?

3) i assume they mean the retroarch render resolution, which is accessed via the menu in 1). however i don’t think that really applies to the Pi2 as you’re not going to be GPU bound in most cases, unless you use a shader. i run everything in ‘output’ resolution, which matches my display, which is 1080p.

[dankcushions]

good work, thanks :) i do think the raspi-config default ‘pi2’ overclock is bad – SDRAM at 500 is very aggressive and caused instability on my system, whilst the cpu/core can run at 1000/500 without any voltage increase for me.

i’m interested in some more specific benchmarking. eg, with n64 performance i get sound and frame-rate issues on occasion, but i’ve not experimented enough to prove whether it’s GPU/CPU/core/memory/etc bound. i think mostly with emulation it’s likely to be CPU-bound, but when running shaders or 3d emulators at 1080p (how i run n64), that could change.

there’s a lot of GPU overclock options that i haven’t really looked at yet: http://elinux.org/RPiconfig#Overclocking_options

[Author]

Posts