Thanks, that's the kind of thing I'm looking for. I'll check it out.

@ooskay I am away from my setup, and I don't even know where a config lives for GPIOnext. You might ask questions about GPIOnext on the github repo. The developer has been very friendly and helpful users in the past.

If you want to go the stripped down route, you can find examples of raw python scripts that setup GPIO pins for input all over the internet. In my opinion, the key to making a script successful is to define OS commands as a function that gets called when the GPIO pin is triggered using EDGE detection method. The script ends in a Pause loop or a while loop so it never terminates.

Then, you just need to launch the scrip at startup. Sorry to be so abstract about it, but it was definitely a learning process and everyone has a different config than you.

@windg said in Problem with the image after i change render res .:

Maybe a RetroArch bug?

Not sure, most likely there's a change in behavior (if this configuration worked before) in a more recent version. The render resolution option in the runcommand launch menu it's not something that's often used - probably people just change the emulator's resolution to do a resolution change.

I can try and see which setting is at stake, but as a workaround you can manually edit the retroarch.cfg (instead of using Save Configuration from the RGUI) and add autosave_interval=900. For the hotkey change, you can edit your gamepad mapping, saved in \\retropie\configs\all\retroarch-joypads, and switch the hotkey from Select to other button.

Full ack!

IMO the retropie-project and ROMS/Images are two different things - even if they depend on eachother to make sense.
And therefore retropie should never implant any direct channels to any sites or databases containing copyrightet material.

It is no Problem to find enough food for the rom-folders by just searching the internet with Google or any other search-engine.
The retropie-project should stay clean, there is no reason to offer any shortcuts to rom-collections imo.

Using raspi-config to change the audio output will not write to /boot/config.txt, but will change the ALSA (sound system) settings.
Changing the settings from the raspi-config will invoke

amixer cset numid=3 2

underneath. Try running this command from the command line (exit EmulationStation via the menu or by pressing F4) and see if the settings are kept after a reboot.
If that doesn't work, then add more info about your system, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

@mitu I know. I want to try to install it with better hardware.

Ok. I followed the instructions. I plugged in the PS3 controller during the Emulation Station startup screen.
No luck. :( Is there a specific time when i'm supposed to plug the controller in?

@mitu mb xD Thanks anyway

@tackett1980 I don't think such option exist, well at least if it does it would be something like the scrapers can do. Maybe the scraping program called Skraper can help you. That is the one i use for scraping roms. It collects data from screenscraper.fr scraping database.

Otherwise i don't know any other options, but maybe someone else here does.

@BuZz i am running the most recent build of retropie on ununtu 18.04 built yesterday from source.

I see there is an 8bitdo option under retropie settings bluetoorh, that writes to bluetooth rules. I assume this may be the culprite as the docs specify if this is not done the controller would not work on a restart.

Ah. Thanks. Thought I was going crazy for a sec there. =D

So,
for me I find "my" solution" to use two joysticks (for my 2P games) without any problem ;-)

The DragonRise USB adapter has the option to use (connect) 12 buttons (plus 4 for the directions),
I use 6 "inputs" for the second player joystick from one DragonRice Joystick-Adapter.
Three free connections on the DragonRise circuit board, and three connections which are not used when playing (like P1 and P2 start-button) and the button 4 (not used in most games), so I have totally 6 "inputs" for the 2nd players joystick.
To connect a joystick (I use my 25 years old competion pro joystick) I solder a 9 pole D-sub plug on it, on the Arcade station also a D-sub rifle.
The second player has "only" 2 buttons he can use (plus 4 for the 4 directions) , but in my most 2 player games this is enough.
In the Mame inside menu I only have to press the wanted buttons on the usual way to learn the buttons for the second player (game by game).

For me it works, no issues with a second USB controller etc .... player one and player two are using the same hardware "controller", only different inputs from this ...

I hope it's clear what i mean ;-)

D-sub rifle (nine pole; 7 used: 6 for the buttons plus ground):
arcade-buchse.jpg

Plugged in Competions Pro:
arcade-joystick-9pol.jpg

@dankcushions
Think so (/home/pi/.cache/mupen64plus/cache)and it need to be a htc file i guess ?
But still didnt get it too work.
Hope soon...

Try adding a

fbset -g 1920 240 1920 240 32

after you switch the video mode via tvservice, this will tell framebuffer console to change it's size to the new video mode.
So

vcgencmd hdmi_timings 1920 1 23 25 39 240 1 4 3 15 0 0 0 60 0 6400000 1 tvservice -e "DMT 87" fbset -g 1920 240 1920 240 32 fbset -depth 8 && fbset -depth 32

@IceChes1 said in Help organizing my FinalBurn Neo Roms. I'm a Newb:

No, I do not know enough. I have never used FinalBurnNeo and thought that the skills I learned from MAME would be enough. Won't reply here again.

fyi MAME also has the concept of non-merged sets. see https://github.com/RetroPie/RetroPie-Setup/wiki/Validating,-Rebuilding,-and-Filtering-ROM-Collections#crash-course-in-arcade-rom-terminology

@Rion Thanks. I used your files. Really useful. Especially the multi bat is very useful in my setup.
I was toying around yesterday with clrmame and romcenter to organise a 0.78 file, but I found it quite hard for a noob. Your files do help a lot !

@quicksilver

Yes I made an account a while back and it’s in the skyscraper config.

Please add more info, as requested in https://retropie.org.uk/forum/topic/3/read-this-first.
A log file (/dev/shm/runcommand.log) would be helpful in diagnosing the problem, switch debug logging from the Runcommand launch menu and then post the file's contents on pastebin.com.