[petrockblog]

there is an option in the “Setup” menu or use

sudo ./retropie_packages.sh stella configure
sudo ./retropie_packages.sh dispmanx

as mentioned above. note you will have to have updated your retropie-setup script first. if it has been some time since you updated, you will need to do a new binaries install as emulator paths have changed.

[petrockblog]

I’ve made some uae4all changes.

If you update the RetroPie-Setup script, and then do

sudo ./retropie_packages.sh uae4all configure

it will update the es_systems.cfg and fix up the launching script too which was broken. you can then do

sudo ./retropie_packages.sh dispmanx

and configure the uae4all emulator to use the dispmanx SDL. this should solve the black screen issue.

note that paths have changed recently, so if you haven’t updated for some time, you should nuke /opt/retropie and do a new fresh binaries install.

[petrockblog]

there are some problems with some recent uae4all changes I made so I need to fix them up also (to do with launching / parameters)

[petrockblog]

Please check this post

Atari 2600 Stella locks up after exit

it might help (replacing stella with uae4all)

changing the output mode may help (lowering or increasing depending). Enabling dispmanx may help too.

[petrockblog]

HDMI or composite ?

What is your default video resolution ?

If you have the latest retropie-setup script, please try

sudo ./retropie_packages.sh runcommand
sudo ./retropie_packages.sh stella configure

and try again. if you get a black screen then go to launch it, but press x or m on the keyboard a few time before it loads and you should get a video output settings. you could try setting it to your native screen resolution. You should probably then do

sudo ./retropie_packages.sh dispmanx

and turn on dispmanx sdl for this emulator. it should then nicely scale up to your native resolution.

[petrockblog]

sounds right to me.

[petrockblog]

http://www.raspberrypi.org/introducing-turbo-mode-up-to-50-more-performance-for-free/

We’ve been doing a lot of work to understand the impact of voltage and temperature on lifetime, and are now able to offer a “turbo mode”, which dynamically enables overclock and overvolt under the control of a cpufreq driver, without affecting your warranty. We are happy that the combination of only applying turbo when busy, and limiting turbo when the BCM2835’s internal temperature reaches 85°C, means there will be no measurable reduction in the lifetime of your Raspberry Pi.

so I wouldn’t worry :)

[petrockblog]

I’m pleased my video output changes have turned out to be useful :) thanks for the feedback.

[petrockblog]

You will know if you have a recent runcommand.sh installed as when launching a rom it will say “Press ‘x’ or ‘m’ to configure video output options for emulator name”

[petrockblog]

no, sorry I wasn’t particularly clear on that. it’s all managed from the main retropie scripts.

quickest way is to do

sudo ./retropie_packages.sh runcommand

[petrockblog]

I believe the mapper stuff in scummvm is still in development or not completed. There might have been some improvements since the last release though so I’ll have a look at the source history/tickets.

[petrockblog]

oh and another thing I didn’t mention – is when you first launch scummvm from emulationstation, and add some games, on exit it will add those games to the emulationstation menu (requires a restart of emulationstation).

I basically incorporated a similar method as https://www.petrockblock.com/forums/topic/guidescript-add-all-your-scummvm-games-to-emulationstation/#post-4814 into the scummvm launcher.

[petrockblog]

You can also test with the dispmanx configuration – under SETUP menu – enabling it or disabling it for scummvm. This is another recent new feature where you can switch emulators to use the dispmanx SDL or not (off by default). This can help with performance and issues with crashes with framebuffer output.

you can run it manually by doing “sudo ./retropie_packages.sh dispmanx”

[petrockblog]

Are you not able to use the mapping gui to map the virtual keyboard ? It certainly worked for me to map it against other keys, but I don’t have a usb gamepad to test.

regarding other points:

the old scummvm is still installed. You can remove it with “sudo apt-get remove –purge scummvm”

regarding the crash – I didn’t see that on my system – are you using hdmi or composite output ? what resolution are you running scummvm in? (Please do a runcommand.sh update – and test with switching the screen mode – after updating/reinstalling the runcommand setup it now supports a per emulator and per rom video output mode – on launch you can switch res by pressing “x” or “m”)

[petrockblog]

changes are merged now, so if you update your script, you can try building / testing the newer scummvm.

[petrockblog]

RetroPie-Setup currently installs the raspbian scummvm package (an older version). It doesn’t actually build it from source at all. My changes now switch over to building from source – so if you currently run sudo ./retropie_packages.sh scummvm it will just install the raspbian package.

You need to wait for my commit yeh, unless you want to checkout my branch beforehand. I actually have commit access to the main repository, but some stuff I do via pull requests as it is useful for feedback/comments from Florian (and others).

Sorry if I confused things :)

[petrockblog]

for individual items the commandline is much easier.

sudo ./retropie_packages.sh

for a list of packages

for scummvm you would do

sudo ./retropie_packages.sh scummvm

and it will go through the process. Scummvm wasn’t a source based packages before, so it will just install the debian package unless you have switched to my scummvm branch.

[petrockblog]

https://github.com/retropie/RetroPie-Setup/pull/551

[petrockblog]

I have the virtual keyboard working. By default it opens on a long press of middle mouse button, or ctrl+f7, but ctrl+f8 opens up the keymapper gui where a key can be assigned. Just finishing off the module configuration and I can submit the code. It requires a source build of scummvm.

basically all this works out of the box on the latest release, the options just need enabling via the ./configure script

[petrockblog]

it is emulationstation re-initing etc. It is not an intentional/configurable delay.

[petrockblog]

it was an experimental module when the last binaries archive was created, you will need to build it manually from source.

from a commandline/console you can build individual packages using “retropie_packages”

in this case run

sudo ./retropie_packages.sh mupen64plus

(Note it could take sometime to build)

[petrockblog]

by default also the keys n and m in retroarch will cycle through the shaders.

[petrockblog]

nice job :)

[petrockblog]

Glad you got it sorted :)

[petrockblog]

the image contains partitions and should be written to the main sdcard block device device, not a partition of said device. so if you device is /dev/sdb it should be written to that not /dev/sdb1

sdb1 would have been partition 1 of an existing partition table on the sdcard.

However I recommend to avoid accidents you use dd if=image of=/dev/disk/by-id/YOURUSBDEVICE (so you don’t overwrite a system disk or something)

for example on my system cards in my sdcard reader will show up as

/dev/disk/by-id/usb-Generic_Storage_Device_00000000000006-0\:0
(with existing partitions having -part1 and -part2 appended)

[petrockblog]

I have recently changed the configs for fastdosbox / ripx86 in retropie so they share the same emulation station menu. However I have more work to do, as I will be replacing fastdosbox with svn dosbox.

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

I will also add a configuration in set up for dosbox to switch dispmanx on/off for it.

[petrockblog]

I will look into adding a “from source” build of scummvm to retropie with the virtual keyboard enabled (as from that page it looks as though it is enabled by default – the wheezy version is also pretty old, and that is the version that is installed as part of retropie currently.

[petrockblog]

I am referring to the “frontend input configuration” under the section

[frontend]
#Keyboard controls for frontend only

that is for the built in launcher/frontend which we don’t use in retropie.

[petrockblog]

the frontend input configuration in mame.cfg is for the built in mame4all launcher/GUI which we do not use.

[petrockblog]

retropie comes with rpix86 and fastdosbox – I believe they both share the same emulationstation key (a bug), so probably rpix86 is set up by default. “sudo ./retropie_packages.sh fastdosbox configure” should enable fastdosbox.

[petrockblog]

for a minimal / controlled install you can also use the “retropie_packages.sh” script, which is a commandline tool for installing packages. run it without parameters for instructions. You can then do things like

“sudo ./retropie_packages mame4all” to get sources/build/install/configure mame4all or

“sudo ./retropie_packages mame4all sources” to just get mame4all sources and so on.

[petrockblog]

The retropie-setup script needs a few changes to avoid adding experimental stuff to menus during a binary install. I’ll get onto that.

there have been large changes in retropie in recent weeks to separate source and binary and reworking of the modules. This means that a lot of stuff has moved/been renamed in /opt/retropie – it might be worth removing /opt/retropie (after saving any of your customisations) and and /etc/emulationstation/es_systems.cfg and do the binary reinstall again. You may need to remove the ~/RetroPie/roms/ports/* stuff too beforehand.

[petrockblog]

yeh you can’t use the team-xbmc ppa for arm.

there is an xbmc under “experimental” menu in retropie – did you try that ?

[petrockblog]

(the emulationstation config for the libretro nes emulator only looks for .nes files – it may well handle zips. I will check and fix up the config generation)

[petrockblog]

You seem to have almost answered your own question. you need to unzip the roms.

[Author]

Posts