Thanks guys! This worked for me as well.
I don't update regularly, but once I did, I found same issue with my Multitap settings set to "auto", leaving my Castlevania Symphony of the Night quest on hold till I figured it out :)
@Rubencn1234 Put it in the same directory as the roms. If you put it in the BIOS directory, it doesn't seem to find it. I had to put it in the roms directory (with the correct name) in order for it to work.
Which emulator are you using? FBA works fine without "neogeo.zip" in the roms folder. I have it just in the BIOS folder.
@Rubencn1234 Check to make sure you have the right BIOS file. neogeo.zip needs to be ~1.5 MB and CRC-32 should be 20F12195
for mame2003-plus on digital only turn analog off you only turn this on for analog controllers if your using them.
ie snes and joysticks use dpads (digital hat). analog off( this is the default mode)
you should do the following in settings
enable legacy mapping ( this is important when it needed for analog or games using analog controls even on a dpad)
in analog mode : directons are on axis 0 an axis 1 (lstick)
@mitu I had the same issue! I also noticed somehow all the files inside the /opt/retropie/emulators/retroarch directory was missing, so I forced the updated in the core packages configuration menu inside the Retropie Setup screen. (Manage packages -> core -> retroarch -> Update from binary)
Hi, thanks for reply.
The game you are linking to is Fishermans's Bait 1, this game works great on my retropie setup.
But i guess you have a good hint there.
I am sure there is a way to map the buttons for Fisherman's Bait 2 also.
@kenibure said in I cannot use this system correctly.:
Problem number 1:
When I try to reboot the Raspberry, the graphic interface disappear, and then appears a command console. I would have to make "sudo reboot" or "sudo poweroff", but then, the system doesn´t detect my keyboard.
I can confirm this is a common problem - especially when the program encounters a fault and exits to terminal. To properly shut down the computer I have to SSH into it and "reboot" since you can't use the keyboard hooked up to the Pi anymore at that point.
...can't help you with how to fix it I'm sorry to day.
