@mitu thank you, that works fine!

@roslof Thanks Roslof. I didn't know your spreadsheet already reflected an overclocked Pi.

If you can install Linux on it, it might work, but support for a new platform is not trivial to add in RetroPie. The device seems similar to the Vero4k hardware supported by OSMC, which is supported (to a certain extent) by RetroPie.

@4retropietft alr thank you so much for your help

@mitu said in EmulationStation Marquee Bug (with work-around):

EDIT: Try the Magazine Madness theme, it has support for marquees in Detailed view.

You're correct @mitu. Just tried in both Detailed and Automatic views and without videos referenced, the marquees do indeed appear.

For each theme I used that exhibits the problem, the marquee section is under <view name = "video">. Updating the themes, including Carbon, by moving the marquee section under <view name = "Detailed"> works (and would seem to be a more common scenario).

Seems that many themes used Carbon as a baseline and have marquee under the video view section. Easy to fix (or change, if it was what the author intended).

Thank you, as always.

@lostless understood, I'm on my own with this thing now unfortunately but it will be a learning experience.

@brentriddell to apply it first put the file tweakvec.py into directory home/pi/tweakvec/ on your sd card ( or other storage whre retopie is installed if that).
Then you can enter in terminal window on your PC or in retropie console next:

sudo python3 /home/pi/tweakvec/tweakvec.py --preset PAL60 you get true colors and pal 60 mode (must be sdtv mode = 1 in config.txt to get 60 Hz in all emulators)

But after next reboot you got standard ntsc mode ( with wrong colores), so if you want tweakwec fix always turned on you need write this command in file /opt/retropie/configs/all/autostart.sh It will be run tweakwec automatilly at every retropie start.

But in the end i've get right colors but also get "flickering" in some games. So to get flickering off i've used progressive mode ( write sdtv mode = 16 in config.txt)

Maybe it was helpfully too ( find my messages in the bottom of thread) https://github.com/raspberrypi/firmware/issues/811

@paul_uk Awesome thanks for this. I was using something from Katie Snow long ago but this seems a bit easier.

@sleve_mcdichael I've done this when I first started using overlays. I've found it works with some, not with others. Depends on where the overlay is from.. and if I decide to zoom in or zoom it out a little. I try to set my overlays/bezels to the best possible screen size for the system, and that's not always the stock size.

I eventually switched to manually setting the size and it seems to work really well . Once I'm happy with the bezel, I don't change it anyway.

BTW... Your description is probably the best I've read on the subject. Thanks for sharing it.

@sirhenrythe5th no problem :) it will be the default in future images at least.

let me know if you get any audio drops! the gameplay should keep going but the audio cuts out for a second or two.

@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.