[petrockblog]

please provide the logfile from “logs”.

[petrockblog]

Does it help if you recompile and reinstall SNESDev?

[petrockblog]

Sure, just post a pull request!

[petrockblog]

The wiki is supposed to be filled and updated mostly by the community. If you see that a lot of paths are wrong or outdated, you are welcome to update the site accordingly. Already a few improvements are worth a lot!

Do not get me wrong – we would love to keep everything nice and clean. But with its size and the ongoing development the wiki heavily depends on the contributions of the community.

[petrockblog]

That’s not true – there are plenty of people offering help, and putting in lots of time giving tutorials and tips.

The wiki relies a lot on user contributions. I do edits where I can and when I have time, but it’s not something the few core devs can do on their own.

[petrockblog]

you can use the shipped with aros rom for many games, or the ~/RetroPie/BIOS folder for kickstart 1.3 to 3.1

[petrockblog]

i found the problem in the code and have now submitted a fix to retroarch for this. I will rebuild retroarch binaries once it has been included.

[petrockblog]

theruncommand script adds an addition config – and it seems retroarch breaks at more than 2 configs added to appendconfig – I have opened a ticket here – https://github.com/libretro/RetroArch/issues/1439

workarounds:

don’t use runcommand so the additional config is not added.

/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/neslibretro/fceumm_libretro.so --config /opt/retropie/configs/all/retroarch.cfg --appendconfig /opt/retropie/configs/nes/retroarch.cfg,/opt/retropie/configs/all/retroarchp2.cfg %ROM%"

alternatively, you can just add /opt/retropie/configs/nes/retroarch.cfg and “include” your addition config from there (putting #include path/to/additional/config in there)

[petrockblog]

you can try adjusting this setting in /boot/config.txt

config_hdmi_boost	configure the signal strength of the HDMI interface. Default is 0. Try 4 if you have interference issues with hdmi. 7 is the maximum. 

[petrockblog]

What did you hve to do to make RetroPie run on the Odroid? Are you using their Ubuntu distribution?

[petrockblog]

well also me, and i just switched our “module” to work from the last source. I believe it must make an assumption regarding sdl and the mouse grab function. i will look into it, but please open a ticket on github so it doesn’t get lost.

[petrockblog]

don’t know about first part. the emulator has only just been added – it may well need some attention.

regarding second point, no, there is no commandline support currently.

[petrockblog]

The RetroPie GPIO Adapter is compatible with the Raspberry Pi 2.

If you already checked the connection between each pin of the SNES connectors and the corresponding pin on the RetroPie GPIO Adapter, it might be that there is a confused connection. Just a guess, though.

SNESDev installs two gamepad devices in the operating system and gets their states by polling the controllers. If everything is wired up correctly and you press the direction buttons for the first time after boot up, the -32767 will disappear and be replaced by 0 then. This comes from the current implementation of SNESDev.

Does the the button on the GPIO Adapter work?

You could also post a picture of your wiring here.

[petrockblog]

Actually, I am the author of SNESDev.

My experience is that you can poll NES controllers also with 3.3V so that you do not need level-shifters at all ad things get less complex! The RetroPie GPIO Adapter also uses the 3.3 V supply voltage.

[petrockblog]

please provide the actual config line in es_system.cfg please.

The problem may be the way you are adding the config and a conflict with runcommand – which appends its own retroarch config with the video mode refreshrate in.

[petrockblog]

“zless” can read them, or depack with “gzip -d”

[petrockblog]

it’s not saying that – it’s saying the binary was not found which means the build failed. the reason for the failure will be earlier in the log.

[petrockblog]

yes.

you can not install a display manager if you don’t want it to start up on boot.

people that really want a desktop gui, should probably just install retropie-setup over raspbian though – the retropie image is meant to be compact.

[petrockblog]

there is no problem if you want to install lxde.

[petrockblog]

[quote=88480]If you have a PI2 use:
3: sudo __platform=rpi2 ./retropie_setup.sh[/quote]

fyi – __platform is only needed if it can’t auto detect or you want to force it (in say an emulated environment). if running on a pi1/pi2 it will set the platform accordingly.

[petrockblog]

which image did you download from that link ?

[petrockblog]

the mousepointer issue is common on sdl emulators when using fbcon driver (or our dispmanx code) – I’ve had to manually fix up fuse also.

Please use the github site for code issues etc/posting patches/pull requests.

thanks for the fix.

[petrockblog]

we never had an overclock settings for the rpi2 included by default. some older images had a overclock setting for the rpi1 which was removed/fixed (I believe it wasn’t intentional)

[petrockblog]

Yeh I noticed it moved – only seems to have included the fixes we have already so far. I will certainly switch back to that repository if it gets some more attention. Would be nice if they used some more descriptive commit messages – most of the changes seem to have one word like “updated” etc.

mame4all was also moved to sourceforge – would have been better on github imho, just because the sourceforge git interface is way behind that which github has.

[petrockblog]

[quote=88302]The RetroPie image automatically overclocks your Pi2 to 1000MHz.
[/quote]

only if you enable overclocking in raspi-config – it is not overclocked out of the box.

[petrockblog]

it used to download/update all binaries, but this was a problem since some binaries required configuration updates which it didn’t do – this was causing problems.

You can update individual items from menu 5, or use the menu 1 to do a complete binary install which will update the system (backup any custom configs etc first).

We may add it back again in the future, but in a way that doesn’t cause the problems as before.

[petrockblog]

update fuse from menu 5 and it should be sorted (after updating the script itself)

[petrockblog]

gpu_mem_1024 sets the memory split for a pi2

gpu_mem_512 sets it for a B/B+ with 512mb ram

gpu_mem_256 sets it for a 256mb model

we use these instead of gpu_mem= so the default is reasonable for all machines.

[petrockblog]

of course none of this should be needed. ~/.emulationstation can get the wrong permissions if emulationstation is run via sudo though.

[petrockblog]

chmodding to 777 is not correct. That will make everything world read/writable and set the executable flag.

chown -R pi:pi ~/RetroPie/roms/

to make sure all roms are writable by the pi user.

chown -R pi:pi ~/.emulationstation/

to make sure pi user can write the gameslists etc.

[petrockblog]

the image is up to date, so there are unlikely many packages to update to.

there is no desktop/gui by default so only install the desktop and things like raspberrypi-ui-mods if you need it.

[petrockblog]

well, it’s impossible to please everyone – we try to make the most common set up the default. as can be read, not everyone appreciates us switching the screenmode by default, which was done to try and sort out performance issues – many of the shaders do not perform well at high resolution.

default does not mean you can’t change the behaviour. I have spent a lot of time trying to make stuff more easily configurable.

[petrockblog]

gizmo – not possible to use this and keep aspect ratio ? perhaps that could be changed and we could use this by default then.

[petrockblog]

you can use menu option 1 (after updating the script). it could overwrite some configs, so it might be worth making a copy of stuff you have changed.

[petrockblog]

retropie 2.3 is no longer supported – please download the 2.6 image. thanks.

[Author]

Posts