@mitu I tried removing it. I'll try explicitly setting it to "nul" and see what happens. Thanks.

Edit: Yeah, that did the trick.

Solution worked (remove the corrupted file) but since I have way too many mame games with different emulators set, this isn't really a file I wanted to "start over" on. Similar to what @jackyracer already said, just wanted to remind and confirm that in my case I copied the bad file to my computer, still opened (thank goodness), copied and pasted the cfg text from the old file to a newly made emulators.cfg file, and moved the new file back over in the same place. All fixed, but most importantly, no damage done.

@mikes82

I make sure to keep a backup of my build as an image file incase my kids mess anything up.

I also disable the launch menu for the games in options run command.

And for mame I map the mame config menu to the keyboard as they don't use the keyboard.

And using kids mode.

I ended up making a seperate kids only setup and getting my kids a pi of their own and backed up their setup so if they do somehow manage to break it I can just rewrite the image.

They didn't want much content just some of their favourites and kodi
Sim

@thorr69 Hey just wanted to confirm that it was a bad ROM issue! Thank you for the help!

Solved!

So the issue was, it was using ~/.config/eduke32 as the config directory where everything went. Even changing the executable's filename did not change this location used so it must be hard coded in the application somewhere (even if it's just "this application is called eduke32" and then it just used "whatever the application calls itself" as the config folder, that is what it is using.) So there really is no way to change the save location... [one more thing I don't think I tried: renaming the folder in which the executable exists -- but it doesn't matter because even if it did work (I have doubts), I think the solution I ended up with is more elegant than quadruplicating the executable folder four different times for four different games.]

...EXCEPT! That location is, already, just a symlink to the config folder in /opt/retropie/configs/ports/duke3d. So, inside of that folder, I made three new folders: dc, nw, and vacation. Then I edited my launch scripts to re-link the .config/eduke32 link. At first I got an error: "failed to create symbolic link: file exists." So I tried it with the -f(orce) option. Got a different error: "cannot overwrite directory." Finally, I decided to just remove the existing link before creating a new one (and then -f was no longer needed.) That worked! Now, before a game is launched, the link in ~/.config is reconfigured to point at the correct subfolder, and then saves and configs are stored separately per-game.

After the game exits, I set the link back to its original location and, for good measure, I move the log in $HOME to the config folder first.

Example duke3d-vacation.sh launch script:

#! /bin/bash rm ~/.config/eduke32 ln -s /opt/retropie/configs/ports/duke3d/vacation ~/.config/eduke32 "/opt/retropie/supplementary/runcommand/runcommand.sh" 0 _PORT_ "duke3d" "-j /home/pi/RetroPie/roms/ports/duke3d -g vacation/vacation.grp -x vacation/game.con -j /home/pi/RetroPie/roms/ports/duke3d/vacation" mv ~/eduke32.log ~/.config/eduke32 rm ~/.config/eduke32 ln -s /opt/retropie/configs/ports/duke3d ~/.config/eduke32

For the Original duke3d.sh script I still set the link to .../configs/ports/duke3d before launch, just in case anything prior left it in weird shape, but obviously I don't have to "fix" it after since that's the original default location anyway.

@andykt76 great tutorial thank you for doing this. I followed your steps for the PS1 lightgun setup and now I’m stuck on the guncon calibration screen in time crisis. I can’t seem to get it to move past this step, any suggestions or did I take misstep?

Thanks!

@red2blue bump

@jigidyjim

Well, this looks a little disheartening. I can't believe you would have to hardwire a shift/alt button, but I'm glad I found this thread before I went down the rabbit hole. I'm currently using a controller called the iPac and it has a mode that acts like a keyboard as well as a mode where it acts as a USB controller. There is a keymap/button configuration tool and also provides a macro setting. I'm hoping this will be the solution because I don't like the idea of getting into a situation in the future where I have hard-wired macros and the software changes the way it works. Regardless, thanks for the thread which really shortened my research time.

@mitu, perfect. Thanks for the help.

@windg Ok, thank you!

@segasonic ...and we have a winner! Thank you very much!

@muldjord said in Skyscraper appends 'T000000' to <releasedate> tag with '--flags unattendskip':

3.6.15 re-released with a fix now based on regular expression. I've tested in in various ways and it seems to work now.

Looks good. I can still break it if I try, by doing weird stuff like:

19970303T12 becomes 19970303T12T000000.

19970303T123456T000000T123456 becomes 19970303T123456T123456.

...but that's me trying to trick it on purpose. For regular use it looks to work fine: the multiple T000000's that got in there automatically, are now automatically removed, date codes with proper 6-digit time stamps are preserved, and ones without are given a single T000000 (which is then preserved.)

@alistairgd having extra loads can increase, whats called, the rise time. no power supply supplies full voltage when first turned on. I work on power supplies and The rise time can be upwards of 100ms. And while that’s a very short time, its enough time to run a few cpu clock cycles on the pi under volted. Add in the extra stuff and you may get a few more dips as those devices power up.

@mitu umm so I was trying to get the blender package and tried to update and that made my retro pie work so sorry for wasting your time 😅

@lister-of-smeg I was halfway through another process on resolving the issue when I saw this post, so I didn't get a chance to try it myself. I appreciate your help and the knowledge you shared though!

This whole mess was a lesson learned for me, so I'm on the same page with backing files up now. Copying that RetroPie-Setup folder was my first priority before running git reset --hard. Thankfully, it doesn't seem like anything broke.

@retropieuser555 Multiplayer is fine for any other emulator. Goldeneye is actually the only game in which I use lr-parallel. I understand it, it is pretty outdated, but seems to work best for this specific game.

When I attempt to play multiplayer for Goldeneye, player 2 looks fine, but the window for player 1 blinks super fast. It is definitely unplayable in this mode.

@kartillian said in No Audio but only in ES / Roms:

I now still get the error message.

This means the Audio Device is not set properly in the EmulationStation settings. Make sure you have chosen 'HDMI' as the output in the Audio settings dialog in the RetroPie menu, then configure again ES with Default/HDMI as Audio Card/Device.

EDIT: I've merged your new topic here. Please don't open separate topics for the same issue.

@mitu fixed

This was solved by using a different controller. Both sticks work fine with my new Logitech F710. The issue still exists with my generic ("Microntek") gamepad.