[dudleydes]

Try the fix below

controller-mapping-issue-es/#post-82880

[dudleydes]

There is Freeablo which is a recreation of the Diablo 1 engine. More info at the link below.

http://freeablo.org/

It does require game data which is difficult to find. Also, I don’t know if anybody has managed to compile the source code for the pi. And if it did, I’m not sure how well it would run.

[dudleydes]

When the wired connection to the pi is lost, the PS3 controller will try to pair with its bluetooth master, your PS3 unit. I found the easiest answer is to unplug your PS3 from the mains whenever you wish to use your pi.

[dudleydes]

Ports are where old games designed to run on one platform such as DOS are converted to run another platform such as Linux. They can occur when the source code is released, for example Doom in 1997. Developers then begin to adapt the code, taking advantage of modern enhancements such as the SDL libraries which allow for use of modern game controllers. You can find out more, including a list of notable ports, at the following Wikipedia link.

https://en.wikipedia.org/wiki/Source_port

You can follow my tutorial on how to install the Wolfenstein 3D port, Wolf4SDL, at the link below.

http://dosonthepi.blogspot.com/2015/01/install-wolf4sdl.html

It’s worth comparing the performance of the port and Wolfenstein 3D run in DOSBox (you can find a link to a tutorial on how to do this at my blog).

I’ll post more tutorials on the blog. If there’s any ported game you’re interested in then let me know.

[dudleydes]

Could you provide a link to the source code and documentation for the Blood port? I shall put it on my list for future tutorials.

[dudleydes]

Yes, you can press TAB and then select Input (general). In the menu, you have the chance to select a controller button to UI cancel (exit mame4all).

[dudleydes]

I have published a tutorial on how to add DOS games to Retropie using DOSBox.

http://dosonthepi.blogspot.co.uk/2015/01/run-dos-games-in-retropie_15.html

In a future tutorial, I’ll describe how to configure game controllers.

[dudleydes]

I’ve only tested it in DOSBox but you can try the DOS Games Archive.

http://www.dosgamesarchive.com/download/wolfenstein-3d/

You will need to use DOSBox to install the game and gain access to the game files.

Before you compile, you will need to edit the file version.h to make sure the binary works for your game files. I don’t think this was done in your script. Judging from the name of the zip file, I think this is shareware version 1.4 so you need to leave line 10 (#define UPLOAD) and line 12 (#define CARMACIZED) uncommented.

[Edit 21 Jan]

I can confirm that the above works. You may have to reboot after you have compiled the binary.

[dudleydes]

You can assign a key to exit mame4all-pi by pressing TAB in-game. I don’t think there’s a default.

[dudleydes]

Ok, thanks. If there’s any testing on jzintv you’d like to be done, then please let me know and I’d be happy to do so.

[dudleydes]

I have found out why dispmanx wasn’t enabled. It was because I hadn’t updated the runcommand script since June 2014. In any case, I ran
sudo ./retropie_packages.sh jzintv configure
as it provided the command to make sure dispmanx was enabled for jzintv.

Now a rom will not launch. I get the following output in the console:

ERROR: MAC Dispmanx - the program is calling SDL_ListModes. That shouldn't happen.
gfx/SDL Error:
Powering on HDMI with preferred setting

before returning to ES.

Incidentally, I could only get audio for the new build of jzintv by adding a -a22050 flag.

[dudleydes]

Thanks, Buzz. I compiled a new version of the Intellivision, jzintv, which fixed a bug that was breaking keyboard hacks. The SVN source is available at the following link: http://spatula-city.org/~im14u2c/intv/dl/jzintv-svn-20141028.zip.

On exit from jzintv, I get a black screen and the pi is completely unresponsive. I can SSH into the pi but sudo reboot doesn’t work. The only way to reset the pi is through a power cycle. There is a long-running issue at the ES github (../EmulationStation/issues/206) that suggests that it’s affecting other non-Retroarch emulators such as VICE.

There is a fix at this post – ../emulationstation-not-restarting-on-emulator-exit/#post-81307. I tried to write a script that would replicate this but I can’t seem to get the exit command in step 2 working as it’s an inbuilt command. Also, I’m not entirely sure why typing exit should relaunch ES.

I also followed this thread ../atari-2600-stella-locks-up-after-exit/ which described a similar situation to mine. I have tried to enable dispmanx for jzintv. I installed dispmanx from the (updated) Retropie setup script and then enabled it for jzintv, also from the setup script. I am still getting a black screen on exit. Now I’m not sure whether dispmanx doesn’t solve the issue for jzintv or whether dispmanx wasn’t enabled as I had compiled jzintv from an alternative source to the Retropie script.

Any advice would be appreciated.

[dudleydes]

By exit-able, I assume you mean that the emulator exits successfully back to emulationstation. If so, then you can include mame4all-pi.

[dudleydes]

This is a long-standing issue regarding ES2 and a number of emulators. You can read the full thread here.

https://github.com/Aloshi/EmulationStation/issues/206

There are 2 fixes you could try.

1. Force VGA by editing the RPi config file and uncommenting the lines hdmi_group=1, hdmi_mode=1.

2. Try lonehelmet’s fix posted on 18 Sep 2014 at the EmulationStation issue thread.

[dudleydes]

For the PS3 controller, you can try the fix at the following post:
https://www.petrockblock.com/forums/topic/controller-mapping-issue-es/#post-82880

[dudleydes]

What happens if you launch one of the games?

The formatting on this forum doesn’t make clear where a link is. Click the text “tutorial for using rpix86” in my previous post to find the tutorial.

[dudleydes]

The first thing I did was install DosBox on my desktop. That way, I familiarised myself with how a DOS emulator works. You can follow the tutorial at the DosBox wiki to get you started. There are plenty more tutorials and videos available online to help.

rpix86 is the faster emulator as well as being the default emulator in ES so you may want to try this first on your pi. You need to place your unzipped game folders in the ~/RetroPie/roms/pc folder and they should appear in ES. Then check out the tutorial for using rpix86.

FastDosBox is an optimised version of DosBox for the pi so it should run in the same way. If you want to try it, then you will need to change the shell command (<command> section) for PC(x86) in es_systems.cfg to

<command>/opt/retropie/emulators/fastdosbox-1.5src/dosbox</command>
Bear in mind, I have not tested the DOS emulators in Retropie. I am still playing around with them in Rasbpian so I can get to grips with how they work before I’ll be happy to introduce them to my Retropie build.

[dudleydes]

I have noticed that the rom path in the mame.cfg in the compiled binary package is incorrect. It should read /home/pi/RetroPie/roms/mame.

I was testing in Raspbian using the default directories explaining why it worked for me.

You may also want to change the samplerate in mame.cfg to 22050 if you are having trouble with sound.

[dudleydes]

Take a look at the last post in the PS3 controller thread at the mame4all-pi source.

https://code.google.com/p/mame4all-pi/issues/detail?id=33

Tititatoo has attached a binary compiled version of mame4all-pi which you can use to replace those on your system. I have tested it and it works.

[dudleydes]

Try my fix at the following post:

https://www.petrockblock.com/forums/topic/controller-mapping-issue-es/#post-82880

[dudleydes]

I’m not an expert so I cannot offer a solution that’s guaranteed to work. Maybe you could try the suggestions in the last post in the thread below.

http://www.pimame.org/forum/discussion/1314/error-during-compile-of-mame4all-pi-sources/p1

[dudleydes]

Could you try recompiling with a CFLAGS parameter as below:

make CFLAGS+=”-lrt”
Let me know if it works and I’ll update the wiki.

https://github.com/retropie/RetroPie-Setup/wiki/Setting-Up-a-PS3-controller-for-mame4all-pi

[dudleydes]

If it is only with Bluetooth you are having problems then the accelerometers may be enabled in your sixad profile (assuming that you are using sixad to pair your controller). You can check with the following command

sudo nano /var/lib/sixad/profiles/default
For the accelerometers to be disabled, the profile should look as below with the last four parameters (enable_accel, enable_accon, enable_speed, enable_pos) set to 0.

enable_leds 1
enable_joystick 1
enable_input 0
enable_remote 0
enable_rumble 1
enable_timeout 0
led_n_auto 1
led_n_number 1
led_anim 1
enable_buttons 1
enable_sbuttons 1
enable_axis 1
enable_accel 0
enable_accon 0
enable_speed 0
enable_pos 0

[dudleydes]

You can get the PS3 controller to connect via Bluetooth without having to configure it in ES everytime by adding a sleep command in the script that launches ES.

At a command line, run the following:

cd /usr/bin/
sudo nano emulationstation

After the #!/bin/bash line, before the $es_bin, add the command sleep 5.

My script now looks like:

#!/bin/bash

sleep 5
es_bin="/opt/retropie/supplementary/EmulationStation/emulationstation"

nb_lock_files=$(find /tmp -name ".X?-lock" | wc -l)
if [ $nb_lock_files -ne 0 ]; then
    echo "X is running. Please shut down X in order to mitigate problems with loosing keyboard input. For example, logout from LXDE$
    exit 1
fi

$es_bin "$@"

Save, exit and reboot. When the sixad service has started and the pi doesn’t seem to be doing anything, press the PS button on your controller. When ES has launched you controller should now be working.

I found 5 seconds was sufficient for the Bluetooth controller to connect. ES for me takes 25 seconds to load so another 5 doesn’t really add much.

[dudleydes]

You can configure your controller by launching a ROM, pressing TAB on a keyboard to bring up the MAME UI and selecting Input (general) or Input (this game).

Forum member Floob has created a video that demonstrates this.

Configuring MAME with USB controller

[dudleydes]

The code for mame4all-pi rejects controllers with more than 6 axes. There is a fix at the wiki:

Setting Up a PS3 controller for mame4all-pi

You should be able to check whether the F710 has more than 6 axes by using the jstest tool. It’s worthwhile doing so as recompiling mame4all can take 3 to 4 hours.

You may also want to try using the F710 in DirectInput mode before recompiling. More info at Logitech support.

Using the input mode switch on the F710 to select DirectInput or XInput

[dudleydes]

I have managed to get jzintv to compile, albeit on Raspbian but it should work in Retropie.

Here’s what I did.

1. Unzip the jzintv-svn folder and copy it to your pi.
2. Change your working directory to jzintv-svn/src and edit Makefile.
3. Change the line that reads

OPT_FLAGS = -O6 -fomit-frame-pointer -fprefetch-loop-arrays -msse #-DBENCHMARK_STIC
to

OPT_FLAGS = -O3 -fomit-frame-pointer -fprefetch-loop-arrays -march=armv6 -mfloat-abi=hard -mfpu=vfp
4. Run the command make.

Here are some links that I found useful.

jzintv Thread at Raspberry Pi forum

Instructions to compile jzintv and integrate it into existing Retropie install

[Edit]

I made my earlier post when jzintv was compiling (which took about 30 minutes) but there is one more step to run jzintv, at least in Raspbian. I think, in Retropie, you should be able to get jzintv to run by editing the es_systems.cfg file

You need to edit the .bashrc file which is in your home directory. At the bottom, add the following lines:

export PATH=$HOME/jzintv-svn/bin:$PATH
export JZINTV_ROM_PATH=$HOME/jzintv-svn/rom

[dudleydes]

The Atarti 2600 emulator should work as the previous poster says.

For Intellivision to work, you need two bios files, exec.bin and grom.bin, which you need put in the /usr/local/share/jzintv/rom folder. More info on how to do this at the wiki page.

https://github.com/retropie/RetroPie-Setup/wiki/Intellivision-Emulator

[dudleydes]

Good to hear you got MAME working.

To change the aspect ratio, you need to edit the retroarch.cfg file by running the command

sudo nano /opt/retropie/configs/all/retroarch.cfg
Add the following line to run games in 16:9,

video_aspect_ratio = 1.78
Save and exit. You’re good to go.

I’ve not tried the N64 emulator so I can’t help you there.

[dudleydes]

You can find how to set up your PS3 controller for mame4all-pi at the link below.

https://github.com/retropie/RetroPie-Setup/wiki/Setting-Up-a-PS3-controller-for-mame4all-pi

[dudleydes]

You need to assign a button on your controller to exit mame. After you have launched a rom, press TAB on your keyboard to bring up the mame UI. In the Input:General menu, there should be an option to configure how to exit mame.

[dudleydes]

The newest Retropie-Setup-Script contains auto config files for PS3 controllers so your controller should work out of the box. The dhomium3009 guide is out of date regards this.

You can find the mappings for PS3 bluetooth controller at
https://github.com/retropie/RetroPie-Setup/blob/master/supplementary/RetroArchConfigs/PS3ControllerBT.cfg.

The file should be in your /home/pi/RetroPie-Setup/supplementary/RetroArchConfigs folder on your pi.

To exit a game, you need to press SELECT and START at the same time.

[dudleydes]

You can find a fix for the PS3 controller and Mame4all-pi at the Retropie Wiki

https://github.com/retropie/RetroPie-Setup/wiki/Setting-Up-a-PS3-controller-for-mame4all-pi

I can’t say whether it’ll work for the other controllers but it may be worth a try.

[dudleydes]

The code in your es_systems.cfg file has set mame4all-pi as its default MAME emulator.

Any text between the tags <!–text–> represent xml comments so you do not need to delete the <!–alternatively> command. Emulationstation ignores this code and won’t run imame4all at all.

[dudleydes]

Mame4all-pi was the default MAME emulator on my image of Retropie v2.2.

The command for the MAME emulator in my es_systems.cfg file is

<command>/opt/retropie/supplementary/runcommand/runcommand.sh 4 "/opt/retropie/emulators/mame4all-pi/mame %BASENAME%"</command>

[Author]

Posts