Forum Replies Created
-
AuthorPosts
-
petrockblogKeymasterWell, visually at least. You can check the end of /var/log/syslog to see when it completes.
petrockblogKeymasterNo way of telling unless you have a light on your USB stick or something.
petrockblogKeymasteruse ppsspp – it is faster and more compatible than the libretro core.
petrockblogKeymasteryou can adjust /opt/retropie/supplementary/runcommand.sh which is used to launch the emulators and handle some configuration to trigger another script before launching (which would control your relay via gpio
petrockblogKeymasteryou can get out of the loop by pressing a button on a keyboard btw – to drop to a terminal.
petrockblogKeymastercheck the permissions of the folder/file in question via ssh
ls -lathe usm rom service script chowns the files correctly, so I can only think it is due to the directories/files having no read access despite being owned by the user (unless it was caused by something else).
files should be
chmod 644and the romdirs
chmod 755petrockblogKeymasterThere are some options you can try in regards to io – check in PPSSPP settings. Did you try adjusting any of them ?
petrockblogKeymasterif you exit ES with f4 I think it doesn’t save any gameslists. I might look at changing the exit so you have exit + save and exit without saving options or so
11/26/2015 at 18:10 in reply to: how can you get video splash screen to play all the way to when ES is loaded #110755petrockblogKeymastermaybe as it starts before ALSA is properly initialised or something.
11/26/2015 at 17:45 in reply to: how can you get video splash screen to play all the way to when ES is loaded #110750petrockblogKeymasterDidn’t realise omxplayer now had a layer option. good spot. I will consider adding this so it stays in front.
11/26/2015 at 16:16 in reply to: how can you get video splash screen to play all the way to when ES is loaded #110742petrockblogKeymasteror a modification of omxplayer to put it on a higher layer – see https://www.raspberrypi.org/forums/viewtopic.php?f=67&t=25866 / https://github.com/xbmc/xbmc-rbp/blob/master/xbmc/cores/omxplayer/OMXVideo.cpp#L546
11/26/2015 at 16:11 in reply to: how can you get video splash screen to play all the way to when ES is loaded #110740petrockblogKeymasteras I said above, you can’t have ES start behind – well unless you disabled the loading screen on ES and have it init everything and then open the GUI. requires modifications of ES code.
11/26/2015 at 15:24 in reply to: how can you get video splash screen to play all the way to when ES is loaded #110735petrockblogKeymasterNote that ES will appear over the video though (afair) and cut it off short but it will be seamless – it will load in background, but the ES “starting up” screen will not.
11/26/2015 at 15:23 in reply to: how can you get video splash screen to play all the way to when ES is loaded #110734petrockblogKeymasterRead the wiki :) https://github.com/RetroPie/RetroPie-Setup/wiki/splashscreen
petrockblogKeymasterread the documentation:
https://github.com/RetroPie/RetroPie-Setup/wiki/How-to-get-ROMs-on-the-SD-card
Starting with RetroPie 3.0 you first need to create a folder called retropie on your USB stick and then follow the above steps.
petrockblogKeymasteraha. so it’s all related to the trigger ? changing the driver had no effect at all (so it does work left as udev in both configs ?)
Could be how the kernel is treating the values – but often it’s also related to buggy firmware in controllers etc. you could try downgrading the kernel with rpi-update to see if that makes a difference.
petrockblogKeymasterplease can you clarify – there were 3 scenarios, one being the original set up which didn’t work before, so not sure which ones you are referring to :)
petrockblogKeymasterJust those examples above – I would like to know how it affects your set up as described in a / b and c scenarios.
so for a)
edit configs/all/retroarch.cfg – change: input_joypad_driver = sdl2
edit configs/all/retroarch-joypads/yourjoypad.cfg – change: input_driver = udevthen test 1 / 2 joypads connected and hotplugging them.
and then do the same for b etc. It will help me to decide what defaults to choose for the next release to work around some issues (including yours).
petrockblogKeymasterthanks.
Can’t advise on calibration I’m afraid.
I am after a little more detail if you can please with the settings:
EG for each of these
a) configs/all/retroarch.cfg - input_joypad_driver = sdl2 configs/all/retroarch-joypads/yourjoypad.cfg - input_driver = udev b) configs/all/retroarch.cfg - input_joypad_driver = udev configs/all/retroarch-joypads/yourjoypad.cfg - input_driver = sdl2 c) configs/all/retroarch.cfg - input_joypad_driver = sdl2 configs/all/retroarch-joypads/yourjoypad.cfg - input_driver = sdl2also if you have any other controllers I would be interested if this affects them with hotplugging etc.
petrockblogKeymasterthe driver name should be sdl2 not sdl for our retroarch I think – not sure if it allows sdl too or just defaults to another setting. Need to check the sourcecode to find out.
Please can you try my suggestions above as it would be useful for retropie development.
petrockblogKeymaster(and using sdl2 rather than sdl in the joypad configuration file).
petrockblogKeymasterI would be interested in the results of config changes with changing just “input_joypad_driver = sdl2” in the main configs/all/retroarch.cfg also
petrockblogKeymasterThere are some other issues solved by switching the driver too for other gamepads which seem to map differently when using udev – see https://github.com/RetroPie/RetroPie-Setup/issues/1077
We may be switching to sdl2 for the input – but it requires some more testing.
petrockblogKeymasterread through https://www.petrockblock.com/forums/topic/emulationstation-screen-dont-fit-after-update/ and then try
sudo rpi-updatepetrockblogKeymasterCheers.
The only other thing I can think of is something is wrong with the includes and
sudo apt-get remove --purge libraspberrypi-dev; sudo apt-get install libraspberrypi-devmight help.petrockblogKeymasterI downloaded the latest berryboot for the rpi2 (berryboot-20150916-pi2-only.zip), and tested with the 3.2.1 RetroPie berryboot image (after updating the RetroPie-Setup script), and it all built fine. Are you using the latest berryboot (in case it is related to the way berryboot overlays the filesystem over its base structure with kernel etc).
petrockblogKeymasterpetrockblogKeymasterWhat is the output of
git log -1from within the RetroPie-Setup folder (just to make sure we are def up to date with the script).petrockblogKeymasterI have seen the build problems you are having before – I think due to an older VC sdk – but could be caused by other conflicting packages/includes hence I wanted to see dpkg.log which will tell me what has been installed etc
petrockblogKeymasterOr for example have you used rpi-update to upgrade/downgrade kernel / firmware / sdk
petrockblogKeymasterdid you update retropie-setup first ? is your system up to date too ? (sudo apt-get update; sudo apt-get upgrade) – have you installed any other packages recently ? (maybe you can paste via pastebin or similar your /var/log/dpkg.log)
petrockblogKeymasterps2 to usb adapter should work though.
petrockblogKeymasteryep.
petrockblogKeymasterSpend less time watching your machine boot, and play the games instead :)
You could add a keypress check in the delay loop and exit it a key pressed perhaps, but I’m not at all interested in spending time on stuff like this I’m afraid.
petrockblogKeymastersounds ok. Guess the overclock is not stable. Reduce it as mentioned and try then.
-
AuthorPosts
