You may be able to launch your python script from the runcommand-onstart script and reset it with the runcommand-onend script.

See: https://retropie.org.uk/docs/Runcommand/#runcommand-onstart-and-runcommand-onend-scripts

@tmntturtlguy Very cool. I didnt realize until now u can just scrape the videos and roms together with Steven Selph's Scraper. This seems pretty fool proof and simple. I am going to give it a try today. I was just scraping the roms before. Just saw the video option.

Thanks...

@aryetis that's the joy of open source projects. Many projects we use come from upstream so when things break it's often nothing we've done and issues and fixes need to be done upstream.

Just for reference this is the repo for desmume and you can see in the recent commit history some changes were made to the makefile and those may have broken the compilation:

https://github.com/libretro/desmume

@spruce_m00se Why do you need to back up scraped roms? You back up your retroarch.cfg.

@jmesa732 you'll find that with the official image generally things will work and if they don't you'll at least know what you've done to it so it's easier to troubleshoot and we're happy to help of course if you get stuck

@Aryetis Great, thanks, that was exactly what I was looking for.

Old thread... My first thread.

I answered some question on myself.

I know I can create maybe "DOOM-TNT.sh" and can put command from emulator call from DOOM.WAD to TNT.WAD. But now if I save games from DOOM1 and DOOM-TNT they are all displayed in both games titles togehther. This is a bad solution.

I created some bash scripts that will solve that.
You now need only one folder with all WADs inside.
You will need zip support enabled so please get zip with sudo apt install zip

Get the scripts here from github

Update: 15.07.17

added FreeDoom1 added FreeDoom2

They work flawless!

Quake issues ...

Two ways...

Use the wiki here! It's the recommended way If you lack of space or you are not able to run Quake and it's official and inofficial packs you can discuss here

Maybe next year I'm back with HeXen and Heretic :)

Solved.

turned out it was actually a malfunction in RGBCommander; the developer contacted me directly to say he was working on a solution. He let me test a rebuilt daemon, and will roll the fix into his next release.

Check out this thread at Arcade Controls.

—Æ

@daistaar if you've updated recently you'll notice video support was added.

Whether or not it was added well or how useful it is is up to debate (I made it function, though I wouldn't call it beautiful)

So if you can clean it up and make it better I have no qualms and would accept pull requests

Initial commit for reference:

https://github.com/HerbFargus/es-theme-tronkyfran/commit/5773aab7f6d2f5bd3fc397551857866a511d3849

@bombay The Raspberry pi is not a pc (x86/64 architecture) therefore it cannot run "windows games" natively. Like for every device, programs have to be compiled specificallyf for a type of machine (pc/mac/Android/etc). So there are two solutions out there to run "windows programs" on Raspberry pi.
1/ You get the source code adapt it and recompile it for the Pi (very unlikely)
2/ You try to run your games throught some "pc & windows emulator" like exagear ( https://eltechs.com/product/exagear-desktop/ )

I think you need to edit the first post to change its type to "Ask as Question". Don't know if it can be done retroactively.

Then you should be able to mark it as solved.

Hope you enjoy the new changes!

@herb_fargus When using the "Update all Packages" is that updating from Binary?

I'm running into a similar issue as well. Through searching through the moonlight github it seems the move to SDL2 has caused some issues with RetroPie. The developer of Moonlight has stated that they wont bother with fixing the problem as it comes from the way RetroPie handles controllers using SDL2 framework. Something around how the buttons are mapped and what the system sees. I'd love more help trying to track this down as well.

@shinyabsol i wrote a guide a while back about the custom gameboy palette and how to do so properly.

https://retropie.org.uk/forum/topic/9769/game-boy-custom-palette

I'm pretty shure Triggerhappy is running, because if it was not running it wouldn't have worked for the shut down hotkey.
I found the "name" of the buttons by using the "thd --dump /dev/input/event*" command in the post you recommendet and created a .cfg:

BTN_BASE3 1 /usr/bin/amixer sset PCM,0 2dB-
BTN_BASE4 1 /usr/bin/amixer sset PCM,0 2dB+

The buttons are connected via USB to the Raspberry and work great with the commands configured in emulationstation. The Speakers are plugged in to the 3,5mm klinke output of the pi.