Messages

1

General / Re: Attract Mode vs Retroarch question

« on: March 11, 2016, 02:59:57 PM »

"[rompath][name].7z" (with quotes) at the end seems to do the trick for libretro. (just a note, I don't seem to have the [romext] variable on my build for some reason so I just added the ".7z")

Ok, the rom loads, but my keybindings are messed up (I seem to have pressed arbitrary buttons for all the important stuff during the retropie setup). It asks for the "Type OK if you're a pirate". Where's the .cfg I can use to set...

...deez keys?


...alcohol is involved, it's friday

2

General / Attract Mode vs Retroarch question

« on: March 11, 2016, 10:28:27 AM »

So I've loaded Retropie up on an SD-card, installed the mame libretro-cores (2003 and 2010) installed LXDE and compiled Attract Mode and got it working.

Now I'm stuck at configuring libretro in AM's menu, I've got:

Code: [Select]

Executable : /opt/retropie/emulators/retroarch/bin/retroarch
Commandline Arguments : -L /opt/retropie/libretrocores/lr-mame2010/mame2010_libretro.so [romfilename]
Rompaths : $Home/pi/RetroPie/roms/mame-libretro/
Extensions : ZIP,7z,DIR

For some reason this setup forgets to add fileextensions to the end of the parsed line when run, so when I run Bubble Bobble I get:

Code: [Select]

/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mame2010/mame2010_libretro.so /home/pi/RetroPie/roms/mame-libretro/bublbobl
Instead of what I should have gotten:

Code: [Select]

/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mame2010/mame2010_libretro.so /home/pi/RetroPie/roms/mame-libretro/bublbobl.7z
I've also tried just adding the ".7z" after the [romfilename] in the commandline arguments. This seems to create the correct launch-command, but it still fails with a "rom not found". OTOH, if I run the command from a terminal (in X) outside AM, then the rom loads correctly.

Am I going about this completely wrong or...?

3

General / Re: OSMC (Raspberry Pi2)

« on: March 11, 2016, 07:41:28 AM »

Yes, it does.

Right now I'm trying with a retropie-image, disabling emulationstation and then installing lxde for X. Then I'll compile Attract Mode.

4

General / Re: Recommended software-setup for Raspberry Pi 3 MAME-machine wanted.

« on: March 10, 2016, 08:09:02 AM »

I think it'd be counterproductive to run mame 0.171 (unless it's for the sake of running 0.171 ofc ); on the RPi2 they talk about 50% slowdowns running Outrun and Gauntlet with 0.171. Color me optimistic but I expect to play more than Donkey Kong and Galaga at full speed on the RPi3

Retroarch huh? I'll take a look at it.

BTW I managed to compile advmame with SDL by using "./configure --disable-fb". It seems to work, it doesn't complain about X anymore, it just can't find the roms.

But but but... the same thread discouraged the use of sdl since that would rule out use of OpenGL ES (which the pi supposedly is capable of).

So that's the next conundrum: Running Attract Mode in X while launching the mame-client outside X for GL ES support. I gather GL ES support would be nice in regards to shaders, but I wonder if there is any performance gain emulation-wise.

5

General / Re: Recommended software-setup for Raspberry Pi 3 MAME-machine wanted.

« on: March 10, 2016, 03:12:21 AM »

Sorry Omegaman, I've given up for now. There just isn't enough info out there yet on compiling stuff specifically for the RPi3, and stuff compiled for the RPi2 is a no-go (tried the 0.171 you linked, it took 30 seconds just to load mame).

I can get Jessie on there and have the hardware work. But then get stumped at the "AM wants X but advmame doesn't"-problem and the "compiling-instructions are there, but not with hardware- and X-support"-problem.

I'm absolutely positive that it should be possible, I'm just not good enough I can solve dependencies and do basic compilation, but I'm at a loss if I have to start editing make-scripts and configure flags.

This would be the ideal setup so far: Image for the RPi3 with Dietpi, whatever X-setup that makes sense, AM (hardware-accelerated?), Advmame 0.94 & 1.4 (compiled to work with X in order to work with AM and hardware-accelerated), wifi-setup-script (think it comes with DietPi), samba-shares setup.

For now here's a script I stumbled upon that compiles and installs AM succesfully on a clean install (works on RPi3 + Jessie):

Code: [Select]

cd ~
mkdir develop
sudo apt-get install cmake libx11-dev libx11-xcb-dev libflac-dev libogg-dev libvorbis-dev libopenal-dev libjpeg8-dev libfreetype6-dev libxcb-randr0-dev libxcb-image0-dev libxcb-util0-dev libxrandr-dev libxcb-ewmh-dev libxcb-keysyms1-dev libxcb-icccm4-dev libudev-dev libavutil-dev libavcodec-dev libavformat-dev libavfilter-dev libswscale-dev libavresample-dev libfontconfig1-dev
cd ~/develop
git clone -b rpi https://github.com/mickelson/SFML sfml-pi
mkdir sfml-pi/build;cd sfml-pi/build
cmake -DEGL_INCLUDE_DIR=/opt/vc/include -DEGL_LIBRARY=/opt/vc/lib/libEGL.so -DFREETYPE_INCLUDE_DIR_freetype2=/usr/include -DFREETYPE_INCLUDE_DIR_ft2build=/usr/include/freetype2 -DGLES_INCLUDE_DIR=/opt/vc/include -DGLES_LIBRARY=/opt/vc/lib/libGLESv1_CM.so -DSFML_BCMHOST=1 ..
sudo make install
sudo ldconfig
cd ~/develop
git clone --depth 1 https://github.com/mickelson/attract attract
cd attract
make
sudo make install


6

General / Re: Recommended software-setup for Raspberry Pi 3 MAME-machine wanted.

« on: March 09, 2016, 01:14:22 PM »

A little update:

I went with raspbian jessie. Compiled Attract Mode, it works.

But...

Then I installed all the mame emulators available from source (wanted to try out some different ones) using the retropie-script. They got installed alright, but strange errors abound:

advance-mame (both 0.94 and 1.4) refuses to run in X since the script compiled them to use framebuffer instead of SDL. I have no idea how to compile it with sdl support. Tried running it another tty but it complained of missing roms even though the path was correct in the .rc-file.

mame4all doesn't recognize 7zip'ed roms, it runs fine if I unpack the contents into a dir, but that's hella messy. Kinda strange.

Also tried compiling advmame manually, but by then there were conflicts and broken packages because the retropie-script had installed a bunch of stuff not in the repos.

I think I'll wait for image nitrogen widget is cooking up 

7

General / Re: Recommended software-setup for Raspberry Pi 3 MAME-machine wanted.

« on: March 09, 2016, 04:19:06 AM »

Ah that's nice to know. I already have a retropie setup on an RPi2 (stuffed in a GAEMS Vanguard case, dedicated to all pre-N64 consoles; I've made an arcade-cabinet for my current MAME-project). I guess I could steal the emulator installation script from there and build on top of Jessie, I'm not really keen on taking retropie to the chop-shop

8

General / Re: Recommended software-setup for Raspberry Pi 3 MAME-machine wanted.

« on: March 09, 2016, 02:25:02 AM »

Raspbian works fine for me on my PI2. Optimized for the pi, supports wireless out of box. What's not to like. 

Ok? I just got the impression there was a lot of hullaballo about using a lean image in order to optimize performance. Which MAME do you use, and when does it start to choke (for instance it'll probably run Double Dragon full speed, but not Street Fighter 4; when does the hardware-limitations start to take its toll)?

9

General / Recommended software-setup for Raspberry Pi 3 MAME-machine wanted.

« on: March 08, 2016, 06:10:27 PM »

It's all in the headline. Which software should I use for a dedicated arcade-frontend-like MAME-machine if I'm on a Raspberry pi 3?

OS: Dietpi? https://github.com/Fourdee/DietPi/issues/216
DE / X-windowmanager: ? (I suppose attract need some kind of graphical environment to run in)
Which version of MAME: ? (performance vs newer something something)
Which Romset: ?

I'm currently trying to compile on raspbian jessie, which I guess would be a waste of resources; but right now it's the only distro I've managed to get both samba and wifi to work on concurrently (samba is black magic to me), so i figured I'd cut my teeth on that until I knew the optimal software-composition.