[petrockblog]

I found an error in the splashscreen script which was introduced the other day which broke splash pictures – sorry I missed this. if you update retropie-setup and then choose to update the splashscreens it should sort it

[petrockblog]

also make sure none of you have removed the “fbi” tool after setting up a splashscreen.

[petrockblog]

Please don’t post large logs directly here – use a site like pastebin etc.

I can’t see an error in that log – if there is an error displayed please post the error. I need some more info to go on as I am unable to reproduce the issue here.

[petrockblog]

then unfortunately everything looks correct. The init.d script is the correct size, the splashscreen.list points to an existing splashscreen, and you have made sure the splashscreen is enabled.

If you could show me the error you said it printed on startup that might help. Otherwise I can only recommend testing with a new image (and backing up your configs first)

the only other thing that affects the splashscreen that I know of is if the system is set to boot into the desktop/graphical environment (if it has been installed), this can cause X to trigger before the splashscreen so you get a black screen.

[petrockblog]

opt/retropie/supplementary/splashscreen/8-bit-dragonberry/8bit-dragonberry.png

or

/opt/retropie/supplementary/splashscreen/8-bit-dragonberry/8bit-dragonberry.png

?

from a terminal please can you paste the output from

ls -l /opt/retropie/supplementary/splashscreen/8-bit-dragonberry/8bit-dragonberry.png
ls -l /etc/init.d/asplashscreen

did you try disabling the splashscreen and re-enabling from the splashscreen options ?

[petrockblog]

I’m not after what you think it is – I’d like you to check please and give me the exact contents of the file. If you have chosen a new splashscreen using the splashscreen configuration it should update the contents of this file.

[petrockblog]

If you have gone into the splashscreen module, it should have installed the new version of the splashscreen script. However if you updated from a beta version (which matches the date you gave), something may not worked right.

what do you have in /etc/splashscreen.list ? (can see it by using the “Manually edit splashscreen” option)

[petrockblog]

Which USB snes adapter ? Impossible to advise without at least some basic information. Maybe it is faulty? Did you test it on another system ?

[petrockblog]

That is the new theme. You can change the theme from retropie-setup – please do read the documentation – https://github.com/RetroPie/RetroPie-Setup/wiki/Themes

[petrockblog]

You didn’t answer my question – Did you reconfigure the splashscreen from the splashscreen settings in retropie-setup ? If you have updated from a version prior to some splashscreen changes you will need to reconfigure it.

menu 3 in retropie-setup – Configure Splashscreen, then choose a splashscreen.

[petrockblog]

Via pastebin.com please next time as requested so formatting is preserved.

so that looks fine – you must have put a full fba romset in the ~/RetroPie/roms/neogeo folder then rather than just the neogeo roms.

Personally I don’t use the neogeo rom folder, and just use the FBA – it’s split as there is a neogeo only emulator that can be optionally used but most stuff is better on lr-fba-next (which can be used for neogeo and the fba rom folders).

[petrockblog]

please post (via pastebin.com or similar) the output of

tvservice -s
cat /boot/config.txt

for retroarch games, have you experimented with the aspect ratio settings in RGUI ?

[petrockblog]

which version did you update from ? please post your /etc/emulationstation/es_system.cfg (via pastebin.com)

[petrockblog]

from which version ?

Did you reconfigure the splashscreen from the splashscreen settings in retropie-setup ?

[petrockblog]

1. it resets the ES configuration. retropie configs don’t get wiped – this will be sorted.

2. probably because you edited /etc/emulationstation/es_systems.cfg – if you want to customise it you should copy it to ~/.emulationstation and your custom one will never be touched (you may have to manually update it from the /etc/emulationstation file though though as needed)

3. shader configs are stored in retroarch.cfg files and they are not overwritten – unless you were on an old retropie-setup and you forgot to update the retropie-setup script before doing a full binary install.

Kodi is not removed nor are lirc settings.

[petrockblog]

Please be more specific regarding what tweaks were overwritten. When updating:

no retroarch.cfg are touched
no retroarch joypads are removed – but ES controller config is reset – I need to fix this.

If you can tell me a specific config that was overwritten I can check/advise.
Also which version did you update from ?

[petrockblog]

Did you check the wiki? – probably your rom set

https://github.com/RetroPie/RetroPie-Setup/wiki/Nintendo-Entertainment-System

Make sure your roms have headers. Roms without headers will not work.

you will have to do your own research to get the correct romset though.

[petrockblog]

yeh also in runcommand

[petrockblog]

another thing that possibly could affect latency (or not) is the cpu governor on retropie-setup – it’s set to “ondemand” by default, but you can switch it to “performance” which might help. this can be changed via retropie-setup -> setup / configuration -> configure runcommand launch script

[petrockblog]

threaded video makes a big difference for performance for some stuff – at least with the gl driver (and for people with rpi1). We changed the default to “false” for a retropie release and there were lots of complaints regarding performance. It is easily switchable via our “config editor” from the retropie menu.

from retroarch.cfg template:

Use threaded video driver. Using this might improve performance at possible cost of latency and more video stuttering.

I am adding the dispmanx driver to our retroarch build (you will need to build from source of course in retropie-setup). I will add an option for switching config in the config editor.

[petrockblog]

https://github.com/libretro/RetroArch/issues/2503

[petrockblog]

Yep RPI2 – I found the cause – Please see my posts above. I’m constructing a report for upstream.

[petrockblog]

ok – it crashes with video_threaded = true so I will report this upstream. BTW when you were comparing the drivers, did you test the GL driver with video_threaded=false and the same options for dispmanx. I would not have though there would be major differences in performance.

[petrockblog]

ok – looks like it’s something config related triggering it – don’t need a config now as I have a working one and will diff/compare. Cheers.

[petrockblog]

please can you post me your retroarch.cfg and the console output from running retroarch –verbose (with a nes core & rom) ? The latest retroarch is segfaulting for me with the dispmanx driver enabled in retroarch.cfg (older codebase works). Wondering what revision you are running etc.

I am currently git bisecting it to post a bug report upstream.

[petrockblog]

2.3 is not supported. Too much has changed since then to really advise apart from saying to backup your image / configs and start from a fresh image.

[petrockblog]

Take the card out and manually edit the config.txt on the first partition on another machine. The overlocking settings can be disabled there.

I doubt you will get usable n64 emulation on a rpi1.

[petrockblog]

or copy platforms.cfg to configs/all and manage it yourself from there (that will be used over the RetroPie-Setup one by the script if it exists. (and then reset the RetroPie-Setup one)

[petrockblog]

there are upcoming improvements to the way everything is managed, but the wiki contains plenty of documention on how to install. New / inexperienced users should not be selectively installing stuff manually, but using the image.

[petrockblog]

Lines that start with # are commented out. Remove the # to activate the config parameter – make sure you back it up first.

[petrockblog]

Do not post links to roms – https://www.petrockblock.com/forums/topic/forum-rules-on-posting-in-regards-to-romsgame-images/?view=all

[petrockblog]

I think it is that – so you will need to zoom the video – but it’s an issue that could be reported back to omxplayer – perhaps to get it to use the same layer as the –layer parameter (or one less or something)

[petrockblog]

When i tested it before it def made the background black – must be due to the layer change, in that ES is over the top of the black background, but under the video – maybe the black background is on a lower layer that isn’t configurable.

[petrockblog]

you shouldn’t use rpi-update unless there is a specific reason to (test a new release or due to an issue that you know has been fixed). New kernels and firmware are packaged up for Raspbian when they are ready.

update retropie like this – https://github.com/RetroPie/RetroPie-Setup/wiki/Updating-RetroPie

[petrockblog]

RetroArch as you have built it will not use SDL 1 btw so you don’t need to install SDL first.

[Author]

Posts