Forum Replies Created
-
AuthorPosts
-
herbfargusMember
Well there are technically two platforms for megadrive: megadrive and genesis and depending on which platform is coded in es_systems.cfg it will pick one or the other see this post:
There is also a known issue with mame games such as pac-man dig-dug etc. Something doesn’t play nice with the symbols or something like that:
https://github.com/Aloshi/EmulationStation/issues/211On the other hand there are alternative scrapers that may work better:
It is also possible some games aren’t on the gamesdb.net website and if that is the case you can set up an account and add them yourself.
herbfargusMemberAlways important to make backups. I usually just start over with a fresh image, or I’ll make a backup of my SD card with win32diskimager and that saves me a lot of the trouble of transferring ROMs and configuring things. You could also just try doing a full binary install if you don’t want to reimage your SD card.
herbfargusMemberHave you looked at this video for hotkeys?
herbfargusMemberIt probably wouldn’t hurt to try another emulator and see if that changes anything. That way it will narrow down if it is really an emulator issue or a controller issue.
04/24/2015 at 16:37 in reply to: all the controller configurations options in RetroPie/EmulationStation #96061herbfargusMemberYou are correct until the third part- the third option is an experimental module petrockblog is working on called inputstation- eventually in theory it should replace the beginning GUI you see when you boot into emulation station the first time. It will not only configure emulation station controls but it will also configure retroarch controls at the same time and will hopefully vastly improve the confusion of controller configuration. See this page near the bottom:
https://github.com/retropie/RetroPie-Setup/wiki/RetroArch-Configuration
herbfargusMemberIts the same size of processor- the ones I used on my B+ I also used on my rpi2. Granted you’ll need to purchase heat sinks specific to the RPI but they are really cheap and you can find them anywhere online.
herbfargusMemberWhich version of retropie are you using? You’ll need to run the controller that doesn’t work through retroarch-joyconfig (if youre using retropie 3.0 it is an option in the retropie menu) and it will create an autoconfig file that should work with retroarch emulators. There will be some separate configurations that might need to be done manually for some emulators but retroarch covers for most of them.
See this page:
https://github.com/retropie/RetroPie-Setup/wiki/RetroArch-ConfigurationAnd this video:
herbfargusMemberI use winscp. But you can also mess around with samba shares as that’s how it is linked to your ROMs folder through windows. I think this is the config folder but I could be wrong
/etc/samba/smb.conf
herbfargusMemberhttps://github.com/retropie/RetroPie-Setup/issues/807
Its been posted as an issue on emulation station as well. As it stands the gamelist.XML only writes on a clean shutdown. I don’t know what command you would use in your script to exit emulation station first but it sounds like a simple enough idea
herbfargusMemberYou can type lsusb and it will give you a hexadecimal code for the product Id and vendor Id http://www.linuxnix.com/2013/05/find-usb-device-details-in-linuxunix-using-lsusb-command.html
Retroarch creates a configuration file based off of the lsusb identification. Some people have added their configuration files to the retroarch source code here:
https://github.com/libretro/retroarch-joypad-autoconfig/tree/master/udevWhen you run retroarch joyconfig it will create a gamepad.cfg file in
opt/retropie/emulators/retroarch/configs/yourgamepad.cfg
and as you’ll see all the aforementioned configs are there plus your newly created gamepad.cfg file. I’m sure there is a setting somewhere related to autoenable that remembers your gamepad.cfg, otherwise you can override those associations by manually editing the retroarch.cfg files for each or all emulators in/opt/retropie/configs
I don’t know everything but hopefully that will give you an idea.herbfargusMemberRule of thumb- don’t use zip files unless its mame, FBA, or neogeo. I always extract my ROMs first and haven’t had any problems. See each emulator page for accepted file types on the wiki:
herbfargusMemberIf you update the setup script- you can see if anything has been added from the setup script menu. You can also check the source code of each linked emulator here for changes (as most links are to the source code in github or source forge):
https://github.com/retropie/RetroPie-Setup/wiki
I keep the wiki up to date- but unless there are any real glaring bugs a full binary install or binary update should get you what you need.
herbfargusMemberI always unzip my files on my computer (as some emulators dont like zipped files) and transfer the unzipped contents over (.smc, .gg, etc.) The only ROMs I don’t unzip are arcade based ROMs like mame, FBA, and neogeo. See each emulator page for which file types are accepted for each emulator:
https://github.com/retropie/RetroPie-Setup/wiki
Likelihood is you have both the zipped files and contents of the zipped files in the ROMs folder so you see both in emulationstation. You really only need the contents. Once you save games it will create a .SRm save state file or something like that but the save state files won’t show up in emulationstation
herbfargusMemberScraping is pulling metadata from a database of sorts for your games- so they can pull boxart, descriptions, publishers, dates etc. Its mostly just an aesthetic thing to make your files and games look neat and organised. There are two main scrapers that are used- the built in es-scraper which is part of emulationstation:
And sselphs command line scraper which many prefer as it is much faster than the built in emulation station scraper.:
But its really up to you. Some people just do without. In order to scrape games you need an active internet connection as the data comes from thegamesdb.net.
herbfargusMemberIn the mean time using tags for posts specific to emulators can help organise results in the tag cloud/ search results.
herbfargusMemberLuckily I can :D I’ve deleted it. I’m going to report this as a bug on github since you’re not the only one who has had this issue.
herbfargusMemberI know this sounds like an odd solution but when in emulationstation in the quit menu select quit emulationstation- not shutdown or restart. Then it should write the changes. Then go back into emulationstation by typing emulationstation in the terminal or reboot and see if the changes stick.
Test it with only a few first just to make sure it works first so you aren’t redoing your work.
herbfargusMemberI highly recommend a raspberry pi 2, I’ve been using mine for a while and it works great. It probably would be easiest just to start over rather than updating as it will minimise the potential issues- n64 is still hit and miss depending on the game and how much you want to invest in messing with configurations, but I haven’t had any issues with any of the older consoles.
herbfargusMember1.51 is too new to work on the emulators in retropie but you can rebuild an older romset from 1.51 so that it will work. The program you will use is called clrmamepro. See this page on how to do that:
https://github.com/retropie/RetroPie-Setup/wiki/Managing-ROMs
Near the bottom shows which romsets work with each emulator and has links to the database files you’ll need to rebuild the sets: courtesy of floob. There is a video tutorial linked on that page as well for convenience.
herbfargusMemberhttps://github.com/retropie/RetroPie-Setup/issues/654#issuecomment-89574816
Seems youre not the only one with this issue. They recently just changed the code for the ps3 controller- I don’t own one so I’m not entirely sure about how it all works but it might be worth updating the script and reinstalling the ps3 sixad controller module
herbfargusMemberI use genesis plus gx. Dgen is probably the last emulator I’d use. Libretro picodrive works as well. It just depends on the game. Just test them out and see which performs better.
https://github.com/retropie/RetroPie-Setup/wiki/Genesis-Megadrive
herbfargusMembersudo rm /opt/retropie/emulators/retroarch/configs/xboxgamepad.cfg
Or you can delete it in winscp.
herbfargusMemberIf unzipping them didn’t work it could also be a poor source of ROMs or you could verify your es_systems.cfg file was set up properly by typing sudo nano /etc/emulationstation/es_systems.cfg each system should match the file types listed on the wiki pages.
herbfargusMemberSometimes zipped files don’t work even if they say they do. When in doubt unzip all ROMs except mame, FBA, and neogeo. See the wiki for the most common file types that work for each system:
https://github.com/retropie/RetroPie-Setup/wiki
For GBA see this post:
https://github.com/retropie/RetroPie-Setup/wiki/Game-Boy-Advance
You’ll need the gba_bios.bin file in the /home/pi/RetroPie/BIOS folder.
It will also be helpful to specify which pi you have and which version of retropie you installed.
herbfargusMemberIve honestly never used the l + r buttons in gameplay for SNES but I’m pretty sure they are functioning. Its possible for your controller they may be buttons 6 and 7 rather than 4 and 5 but idk. This is my official gamepad configuration file that was created by retroarch (I didn’t know what I was doing when I created the first file above):
https://github.com/libretro/retroarch-joypad-autoconfig/blob/master/udev/USBgamepad.cfg
herbfargusMemberTheres the autoconfig file in
opt/retropie/emulators/retroarch/configs/yourgamepad.cfg
that is created when you do the retroarch joyconfig. Then there is the retroarch.cfg inopt/retropie/configs/all
that is set up for all retroarch emulators and then there is also a retroarch.cfg file for each individual retroarch based emulator in each respective folder inopt/retropie/configs/<systemname>
See this wiki page on controller configurationshttps://github.com/retropie/RetroPie-Setup/wiki/RetroArch-Configuration
herbfargusMemberIf any of the above steps didn’t work for anyone, this is what I did to get my dpad to work:
I went into
/opt/retropie/configs/all/retroarch.cfg
and changed
# Axis for RetroArch D-Pad. # Needs to be either '+' or '-' in the first character signaling either positive or negative direction of the axis, then the axis number. # Do note that every other input option has the corresponding _btn and _axis binds as well; they are omitted here for clarity. # input_player1_left_axis = # input_player1_right_axis = # input_player1_up_axis = # input_player1_down_axis =
to
# Axis for RetroArch D-Pad. # Needs to be either '+' or '-' in the first character signaling either positive or negative direction of the axis, then the axis number. # Do note that every other input option has the corresponding _btn and _axis binds as well; they are omitted here for clarity. input_player1_left_axis = -0 input_player1_right_axis = +0 input_player1_up_axis = -1 input_player1_down_axis = +1
herbfargusMemberI had the same issue with my controller- exact same as yours. For some reason the autoconfig with retroarch had issues and I had to manually set them in the retroarch.cfg file. I put in my custom controls and changed autoenable from true to false (you’ll know if you did it right by the yellow joypad text not showing up when you start a game)
herbfargusMemberherbfargusMembercd /opt
I usually just use winscp
herbfargusMemberDelete the # before disableoverscan=1 in boot/config.txt, save your edits and reboot and see if that makes any difference.
herbfargusMemberI would have to agree with floob- 2 separate sections for new users and controllers would help thin the redundancy. Once you’ve sorted out input station I think that will really help with the controller issues. I think one other issue that’s is pretty common is mame and getting the right romsets- this thread may be useful as a stickie for mame:
herbfargusMemberI can understand the issue with redundancy which is why I sorted out the wiki as best I could. I created it as I tested each emulator so it should cover for most issues for the basic setup and controls of each emulator.
https://github.com/retropie/RetroPie-Setup/wiki/Atari-2600
Plus people are just inherently impatient so its easier to throw out a post in frustration than it is to try and find a solution to a problem that was likely already solved in a previous post. But I do agree, the forum could use some better organisation.
-
AuthorPosts