[petrockblog]

[quote=86484]
Also maybe im missing something, me and my newbie ways, cause when i ran the update scripts and binaries from the 2.3 image it added all these duplicate folders and files with different letter casing. it made configuring controllers and find the correct path to things a pain. if the update added new paths and moved things around and made everything lower case was it meant to also remove the old stuff and i missed something?
[/quote]

it doesn’t remove the old stuff – so removing everything in /opt/retropie is advisable if starting with the old 2.3 image. there was a major rewrite after 2.3 of the retropie core and most paths changed.

But just use the 2.4.x image – the beta was only put on it as a precaution – it is stable. Only major bug I know with the last version is the usbromservice which I broke, but if you update the script and re-run that supplementary option it will be fixed.

[petrockblog]

i will sort an updated images when I get a free moment. The updates bootloader packages now includes a kernel7.img as well which is used for raspberry pi 2. Shouldn’t need to do a rpi-update btw as the important update is in the rpi repository.

[petrockblog]

you wont get 6x performance from emulators though btw – that figure is based on multi threaded stuff that can use all the cores.

[petrockblog]

the image wont work, but it should work if installed on top of the new raspbian. I added some basic multi platform support into retropie, which could be used to set different build options to optimise for the raspberry pi 2.

[petrockblog]

glad you got it sorted.

[petrockblog]

I would need to look at a log to see if anything didn’t work – you are probably better off with doing a binary install though – most of the binaries are reasonably up to date currently. if new to linux – using the prebuilt 2.4.2 image might do you even better.

[petrockblog]

No idea as it works here both on composite and hdmi with dispmanx off, but if you wait a bit we will update scummvm with a new version that has native pi display out that should solve your problems.

If it initially worked then maybe something happened to the config – maybe worth going with a fresh image again ?

[petrockblog]

I like the idea of using the pie. However, am not 100% convinced of the mix of pixel art and smooth lines.

Recently, I have ordered some decals. Maybe that might also give some inspirations.

[petrockblog]

try switching the screenmode before emulator launch to 640×480.
you can also enable/disable dispmanx support for the emulator in the supplementary config section of retropie-setup

[petrockblog]

you can update just this emulator by updating your retropie_setup, and then going to option 5 “Install individual emulators from binary or source”, scrolling down to psxlibretro choosing it, and then choosing “binary” (I have updated the binary for it now). You can use this to individually update an emulator at any time (if there is a newer binary available), or build from source to build the very latest version.

[petrockblog]

I meant compatibility not performance. tired brain. I will update the binaries as soon as I get a free moment and we can test the latest version.

[petrockblog]

your ticket was closed as you asked a question on the forum, then opened a ticket, without replying to the forum reply – there are differences between the emulators of course – as the 2.4 one is newer – it’s possible some emulator updates reduced compatibility, but please provide detailed info (such as what specific games etc)

[petrockblog]

use retropie 2.4.2 image – and it has separate rom folders for each emulator – so if you only want to use snes9x put your roms in the snes-snes9xrpi folder.

It also has the ability to switch video output mode on emulator launch.

[petrockblog]

are you trying to launch it from a remote ssh session ?

[petrockblog]

well, we aim to improve the software, but i am running nes fine on 2.4.x

[petrockblog]

I would definitely upgrade to the beta or wait a few days as we will remove the beta tag from the next version – however I know of no major issues with the beta and it’s what I am running myself etc.

[petrockblog]

the wifi can be configured from console – see http://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md we will be introducing a simple configuration item in retropie-setup for this also at some point.

the retropie image has been made smaller to provide an emulation distro without unrelated extra bits. If you require a full desktop, you can use retropie-setup on top of raspbian for example or install a desktop environment later.

[petrockblog]

Have you tried another sdcard – to rule out a fault/error on your current one ? it looks like it almost completes and gets an error – this could be a write error on the card. it may not show up with another image due to differing sizes etc.

[petrockblog]

mame4all is not the same as mame 0.37b5 0- it has additional fixes / compatibility changes etc afaik. It comes with a rom manager dat so you can build a romset for it from other sets I believe

I’m pretty sure 1941 and 1943 work perfectly.

[petrockblog]

Until now there is not really an official logo. However, it would be nice to have one, I think. If someone feels to donate a logo, that would be great.
We must make sure, however, that the logo does not break any copyright or trademark rules, e.g., from the Raspberry Pi (http://www.raspberrypi.org/trademark-rules/).

[petrockblog]

on the latest retropie-setup script there is a menu to install individual packages from binary or source (menu item 5). added so people can quickly create a custom install, or rebuild stuff quickly.

This is also possible from the retro_packages.sh commandline tool (which can do a lot more also)

[petrockblog]

using this method to remove clones.. you could do something like (this doesn’t actually remove anything – just echoes it – remove the echo to remove)

/opt/retropie/emulators/mame4all/mame -listfull -noclones | cut -d" " -f1 >noclones.txt
/opt/retropie/emulators/mame4all/mame -listfull | cut -d" " -f1 >all.txt
grep -v -x -f noclones.txt all.txt >clones.txt
for rom in $(cat clones.txt); do echo rm $rom.zip; done

[petrockblog]

/opt/retropie/emulators/mame4all/mame -listfull -noclones

/opt/retropie/emulators/mame4all/mame -listfull -noclones | cut -d" " -f1

for just rom names.

[petrockblog]

What a comprehensive write up! Sou might also consider to add this article to the RetroPie Wiki at https://github.com/retropie/RetroPie-Setup/wiki.

[petrockblog]

It may be fixed – not sure but you should probably check the emulationstation bugtracker – https://github.com/Aloshi/EmulationStation/issues

[petrockblog]

It probably isn’t upgraded completely. My recommendation would be to start with the 2.4.x image which is a lot newer than 2.3.

[petrockblog]

I’m not familiar with the “famous” issues you are referring to, but if you can describe a specific issue, I can try and help.

Also please start with retropie 2.4.2 – a lot has changed since 2.3

[petrockblog]

I have – although I found compatibility to be somewhat poor. I did find some games that worked though. Hopefully compatibility will improve with updates but Crash_Bandicoot worked for example.

[petrockblog]

we generate a minimal config for vice – once you have loaded it, you can configure other stuff and then save the configuration.

press f12 for the configuration menu inside vice – joystick mapping is configured under “Machine settings -> Joystick Settings”

Documentation for the emulator is here – http://vice-emu.sourceforge.net/vice_toc.html and has lots of information regarding configuration etc.

[petrockblog]

because it wasn’t available as a libretro core until recently and hasn’t yet been included.

[petrockblog]

to change video mode for an emulator. press “x” or “m” before the the emulator loads. it prints a one line instruction to do this at the top of the screen.

you shouldn’t need to use tvservice manually anywhere.

[petrockblog]

no idea then – it looks as though you have the rom in place, and the disk.img so it should work. maybe try another rom?

I have tested it with the files from this page – http://www.redundantrobot.com/sheepshaver-tutorial/

http://www.redundantrobot.com/macemulator/MacStartup.img

and

http://www.redundantrobot.com/macemulator/1mbMacrom.zip

and it works fine. Maybe double check the filenames – that there is no trailing space or something.

[petrockblog]

yep. sorry.

well, that looks fine – so it should find the rom/disk image. you are launching from emulationstation right?

[petrockblog]

Please test with a 2.4 image.

[petrockblog]

You started with a fresh 2.4 install or 2.3 ?

[Author]

Posts