Forum Replies Created
-
AuthorPosts
-
petrockblogKeymaster
probably because the folder below it are not writeable.
if using fat32 – you should make sure it is writeable to the user you will be using. this can be done with mount options.
if mounting via fstab
http://serverfault.com/questions/43634/how-to-mount-external-vfat-drive-as-userif using usbmount
http://unix.stackexchange.com/a/39941petrockblogKeymastermake sure the linapple folder is writable by the user you are running it under- should work fine out of the box on the image though – what version etc are you running ?
chown -R pi:pi /opt/retropie/emulators/linapple
petrockblogKeymasterthanks for the feedback.
petrockblogKeymasterYou will need to re-configure inputs for EmulationStation. But EmulationStation will recognize the ControlBlock inputs right away if everything is running properly.
petrockblogKeymasterthanks.
I have hopefully fixed up the mame issue now, and have improved the launch menu.
update with
git pull sudo xmlstarlet ed -L -P -d "/systemList/system[name='mame4all']" /etc/emulationstation/es_systems.cfg rm /opt/retropie/configs/mame-mame4all/emulators.cfg sudo ./retropie_packages.sh mame4all configure sudo ./retropie_packages.sh lr-imame4all configure sudo ./retropie_packages.sh runcommand install
note the rom location for mame4all/lr-imame4all is now ~/RetroPie/roms/mame-mame4all
petrockblogKeymasterthanks
1. should be fixed now – please update with
git pull sudo ./retropie_packages.sh lr-mednafen-pce-fast configure
2.
I like the ideas – Will make it clearer there is a specific rom/emulator override by hiding the remove. I’ll look into displaying the video mode.
in regards to what video mode to choose, this is something that depends on your system / monitor and the emulator. in many cases there is no need to change it at all. Not sure right now what useful info could be added – but maybe later something can be done via the wiki.
petrockblogKeymasterthey all have the same amount of ram etc?
petrockblogKeymasterthe makefile overrides our CFLAGS, I have committed a fix to the dev branch to patch it. This is unrelated to any new functionality with the new branch.
petrockblogKeymasterI am just guessing that if you had some overclocking enabled in /etc/config.txt that could be the cause as not all pi can overclock the same. if not then I’m out of ideas, especially if using the same psu etc.
petrockblogKeymaster[quote=91027]
Only issue with doing that is it takes ages to complie the RPi2 image and if you want to do a fresh install at any point they you’d have to compile all over again. I’ll wait until there is a RPi2 image before testing i think
[/quote]It doesn’t take ages to do a binary install. Once that is done you have the equivalent of a rpi2 image. There won’t be a rpi2 image for testing.
You don’t actually need rpi2 optimised binaries to help me find any issues before the code gets merged – which is the point of this thread.
petrockblogKeymasteroverclocking settings that one pi doesn’t like ?
petrockblogKeymasterI have fixed pocketsnes – to update – cd to RetroPie-Setup and do
git pull sudo ./retropie_packages.sh lr-pocketsnes configure
petrockblogKeymasterregarding rpi2 optimised image – as I said in my post – just do a full binary install on it and you will get rpi2 optimised binaries – the equivalent of an rpi2 image then.
03/11/2015 at 06:39 in reply to: [Solved] SNESDev issues with reset/shutdown button in Retropie 2.6 #90970petrockblogKeymasterGlad you figured it out and thanks for sharing it here!
SNESDev simulates the press of the ESC key when pressing the button three times in a row. The hotkey behavior of RetroArch must have changed between RetroPie 2.3 and 2.6.
petrockblogKeymastergreat feedback – thanks! I’m really happy that most stuff has worked – and that you like the functionality.
re ppocketsnes – Looks like I may have a bad path in there or something else – will test/get back to you about that.
regarding your other points – one of the problems I have in controller testing, is I never have the controllers – but this is not specific to this build or ? the core system is the same, mostly just reworked launch scripts etc.
I really would like to make controller configuration better. Perhaps it’s worth seeing if we could come up with a viable way of people loaning controllers to me or other devs for testing ?
we could possibly do a symlink between genesis/megadrive, so either folder would suffice ?
petrockblogKeymasteryou can grab the image from here
https://drive.google.com/open?id=0B_knGioK16E6bXlQMC0wTEZ6YlU&authuser=0
note it is a rpi1 optimised image – will work on the rpi2. You can do a full binary install on it on a rpi2 to get rpi2 optimised binaries.
the installed RetroPie-Setup is tracking my branch
lr_module_and_emulator_rework
so once that branch is gone, if you want to continue using it, you will need to switch back to master (git checkout master)
updating it currently will get any new fixes I apply to my branch
new configfiles for those that like digging around:
/opt/retropie/configs/SYSTEM/emulators.cfg – contains the list of choices for emulators – only some systems have this when they have multiple emulators
~/RetroPie-Setup/supplementary/platforms.cfg – has a list of names and file extensions for platforms. if you wanted to add a file extension you can copy this to /opt/retropie/configs/all and add new ones (you will need to re-run the configure stage for the emulator in question with “retropie_packages.sh id configure” or via the gui menu 5 to reinstall / configure)
to switch emulator for a system or specific rom, you need to access the menu after launching a rom (when the screen is black). by pressing “x” or “m”.
petrockblogKeymasterI have updated emulationstation binaries. The simple theme was also updated yesterday by petrockblock, so if you do
sudo ./retropie_packages.sh emulationstation install_bin sudo ./retropie_packages.sh esthemesimple
it will update both emulationstation and the theme.
petrockblogKeymastergreat – thanks. I shall post a link when I’ve done a little more testing myself. Still fixing some bits here and there.
03/09/2015 at 20:59 in reply to: [Solved] SNESDev issues with reset/shutdown button in Retropie 2.6 #90795petrockblogKeymasterHi Jara,
did you make any progress on this? There has been an update to the newest version of the BCM2835 library to support the Raspberry Pi 2 …
petrockblogKeymasterDid you make any progress?
petrockblogKeymasterThe ControlBlock service installs two gamepads which use the CB as input. Any other gamepad that is, e.g., connected via USB is detected as additional gamepad in the operating system and they do not interfere with each other.
petrockblogKeymasterInteresting. I have tested the CB with Pi2-overlocking settings and I did not observe this behavior. Maybe this comes from different characteristics of power supplies and USB cables …
petrockblogKeymasterThe MOSFET on the ControlBlock is specified for up to 3.7 W. To get the switched 5 V you could use a 2×6 pins connector with long pins. Or you might just solder the fan to directly to the 5 V out of the ControlBlock.
petrockblogKeymasterThe ControlBlock provides both functionalities: a power switch interface for your rocker-switch as well as terminal blocks for arcade controllers. After the setup the RPi listens to the ControlBlock and gets the commands to shut-down safely.
petrockblogKeymasterThanks. Your contributions are appreciated. Writing documentation is a chore – so always happy for someone else to do it! :)
petrockblogKeymasterit does come with the aros kickstart substitute though which works for many games.
petrockblogKeymasterthe images are basically the same. there will be the difference of a few emulator,, but in operation they should be identical, so they can both probably share the same documentation, with just a few extra pages for any pi2 specific emulators.
03/04/2015 at 18:00 in reply to: Controller-only operation of Retropie: Realistic expectation? #90144petrockblogKeymaster[quote=90129]…
and for configuring controllers for (most) of the emulators use this guide (from point 8 forward, point 10 describes how to add a hotkey to enable quiting the emulator/saving/loading)
https://www.petrockblock.com/forums/topic/updated-for-2-3-step-by-step-guide/
…[/quote]
If that guide is useful, it would be great if some one from the community could put the information into the wiki at https://github.com/retropie/RetroPie-Setup/wiki. It might be easier to find there.
petrockblogKeymasterGood videos btw – I’m a channel subscriber! ;-)
petrockblogKeymaster[quote=90100]Ok not to be rude but let’s act like I know what an emulator is I am using .smc for the snes and .z64 .v64 for n64.
If you read the entire post I was saying the raspberry pi said there is no file/directory also the editor was a black file
[/quote]I don’t think anyone suggested you didn’t know what an emulator was – they were giving you information on supported file extensions, and then information on the correct location of the interfaces file which you seemed to have not picked up on. I recommend you read through the advice given carefully.
Regarding the black screen – you edited the wrong file/path. You probably made a typo. You said you were editing “/ect/network/interface” – there is no file of that name. Network settings are in “/etc/network/interfaces”
You can configure wireless easily as with the post above.
petrockblogKeymasterFeed it back to the emulationstation project maybe (there might be a ticket open already for it)
petrockblogKeymasterthis is now fixed (to use ip route get), Should be more reliable, – some other tweaks were made too.
petrockblogKeymasterI have opened a ticket here https://github.com/retropie/RetroPie-Setup/issues/711
petrockblogKeymasterthe script is installed at the end of ~/.bashrc, but the source script is part of retropie-setup, which needs fixing
petrockblogKeymasterThe rules have not changed – I have removed the link – OP: please do not post links to copyrighted firmware/roms
FORUM RULES (ALSO ON POSTING IN REGARDS TO ROMS/GAME IMAGES)
-
AuthorPosts