[petrockblog]

the xbmc module is beta and needs some work to fix up dependency installation it seems. I’ll make a mental note of it. I’m still working though the emulators one by one fixing up stuff (vice for example is much improved for 2.4.2 image)

[petrockblog]

and what is the output of this command from the terminal:

grep "BasiliskII" /etc/emulationstation/es_system.cfg

[petrockblog]

please give me details of exactly the filenames and file locations (output from ls -la / pwd for example)

the filesystem is case sensitive – they need to be lowercase.

are you running the latest retropie image 2.4.x ?

[petrockblog]

are you using retropie 2.4.x image ? please download the latest image, and if you get a black screen on exit, please give me details of your system config (screen output/resolution etc), and which emulator. thanks.

[petrockblog]

retropie comes with a working basiliskii and it doesn’t require manual building etc. it also doesn’t require X to run. the latest version (check the image downloads for ready / setup image), looks by default for a mac.rom and a disk.img file in the ~/RetroPie/roms/mac folder – I have tested it booting a prebuilt image files from http://www.redundantrobot.com/sheepshaver-tutorial/ with the performa rom.

if wanting to replicate our build elsewhere, check out the source in our repository in scriptmodules/emualators/basilisk.sh

you can also use retropie to build manually by doing

sudo ./retropie_packages.sh basilisk sources
sudo ./retropie_packages.sh basilisk build
sudo ./retropie_packages.sh basilisk install
sudo ./retropie_packages.sh basilisk configure

or

sudo ./retropie_packages.sh basilisk

which will do all of the above.

[petrockblog]

Could be the hardware triggering it – so you are using the analogue audio out from the pi from the headphone socket ? Have you tried switching PSU etc? it could be related to what the pi is doing, rather than a software trigger. I would try some solutions presented when googling – there are a few.

you could also extract the audio from the HDMI socket or use a usb soundcard or something.

Not all the emulators support zips, but retroarch should work.

is the script executable ? chmod u+x it.

[petrockblog]

[quote=85098]I had these issues with the previous versions, so I may have something mis-configured.
[/quote]

1. Are there emulationstation navigation sounds? I hear none. I installed ESConfig, and force headphone output.
[/quote]

nope.

[quote=85098]
2. If I launch MAME (mame4all) I get a lot of background static/noise/sound.
[/quote]

I don’t get that here. And no other emulators affected ?

[quote=85098]
2a. I have followed suggestions about overclocking, forcing headphone output, etc, but I can’t seem to get rid of the static. The static does not get output when in terminal or lxde.
[/quote]

have you tried looking into things like

http://www.crazy-audio.com/2013/09/raspberry-pi-power-supply-noise-on-the-5v-rails/
or getting a ground loop isolator or something.

You would do better to take the audio out form HDMI though

[quote=85098]
3. When in a MAME game and I enter the TAB menu, I have some sort of controller conflict. The menu forcibly scrolls up when no keypress.
3a. I am using an Ultimarc IPAC as my controller via USB. So, really it’s just a keyboard.
[/quote]

not seen this. can’t advise sorry.

[quote=85098]
4. NES and N64 Roms won’t load. I have them in their respective .ZIP files. EmulationStation sees them but I get a blank screen when launching.
[/quote]

this is not enough information to help with really. nothing outputted at all before the screen is blank ? tried unpacking the zips also ?

[quote=85098]
5. Ports. I have the Doom 1 and Doom 2 wads. When I try to launch Doom 1, it says ../rom/ports/Doom 1.sh not found. It is there.
[/quote]

are you sure you are running the new image ? There is no file of that name in the new image – it is called “Doom 1 Shareware.sh”

[petrockblog]

lynx is now available and vectrex went in today as an experimental module.

[petrockblog]

fastdosbox is removed and replaced with dosbox (which is actually faster than our previously compiled fastdosbox)

[petrockblog]

use retropie 2.4 (or update script and do a complete binary install again).

in sudo ./retropie_setup.sh SETUP menu configure uae4all to use dispmanx

should solve the black screen issue.

[petrockblog]

If you got a Fatal Error it’s possible not everything installed correctly. The project has been going through heavy development, and it’s possible there were some bugs when you ran it. Please do sudo ./retropie_setup.sh – update the script – exit and run it again and do the first option (btw there is no need to run update binaries before doing that – the first options also updates the binaries).

If you get any errors please post me a log.

[petrockblog]

It is not pre-installed. Did you google it – search for “raspbian install lirc” and you will find some guides.

[petrockblog]

it is a graphics/windowing api, which can be utilised by a modified sdl 1.x. Many emulators when using the framebuffer directly can be problematic, and running with the dispmanx sdl can solve these issues (it can also scale without performance loss).

[petrockblog]

just to do with the source file permissions. They should all be 644 really, but it doesn’t really matter.

[petrockblog]

none that I know of :)

[petrockblog]

it works fine here – it starts x and opens up xterm in the top left (by default). Is that what you mean?

There is no desktop environment included here by design (to keep it small). you can still run stuff under x if required, or install a desktop environment/window manager if you need it. Nothing in retropie requires it though.

if you installed a window manager startx will look different – eg. sudo apt-get install fvwm and then run startx.

[petrockblog]

Yep. there is no need or advantage to use fastdosbox – and our previously compiled fastdosbox wasn’t any faster than debian dosbox. Fastdosbox is based on an older dosbox codebase than our build, and has very little difference over dosbox codewise.

http://www.raspberrypi.org/forums/viewtopic.php?f=78&t=95421

[petrockblog]

the ./retropie_setup.sh script

[petrockblog]

http://www.dosbox.com/wiki/Usage

Usage

name
If name is a directory, DOSBox will mount the specified directory as the C drive.
If name is an executable, DOSBox will mount the directory of name as the C drive, and start executing name.

add the extension of the executable also – and make sure the path is right etc.

note you should “apt-get remove dosbox” and use the retropie packaged version for best performance – /opt/retropie/emulators/dosbox/bin/dosbox

(get the latest retropie 2.4 beta image or update binaries on your current one if it isn’t there)

[petrockblog]

Go to retropie-setup and choose “configure emulators to use dispmanx” and enable it for vice

[petrockblog]

Oh and if you add a game to scummvm from the scummvm gui, it should add it to the emulationstation menu (after a restart). This was based on an idea posted on this forum, and seemed sensible to incorporate it.

dosbox is also about 2-3 times faster, as we worked out how to compile it with the ARM recompilation core. it also mounts the roms/pc folder as C: on start.

[petrockblog]

Watching video now – Nice job – thanks. Very detailed and informative.

I contributed a fair amount of the new bits n pieces so wanted to make a couple of comments.

It’s X or M for the menu because I originally used M (for menu ;-) ) and then realised I couldn’t use it on my picade but I could use X – so I added X also – since nothing else is happening at that point I thought it wouldn’t really matter to have two keys ;-)

Regarding the runcommand.sh menu – glad you like it – I was happy how it turned out. One additional feature is that if you choose a 50hz/60hz mode, the refresh rate is passed on to retroarch, which could help with timings for pal/ntsc games etc (in theory – I’ve only given it limited testing)

Apologies for the retropie hostname bug – it sneaked in there. the image will be updated asap with the retropie hostname in /etc/hosts

enabling dispmanx (as well as what you said in the video), can also help with some emulators that freeze/crash when rendering directly to the framebuffer. it can help with performance also as you mentioned, for some emulators as they can render at a lower resolution, and it can be upscaled by dispmanx SDL in hardware.

One main thing behind the scenes is that source and binaries are now separated, so the /opt/retropie contains binary data rather than source. This makes it a bit tidyer and it should use up less space.

New stuff that is happening right now:

The binaries distribution has been split into multiple archives. If you update retropie-setup you can now install binaries individually (from retropie_packages.sh (sudo ./retropie_packages modulename install_bin). We can introduce a new menu for selectively installing/configuring emulators – it should make it easy for people to set up a customised system with just a few emulators they want without having to build from source

Multiplatform support – some initial code has gone in that would allow retropie to be more easily adapted for other arm hardware like the odroid etc. This is currently WIP, and should be transparent to Pi users.

Cheers.

[petrockblog]

I found a major problem that happened due to the order of a few lines of code that got changed by me today. This may have been the cause of problems IF you updated the script today.

Please update the script, and try again and it should set things up correctly.

Of course, you may have another issue if you hadn’t updated the script.

[petrockblog]

oh yeh. that needs updating too – I thought I had mentioned that in the other thread.

that sdl error isn’t fatal afaik, i think stuff usually runs anyway, but i’d have to check.

I don’t have any time right now to look into this, but when i update jzintv I will check it’s working etc and fix up any issues I find.

[petrockblog]

thanks for the updated source.

[petrockblog]

did you do

sudo ./retropie_packages.sh jzintv configure

(or run the main install binaries script again which will run configure for everything). the dispmanx configuration requires that the es_system.cfg is updated with latest configuration from the jzintv retropie module.

[petrockblog]

Did you update the retropie script first ?

[petrockblog]

if not – let me know which and what happens and I’ll try and help.

[petrockblog]

They should all be exitable?

[petrockblog]

add a new es_systems.cfg for say “media files” point it to a location with some files (maybe a remote mount or something), and use something like omxplayer ? it could then just use the emulation station browser to show a list of media to play.

alternatively you could make a little script you launch that uses something like

FILE=$(dialog --stdout --title "Please choose a file" --fselect $HOME/ 20 60)

to get a file path via a little file browser

http://askubuntu.com/questions/488350/how-to-prompt-users-with-a-gui-dialog-box-to-choose-file-directory-path-via-the

[petrockblog]

what sort of update did you run ?

please update the script again, and do a full binaries install perhaps. a lot of stuff has changed recently. Or check out the new 2.4 beta image as a new starting point.

[petrockblog]

The best way of building a very compact raspbian would be to start from debootstrap. (There are some tutorials on this around the net).

If removing stuff, you could remove xorg /xserver and related packages – anything that relies on it would then get removed too. You can also remove many libraries, icons / fonts etc. check out /usr/lib / usr/share and do “du -sh | sort -h” and you will get a sorted listing of what uses what. You can then google what stuff is and work out if it would be ok to remove.

Or just start with my minimal retro pie and go from there :)

[petrockblog]

the only issue you might have now is performance – but with dispmanx enabled for those emulators that use the framebuffer with no acceleration, they should do better at 1080p (hardware upscaling via dispmanx sdl). that is of course if they render to a reasonable lower resolution first.

[petrockblog]

I guess the quickest way would be to remove the roms folder, and create a symlink to your usb drive. no need to change any configs then.

[petrockblog]

congrats on the new arrival :)

[Author]

Posts