[herbfargus]

These are my partial notes on installing on my odroid C1+:

https://github.com/retropie/RetroPie-Setup/wiki/Odroid

[herbfargus]

btw this is my latest modified module (should in theory automatically set the rom and bios folders. I haven’t tested yet but am testing now: Really advmess and advmame are essentially the same, just a few minor config differences.

#!/usr/bin/env bash

# This file is part of The RetroPie Project
# 
# The RetroPie Project is the legal property of its developers, whose names are
# too numerous to list here. Please refer to the COPYRIGHT.md file distributed with this source.
# 
# See the LICENSE.md file at the top-level directory of this distribution and 
# at https://raw.githubusercontent.com/RetroPie/RetroPie-Setup/master/LICENSE.md
#

rp_module_id="advmess"
rp_module_desc="AdvanceMESS"
rp_module_menus="4+"
rp_module_flags="!x86 !mali"

function depends_advmess() {
    getDepends libsdl1.2-dev
}

function sources_advmess() {
        wget -O- -q "https://github.com/amadvance/advancemame/releases/download/advancemess-1.4/advancemess-1.4.tar.gz" | tar -xvz --strip-components=1
}

function build_advmess() {
        ./configure CFLAGS="$CFLAGS -fsigned-char" LDFLAGS="-s -lm -Wl,--no-as-needed" --prefix="$md_inst"
        make clean
        make
}

function install_advmess() {
        make install
}

function configure_advmess() {
    mkRomDir "mame-advmess"
    mkRomDir "bbcb"

    moveConfigDir "$home/.advance" "$configdir/mame-advmess"

        su "$user" -c "$md_inst/bin/advmess --default"

        iniConfig " " "" "$configdir/mame-advmess/advmess.rc"
        iniSet "misc_quiet" "yes"
        iniSet "device_video" "fb"
        iniSet "device_video_cursor" "off"
        iniSet "device_keyboard" "raw"
        iniSet "device_sound" "alsa"
        iniSet "display_vsync" "no"
        iniSet "sound_samplerate" "44100"
        iniSet "sound_latency" "0.2"
        iniSet "sound_normalize" "no"
        iniSet "dir_rom" "$biosdir"
        iniSet "dir_artwork" "$romdir/mame-advmess/artwork"
        iniSet "dir_sample" "$romdir/mame-advmess/samples"
        iniSet "dir_image" "$romdir"
        iniSet "device_video_clock" "5 - 50 / 15.62 / 50 ; 5 - 50 / 15.73 / 60"

        addSystem 0 "$md_id" "mame-advmess arcade mame" "$md_inst/bin/advmess %BASENAME%"
        setESSystem 'BBC Micro Model B' 'bbcb' '~/RetroPie/roms/bbcb' '.bbc .BBC .img .IMG .ssd .SSD' '/opt/retropie/emulators/advmess/bin/advmess bbcb -floppy %BASENAME%' 'bbcb' 'bbc'
}

Once you have it compiled and running in the places you want it to be adding new systems will be easy. Basically you just add a new line at the bottom

addSystem 0 "$md_id" "mame-advmess arcade mame" "$md_inst/bin/advmess %BASENAME%"

the addSystem function assumes the system is listed in platforms.cfg. if not it needs to be either added or you can use the setESSystem function like so:

setESSystem 'Kodi' 'kodi' '~/RetroPie/roms/kodi' '.sh .SH' '%ROM%' 'pc' 'kodi'

Where the 7 (soon to be 8 with direct launch tag) are listed in this order: Full Name, name, rompath, Extensions, launch command, platform, theme.

https://github.com/RetroPie/RetroPie-Setup/blob/c20409eede07031bca09d6babd07e012e604ea96/scriptmodules/helpers.sh#L296-L331

Then Once you have added your system and you don’t want to compile advmess again just so you can configure a system you can type:

cd RetroPie-Setup
sudo ./retropie_packages.sh advmess configure

And it should configure the proper launch options (for each system you’ll also likely need to add its rom folder with mkdir <romfolder> in the configure function. Because of how many specific launch options there are with advmess its likely we’d have to do something similar to vice so that even though they are basically the same emulator we treat each game type as it its a different system.

[herbfargus]

Most people use mess with a gui so there isn’t much documentation on command line options. But you can follow the config examples on the github page above to get an idea of configs for each system.

This page was the most useful for me:
http://www.progettoemma.net/mess/sysset.php

Name column is the rom folder name for that system, and then if you select a sytem it shows you the options for command line (like if you’re loading a cartridge vs a disk image) and it also says which bios is required. I may look at modifying the module so that the rom folder paths are set to retropie’s rom folder and bios folder (can be set in the advmess.rc file)

[herbfargus]

I don’t know of any direct launch options for the BBC micro games though it’s probably possible with a script of sorts, I haven’t really looked into it all that much.

[herbfargus]

Not playably.

[herbfargus]

You create a file called advmess.sh in

/home/pi/RetroPie-Setup/scriptmodules/emulators/

And copy over the module listed in the link above and then you can install it from the experimental menu of the setup script and then just place everything in the paths mentioned. (The module could definitely be cleaned up)

[herbfargus]

As noted on the wiki there is a beta Mac version of clrmamepro.

[herbfargus]

Stay away from allwinner chips, they have terrible driver support and would have far too many incompatibilities to run retropie.

And no the A+ will not emulate the n64 or ps1 the raspberry pi 2 barely even emulates them. Those are best left to a pc if you want something playable.

[herbfargus]

I just tested Bussard out – Its pretty awesome: brilliant work

All its missing is some ambient space music in the background.

just as a reference for anyone else who is building a love game from a github repo you can follow this format in the configure function of the love script:

    # get Bussard for Love 10.0 (game data)
    if [[ ! -f "$romdir/love/bussard.love" ]]; then
        gitPullOrClone "tmp" https://gitlab.com/technomancy/bussard.git
        cd tmp
        zip -r "$romdir/love/bussard.love" "."
        rm -R "tmp"
        chown $user:$user "$romdir/love/bussard.love"
    fi

It can be run with

cd RetroPie-Setup
sudo ./retropie_packages.sh love configure

Mr. Rescue

    # get mrrescue-1.02d.love (freeware game data)
    if [[ ! -f "$romdir/love/mrrescue-1.02d.love" ]]; then
        wget "https://github.com/SimonLarsen/mrrescue/releases/download/v1.02d/mrrescue-1.02d.love" -O "$romdir/love/mrrescue-1.02d.love"
        chown $user:$user "$romdir/love/mrrescue-1.02d.love"
    fi

Sienna

    # get sienna-1.0c.love (freeware game data)
    if [[ ! -f "$romdir/love/sienna-1.0c.love" ]]; then
        wget "https://github.com/SimonLarsen/sienna/releases/download/v1.0c/sienna-1.0c.love" -O "$romdir/love/sienna-1.0c.love"
        chown $user:$user "$romdir/love/sienna-1.0c.love"
    fi

[herbfargus]

By default if you are using a gamepad they will be mapped to Top left and Top right triggers.

[herbfargus]

this is taken directly from the default retroarch.cfg

input_player1_a = x
input_player1_b = z
input_player1_y = a
input_player1_x = s
input_player1_start = enter
input_player1_select = rshift
input_player1_l = q
input_player1_r = w
input_player1_left = left
input_player1_right = right
input_player1_up = up
input_player1_down = down
input_player1_l2 =
input_player1_r2 =
input_player1_l3 =
input_player1_r3 =

l2 and r2 are the next/ previous weapon buttons for override syntax you may have to put the button in quotations like input_player1_l2 = "1"

You can also check out floobs video for core input remapping options

It looks like they only have controller hooks for next and previous weapon so I don’t think its possible to use the numbers as one gun per number selector.

[herbfargus]

would be /opt/retropie/configs/doom/retroarch.cfg

see this page

https://github.com/RetroPie/RetroPie-Setup/wiki/RetroArch-Configuration

I’m just assuming that they coded in hooks for those original values in the game, but I’m not entirely sure as I haven’t looked into it all that much.

[herbfargus]

Just to verify is it both the top numbers and the numpad that don’t work ? Are you using pr-boom or zdoom? Have you tried reconfiguring the controls with retroarch as the default is a retroarch based emulator

[herbfargus]

A bajillion. Actually just over a thousand, though I can’t say I’ve tested very many as I’ve only focused on the few that retropie doesnt have or that aren’t obscure enough that nobody would want. I’m guessing some just flat out wont work, others probably will have terrible performance, and there may be a few that perform well. If you have the time for testing I’d be interested in your results.

Just as an fyi MESS is more of a quantity over quality so they basically just puke out as many barely functioning systems as they can without too much regard to optimisations and whatnot. Standalone emulators and retroarch focus more on performance and optimisations hence why they usually run better than their MESS counterparts.

When I’m feeling really ambitious I may make a module for a few systems but I need to figure out if I want to mash it in with advmame or if I want it as a separate module with multiple system configurations. I haven’t really decided yet.

[herbfargus]

Sounds like your issue lies in having too many clones which can be managed more effectively with a building a merged set with clrmamepro:

https://github.com/RetroPie/RetroPie-Setup/wiki/Managing-ROMs#step-5–rebuild-a-rom-set

I would think that the filenames are out of the bounds of theme management and are rather a core emulationstation function which is much more of a headache to sort than a few xml files.

[herbfargus]

You don’t need a partition for windows to read. Just use samba shares:

https://github.com/RetroPie/RetroPie-Setup/wiki/first-installation#samba-shares-needs-an-active-internet-connection

[herbfargus]

In other words its simpler to start with a fresh image as it has less room for issues.

[herbfargus]

I got it working:

https://github.com/RetroPie/RetroPie-Setup/issues/210

[herbfargus]

Renaming it would be fine. You can just add a .bak to the filename

[herbfargus]

I wouldn’t count on the n64 running smoothly on anything but a pc and even then emulation suffers on some games. You can tweak settings and plugins to get some games working but there is only so much you can do even with a pi 2. That being said I definitely prefer a pi2 over my B+.

[herbfargus]

There is already preliminary support for x86. I wouldn’t count on drivers for different dev boards being supported as well as the rpi

[herbfargus]

Once we integrate this, it should simplify things a little bit (hopefully):

https://github.com/RetroPie/RetroPie-Setup/issues/1219

[herbfargus]

So your roms are in

/home/pi/RetroPie/roms/mame-mame4all

?

Because that’s where .037b5 romsets go if you want them to work.

https://github.com/RetroPie/RetroPie-setup/wiki/Managing-ROMs

[herbfargus]

Perhaps you should verify your rom folder paths and which ones correspond to each emulator:

https://github.com/retropie/retropie-setup/wiki/MAME

[herbfargus]

And you have roms in your mame folder?

[herbfargus]

It’s not in the experimental menu:

https://github.com/retropie/retropie-setup/wiki/PSP

https://github.com/retropie/retropie-setup/wiki/Updating-RetroPie

It will be under option 5.

And apt-get update has nothing to do with updating or installing emulators for retropie.

[herbfargus]

I installed mine directly with a USB keyboard rather than over ssh, I don’t know if that makes a difference. Really it’s more a novelty than a practicality and I’d definitely recommend hardware over it if you have it.

[herbfargus]

Switch the player index in retroarch.cfg.

[herbfargus]

You will run into problems on any hardware that isn’t a raspberry pi. The only hardware retropie is stable on is the raspberry pi and even then we are still working on things. Though there is also some support for x86 which means if you have an old laptop laying around with Linux on it you can install it on there as well.

[herbfargus]

Possibly with an executable shell script that kills lxde and starts emulationstation:

#!/bin/sh
pkill -9 -f lxsession
emulationstation

From here:

http://unix.stackexchange.com/questions/170029/command-to-log-out-of-lxde-directly

Likely you’ll need to amend it somewhat to get it working as I have not tested it

[herbfargus]

Yeah it looks like it installed fine, so it probably is a network issue of sorts but I wouldn’t have any idea on where to begin troubleshooting

[herbfargus]

its port 80 but I think it can be changed in the config.json maybe.

https://github.com/miroof/node-virtual-gamepads/blob/e40fe4968bf77cf77dd00384cf32b88eac68ae32/config.json

But if its on the same network I don’t see how that would block the port that way, but I am not familiar enough with network protocols to know how that stuff all works.

[herbfargus]

I just installed it again from a fresh image and it works fine, so its possible something may have happened during your install or some other issue with your network possibly.

[herbfargus]

That would have to be done by theme

[herbfargus]

I have an odroid C1+ and it sorta works but its a bit hacky at some points, definitely lacks the community support the raspberry pi has.

[Author]

Posts