@lex3001 Please excuse the question, but are you really sure about the ghost inputs only happening in the Arcade menu? I ask because It sounds rather strange. Did you wait long enough in all of the menus to rule out mere coincidence of it happening only in the Arcade menu?

You can test a controller for ghost inputs out of Emulation Station by pressing F4 (you'll land in Retropie's command console) and entering this command:

jstest --event /dev/input/js0

Any inputs coming from the device will be listed while the command is running. You may have to change js0 to the device name of your controller, e.g. js1, js2 etc. You can end the test by pressing ctrl+c and return to Emulation Station with the command exit.

As for solutions for ghost inputs from bluetooth controllers, I fixed those that came from my Qumox Wii U Pro controllers by using a Mayflash Wii U Pro wireless adapter instead of the Raspberry Pi's own bluetooth to connect them. That got rid of the ghost inputs for good.

Thanks for sharing your solution. As for readability, it helps to put commands etc. in single grave accents (`) to highlight them and use a fixed-width font like this.

See the Markdown syntax for more formatting options. It's also linked at the upper right corner of the input area of a new post (the small grey "compose").

@webodan Please provide more details about your system - https://retropie.org.uk/forum/topic/3/read-this-first.

You are right! It works.
Now I have to duplicate and rename the scraped favorite roms.

Thanks for support!

Hi. Ooooh, OK. Right there in front of me. I think if I saw that headline before, I saw the words ROMs and flash drive and thought it was more discussion of the process I had already done. Sorry for that, thanks very much! We'll see what questions come up next... --Eric

@mitu I would like to use it and this :)

@rbaker I checked it and nothing helped , I used brand new Kingston microSD card so it must not be reason . Anywan I will buy new one during black friday I just want to know now , can I use Pi 3 Model B heatsinks with Pi 3 Model B + if so I ahve some of them

@hhromic Not really sure that's the culprit, that's the kernel image used to get Wine working - see the (rather recent) Diablo-on-Wine-on-Retropie thread. But for a 3B+ it might be a factor, given the frequent updates added by the Raspbian team to stabilize it on this new model.

@BuZz sorry I put whole file there now, I was just showing the main poster that I have keyboard values in this file. My setup works fine.

Unfortunatly, This is not yet good.

I'm going to check all my kickstarts files (ref here https://github.com/midwan/amiberry/wiki/Kickstart-ROMs-(BIOS).

First, I downloaded and copied these good files (CRC ok) into /home/pi/Retropie/BIOS:
Kickstart v3.1 rev 40.68 (1993)(Commodore)(A1200).rom 1483a091 / 1d9aa278
Kickstart v1.3 rev 34.5 (1987)(Commodore)(A500-A1000-A2000-CDTV).rom c4f0f55f
Kickstart v1.2 rev 33.166 (1986)(Commodore)(A1000).rom TBC
Kickstart v3.1 rev 40.60 (1993)(Commodore)(CD32).rom 1e62d4a5
CD32 Extended-ROM rev 40.60 (1993)(Commodore)(CD32).rom 87746be2

Then, I created these links (after copying files into /home/pi/RetroPie/BIOS):
kick33180.A500 Kickstart v1.2 rev 33.180 (1986)(Commodore)(A500-A1000-A2000).rom
kick34005.A500 Kickstart v1.3 rev 34.5 (1987)(Commodore)(A500-A1000-A2000-CDTV).rom
kick37175.A500 Kickstart v2.04 rev 37.175 (1991)(Commodore)(A500+).rom
kick39106.A1200 Kickstart v3.0 rev 39.106 (1992)(Commodore)(A1200)[!].rom
kick40063.A600 Kickstart v3.1 rev 40.63 (1993)(Commodore)(A500-A600-A2000)[!].rom
kick40068.A1200 Kickstart v3.1 rev 40.68 (1993)(Commodore)(A1200).rom
kick40068.A4000 Kickstart v3.1 rev 40.68 (1993)(Commodore)(A4000).rom

But I have the same issue when the WHDload Autobooter scanning files. So I'm going to continue to look at the video...

If anyone has a good idea, thanks a lot...

@BuZz Ah yes, you are right, I was confusing 2 different fixes ... Anyway, there are some improvements that we can do for Kodi 18, when it approaches the final/stable version I will talk to you.

@Stevezx81 You have to create it yourself. Just open a new document in the folder then save it with the name I gave you.

For what it's worth, I got a 5.2v 2.5a power supply. I had no reason to believe it would make a difference; but I've seen much stupider things fix dumb things.

Of course, the cursor still pops.

@cousinsfan said in Issues Making AdvanceMame Rom set...:

You said "it's corresponding" rollback set...not any old older one?

I've always only used a ROM set's corresponding rollback set when building. What's more, I always use the absolute most recent available at any time when doing so. I can't speak to the results of any other method, but I've never had an issue using that work flow.

Uhm..."simply obtain .106".....I have a question. :)

...A question that is not allowed here in any way. Please read the forum rules.

The paths are specified in the docs - for the es_systems.cfg. For the themes, I think it's in the first post, but the idea is that the themes are copied in the /home/pi/.emulationstation/themes folder (which doesn't exist by default, you'll have to create it).

Hello and thanks for the answer again. Every emulator, even if I enter Retroarch to move between commands I have to use the controller 2 instead of 1. Image the last one, 4.4 and about the retropie version don't know what you mean, I have updated the script but don't know about the version, how do I see it? Sorry and thanks again.

I managed to get it working. I uninstalled amiberry, cleared the /opt/retropie/configs/amiga/amiberry folder. Reinstalled from sources, recopied various bios roms and ended up with this rom working:

kick40068.A1200 -> /opt/retropie/emulators/amiberry/kickstarts/Kickstart - 391773-01 (USA, Europe) (v3.1 Rev 40.068) (A1200).rom

I also ensured 755 permissions on the kickstart roms - they were 744 before. Not sure which of these steps actually fixed the issue though.

@ivankahl What image are you installing? How did you install it? This matters because nobody can second guess a third party and the current image is 4.4 - you say 4.1?? Only the official image is supported. Second, you cannot use a charger to reliably power a raspberry pi, especially that one as you need a minimum of 2.5A at 5V. Finally, which SNES emulator are you using, there are 7!?