[petrockblog]

There are no roms – sam coupe uses floppy disks ;-)

-end pedantic mode-

[petrockblog]

Also see if there are any settings on your screen you can tweak in reagrds to display size/zoom. Also check settings here – http://elinux.org/RPiconfig (maybe trying other other modes / hdmi safe mode etc)

[petrockblog]

afair overscan_left / right etc won’t affect ES, just the framebuffer – but usually overscan_scale=1 solves problems of it being offscreen – you said you have tried that so im out of ideas. You didn’t post your config.txt though.

[petrockblog]

http://raspberrypi.stackexchange.com/questions/6972/location-of-berryboots-config-txt

(This came up first on google – as mentioned in it you probably need to mount the first partition somewhere).

retropie itself doesn’t use the config.txt – it’s used by the pi firmware.

[petrockblog]

my instructions require typing in some commands manually into the terminal – it’s not a matter of looking for the files/folders via samba share. Unfortunately debugging this will require you to learn how to go to the commandline and type in basic commands – there are tutorials on this.

I can’t help otherwise I’m afraid – apart from recommending trying a fresh image. If it doesnt work with a fresh image, I can only thing there is something wrong with the roms you are using.

[petrockblog]

I can’t think lirc is related, unles something adjusted the config.txt for the system – maybe you have some conflicting settings in config.txt ? Perhaps you can paste it via pastebin or similar.

or start with a fresh retropie image – and if that works, compare the configs ?

[petrockblog]

It also sounds like you need to spend some time reading the wiki or watching some tutorial videos on how to use retropie – as switching emulator is one of the core features etc.

[petrockblog]

I would prefer to debug with a libretro core, so

with

lr-pocketsnes

please switch to that and try it first. then ssh in to retropie (using putty on windows or if on another system another ssh client)

and do

/opt/retropie/emulators/retroarch/bin/retroarch --verbose -L /opt/retropie/libretrocores/lr-pocketsnes/libretro.so --config /opt/retropie/configs/snes/retroarch.cfg ~/RetroPie/roms/snes/SNESROMNAME

putting in your game rom name etc.

and then paste me the outputted text via pastebin.com or similar

Snes emulation does work – so either your roms are bad, or your install is bad. it might be worth re-imaging and trying again too.

[petrockblog]

Very nice – how about an update with the new logo ? :)

I might even be persuaded to have a video splash then – which I never thought I would say ;-)

[petrockblog]

What display do you have ? how is it connected? does changing videomode in config.txt help ?

Make sure you have tested both with and without overscan_scale – and also try disable_overscan=1

[petrockblog]

you can also edit those files from retropie-setup “Edit RetroPie/RetroArch configurations” under supplementary menu. saves dropping to terminal etc.

[petrockblog]

Have you tried adjusting the overscan options in /boot/config.txt ?

[edit] sorry misread – but have you tried all the overscan settings – including overscan_scale ?

[petrockblog]

I guess you may not have tried other emulators if you don’t know which one is being used ?

[petrockblog]

don’t assume – check via the pre-launch menu – press keypad 0 or press a keyboard key when the screen goes black before the emulator is launched.

[petrockblog]

ok let’s go through this step by step.

Which snes emulator are you using (please choose a specific one and we will debug it from there).

We can then try it from commandline to see what is failing.

[petrockblog]

What you pasted has nothing to do with retropie :)

[petrockblog]

Look up where the file is located on a berryboot setup – I don’t use it myself – but Google knows.

[petrockblog]

im assuming you are using the retropie 3 splashscreen init.d script (/etc/init.d/asplashscreen) ? worth putting that on pastebin or similar for me to check.

[petrockblog]

please paste the contents of /etc/profile.d/10-emulationstation.sh

[petrockblog]

go to retropie-setup (eg from within ES) and update the script, and then disable / re-enable auto starting emulationstation from the supplementary menu of retropie-setup.

[petrockblog]

update retropie-setup, and disable then re-enable emulationstation autostarting from the supplementary menu.

[petrockblog]

You likely don’t have enough memory allocated for the gpu. There are many threads about this on the forum.

not sure why deleting /opt/retropie didn’t work – that’s pretty much how my image build script prepares a new release from the old (it removes /etc/emulationstation too but that shouldn’t have mattered).

[petrockblog]

I assume you have sourced different bios files to make sure ? What is the extension of your rom files ? Providing the md5sum of your bios files may help.

[petrockblog]

wrong system bios files or bad/non working rom or something perhaps.

I have just tested it with “burgertime” and it works fine.

[petrockblog]

try launching it from terminal to see what is going wrong

/opt/retropie/emulators/jzintv/bin/jzintv -p /home/pi/RetroPie/BIOS -q /path/to/rom

[petrockblog]

you can always rollback the firmware/kernel with rpi-update

[petrockblog]

No need to post the full config here – makes threads hard to follow – please use pastebin or similar.

if you are talking about the default mame4all, or advmame – neither are retroarch emulators so they dont use this config. I think mame4all-pi might need a patch to “fit to screen”.

[petrockblog]

after launching a rom (which doesn’t work) – please check the contents of /tmp/runcommand.log and it might contain some information as to why it didn’t launch.

you can do this by connecting to the pi via ssh (eg using putty.exe on windows), and then doing

cat /tmp/runcommand.log

once you have logged in.

[petrockblog]

It is unlikely to work for anything but terminal apps.

[petrockblog]

yeh – different rotation, but the code would be adjusted in the same manner – however unless it ever becomes part of upstream ES i doubt we will ever add it as an option.

[petrockblog]

I should think you can you pair the second controller in the same way as the first controller. I don’t have two controllers so I cannot check/test.

[petrockblog]

if you configured retropie 3.0 via ES it will have set up the escape button to be “select + start” – which would be whatever keys you mapped it to.

To change hotkey behaviour from this – use there is a option in retropie-setup / supplementary to change hotkey behaviour – Configure input devices for RetroArch

[petrockblog]

I don’t think it will work without a controlling terminal as /dev/tty wont exist. I don’t really have time to dig further – runcommand requires that a controlling terminal exists. It’s not going to work from cron – if kodi is launched from terminal then it should be possible to get it to work – but I wouldn’t bother with the cron launching. if you are launching kodi that way, that will not work either

we launch emulation station from /etc/profile.d/

[petrockblog]

is what a true statement ? not sure what you are saying changes kernel and bootloader. retropie is based on raspbian and uses the raspbian firmware/kernel.

You have not detailed what doesn’t work – you don’t get any display output or it breaks at some point or ? I need details to help.

[petrockblog]

here are the values

ASPECT_RATIO_4_3 = 0,
ASPECT_RATIO_16_9,
ASPECT_RATIO_16_10,
ASPECT_RATIO_16_15,
ASPECT_RATIO_1_1,
ASPECT_RATIO_2_1,
ASPECT_RATIO_3_2,
ASPECT_RATIO_3_4,
ASPECT_RATIO_4_1,
ASPECT_RATIO_4_4,
ASPECT_RATIO_5_4,
ASPECT_RATIO_6_5,
ASPECT_RATIO_7_9,
ASPECT_RATIO_8_3,
ASPECT_RATIO_8_7,
ASPECT_RATIO_19_12,
ASPECT_RATIO_19_14,
ASPECT_RATIO_30_17,
ASPECT_RATIO_32_9,
ASPECT_RATIO_CONFIG,
ASPECT_RATIO_SQUARE,
ASPECT_RATIO_CORE,
ASPECT_RATIO_CUSTOM,

16:9 is aspect_ratio_index = 1

[Author]

Posts