[petrockblog]

Change aspect_ratio_index in /opt/retropie/configs/all/retroarch.cfg to force to the aspect of your screen.

for my dev monitor (5:4) that would be aspect_ratio_index = “10”

you can count from 0 in the retroarch gui settings to work out the value without having to save the entire retroarch.cfg or can configure from there / save new config and extract the value needed.

[petrockblog]

I assumed you were on a rpi2 – the emulator is not available for the rpi1. Then you must have another problem – something broken in your set up. Please provide some information – eg rpi model, which image you installed and so on.

[petrockblog]

See https://github.com/Aloshi/EmulationStation/issues/265 – will require code changes.

[petrockblog]

not sure what you mean by adjust going forward, but the input configuration for ES is in ~/.emulationstation and for retroarch it is stored in /opt/retropie/configs/all/retroarch.cfg for keyboard and /all/retroarch-joypads for controllers.

I recommend reading through the wiki as a lot of information is there (plus this forum)

[petrockblog]

so it was a psu issue then. Usually is.

as for the “ok” press the key you defined as “a”

[petrockblog]

and make sure you are launching es from the binary directly and not our launch script to rule anything in that out.

[petrockblog]

likely due to it not being attached to a TTY when launching via the other methods.

you could try adding

</dev/tty >/dev/tty

to it perhaps.

You can add extra logging to runcommand.sh by putting set -x at the top of the script (and perhaps adjust ES launching of it it to redirect all output to a file).

I can’t advise further without you producing some logs.

[petrockblog]

updating from 2.3 to 3.0 requires more than that (unless you nuke /opt/retropie first). You can re-install the simple theme from retropie-setup. Better to start with a fresh 3.0 I think.

[petrockblog]

people have already made 3.0 images https://www.petrockblock.com/forums/topic/updating-retropie-3-0-in-berryboot/

you can’t update from 2.3 to 3.0 without some manual work – if you delete /opt/retropie and do an install from binary that should work though and give you a fresh 3.0 set up – you will still need to clean up some old rom folder names in ~/RetroPie

If you want to keep any of configs, it requires manual merging / cleaning up etc – so upgrade is possible, but not recommended unless you know what needs doing.

[petrockblog]

Try this – https://github.com/RetroPie/RetroPie-Setup/issues/946#issuecomment-130401096

[petrockblog]

try 256 ? increase more if needed.

No idea regarding berryboot specifically though as I don’t use it. I guess more gpu will not be needed for kodi, so you will have less ram usable.

If you have a rpi2 it won’t matter as they have 1gb of ram.

[petrockblog]

as i said, you were launching the script manually via “sh script” so the first line is ignored. No point adding it at all if launching like that, but if you wanted to make it executable it needing fixing.

don’t run it as root, ES / our launcher script is not designed to be run as root (only the setup script).

you didn’t answer if there was anything saved in /tmp/runcommand.log

when you launch emulation station normally, it is actually launched from a script (in /usr/bin/emulationstation), so not sure what your problem might be. You are running on the system directly and not over ssh right ? Try launching from the pi itself – it’s not designed to be launched over ssh.

[petrockblog]

yes via config.txt

[petrockblog]

tnanks.

Instead of editing bluez-simple-agent try passing it the command parameter “-c DisplayYesNo”

After checking the source it seems to use this parameter – it isn’t documented it seems. should save having to edit it (to force the security theme used)

[petrockblog]

glad you have it sorted.

Please do add it to the wiki https://github.com/RetroPie/RetroPie-Setup/wiki/First-Installation so others can benefit. thanks.

[petrockblog]

have you installed https://github.com/abstrakraft/cwiid ? I think you need a daemon so that the wiimote sends joypad or keyboard presses.

[petrockblog]

Don’t know where to add what ? hdmi_drive ? that goes to /boot/config.txt (you can add it via the pi, or by editing on a PC)

You should spend some time reading up on configuring the raspberry pi – http://elinux.org/RPiconfig and other sources. It will be easier to advise if you understand the basics.

[petrockblog]

or launch it with bash scriptname – no point adding #!/bin/sh etc if going to launch via shell manually. just chmod u+x and launch without.

[petrockblog]

your script is missing a slash (/bin/sh instead of bin/sh). Nothing logged in /tmp/runcommand.log ?

In case it’s related to the shell, does it make any difference if you use /bin/bash instead (rather than /bin/sh which is dash)

[petrockblog]

well it’s more an issue of memory usage. this perhaps could be improved, but I doubt it will happen anytime soon.

Emulationstation needs a lot of GPU memory – just increase the memory allocated to gpu if needing to run a lot of systems.

[petrockblog]

retropie 3 ?

Please detail your power set up (you mention a hub, but don’t mention if it is powered).

check the output from dmesg etc from terminal (you can paste it via pastebin.com if you want me to have a look).

sounds like power issues to me though, or a hardware problem/fault.

[petrockblog]

You should open a new thread – you have a different problem.

the button for “a” should work. No idea if not – but it’s not a retropie bug but something with your setup. check your pi is getting enough power etc. Perhaps try another Key for A also ? Are you running from a fresh rpi3 image ?

[petrockblog]

You can open a ticket if there isn’t already one and we can remove the limit or increase it further. We had it removed before, but when upstream fixed it, we assumed they had tested their code, I guess not!

[petrockblog]

Increase gpu_mem in config.txt ?

[petrockblog]

May well be hard coded – the core is new and still a work in progress – https://github.com/libretro/fuse-libretro (You can report issues / request features on the libretro github page)

[petrockblog]

re-install emulationstation from binary via menu 5 of retropie-setup and it will reset its input configuration.

However it sounds like you might have another issue, as it should be able to pick up the keyboard despite your changes. With USB devices not working as they should, the first thing to check is PSU and USB cable – as if the pi isn’t getting enough power than can cause problems.

[petrockblog]

have you overclocked ?

You can also go to retropie-setup script, supplementary menu and go to “Edit RetroPie/RetroArch configurations” – then choose Change common RetroArch options and select “all/retroarch.cfg” to edit and change the “video_threaded” option to true – you can set this just for the specific libretro core also from the same menu rather than globally.

[petrockblog]

you can update individual emulators from the latest source from retropie-setup menu 5.

[petrockblog]

The original file is correct, but the resulting image is not. It does not unpack to 7.51 GB – the unpacked size is 2200000000 bytes – something has gone wrong there.

the md5sum of the unpacked image is b3c489015d2f37b917da8e999465144d

[petrockblog]

That doesn’t match up the ES binary from either rpi1 / rpi2 retropie 3.0 images. So either it is somehow corrupt or you have downloaded another image.

Please give me the filename / size and md5sum of the image you are writing (and the url where you downloaded it from)

[petrockblog]

please exit to a terminal or ssh in, and type

md5sum /opt/retropie/supplementary/emulationstation/emulationstation

and paste the output.

[petrockblog]

assuming you are using retropie 3, configure the controls in emulationstation and it should set them up for retroarch.

re-installing from binary wont reset any configs to default, as it preserves existing configurations. Maybe you would be best starting from a fresh image.

[petrockblog]

The bug has now been fixed in retropie if you reinstall dgen, but I wouldn’t recommend this emulator really over picodrive – as it isn’t retroarch based so may need manual configuration for controls etc (Unless you need it due to a picodrive compatibility issue)

[petrockblog]

Despite you saying you downloaded the rpi1 image, it still sounds like you are running the rpi2 image.

You would be better off with purchasing a rpi2 for retropie – but it wont matter too much if you only want to emulator older systems.

[petrockblog]

updating the script and re-installing the binaries is the update mechnism – only you may need to merge in new configs, as no old configs will be overwritten (to stop it overwriting customisations).

[Author]

Posts