[Floob]

@retroco That sounds like a very different problem to blockaboots. You say you can pair yours. If you are using pifba that wont use the retroarch controls so it may just be a config issue. If you are using lr-fba, check this to set the credits:

FBA Retroarch core – coin controls

[Floob]

@blockaboots Which option have you selected where Master System is sluggish? If you let me know which of the options you have used I can check the config.
At the moment there is only one shader option, the rest are overlays, but I could always add other shaders as options.

You can find various non scanline overlays in
/opt/retropie/emulators/retroarch/borders/
and some here
http://retroarchborders.blogspot.co.uk/

[Floob]

This video may help if you want to see the install in action

[Floob]

Here is a guide that may help.
https://github.com/RetroPie/RetroPie-Setup/wiki/First-Installation

If you want to add RetroPie to an existing setup (the option above is much easier unless you really need to keep your existing build) you can use the guide shown here:
https://github.com/RetroPie/RetroPie-Setup/

[Floob]

What version were you on before updating to RetroPie 3 final?
Can you attach your controller config?
It should be in /opt/retropie/configs/all/retroarch-joypads/

[Floob]

Are you running RetroPie 3 final? Have you overclocked the Pi?
Which game/emulator combo has an issue?

If you try Super Mario World on the SNES, do you have the issue with snes9x-next as well as pocketsnes?

[Floob]

Have you copied the BIOS across?
https://github.com/RetroPie/RetroPie-Setup/wiki/Game-Boy-Advance

[Floob]

@geauxwave – If you want to provide the images used in your examples I’d be happy to add your settings to this video tool to let others qyuickly try out your settings.
I’ve added thorigs yesterday.
https://github.com/biscuits99/rp-video-manager

@dankcushions – that sounds great to create custom per rom configs for libretro based mame emulation.

[Floob]

I’ll try that out and see what happens, have you tried lr-mame4all or lr-fba as an alternative?

[Floob]

Try playing a game, then choosing the shut down option from the Emulation Station menu as opposed to pulling the plug.
Is your gamelist.xml on the USB as well?

[Floob]

Can you do one step at a time
– Re-image (SSH should be enabled by default)
– Copy just one systems roms across and see if you have the issue

Its not needed to restart the Pi after adding roms, but you do have to quit Emulation Station. It will auto restart after 5 seconds unless you press a key.

[Floob]

Which version of RetroPie are you using?
Have you tried the new RetroPie 3 yet?

[Floob]

Yes, the core options save independently the retroarch.cfg file.

The retroarch.cfg specifies it here:
core_options_path = /opt/retropie/configs/all/retroarch-core-options.cfg

but this can be overridden in the rom specific config file to point to a different file.

[Floob]

Ah – yes, I think.
You can specify the file location of a different core setting file in the rom specific retroarch config file.
Then simply have whatever settings you want in the new file.

This will only work in RC1.

I could do a video, although this is quite niche. I may get about 10 views! haha!

[Floob]

If you hold the “select” button and then press m does that work?

[Floob]

Mainly because there are a mass of changes between 2.6 and 3, not least the paths changing.
It would be best to install a clean version of RetroPie 3 if thats practical for you.

[Floob]

You can see what is being updated here:
https://github.com/RetroPie/RetroPie-Setup/commits/master

And you can make suggestions for new features here:

Ideas for Further Enhancements

[Floob]

I could put some more 720p options into this tool
https://github.com/biscuits99/rp-video-manager

Although I have a 720p TV and it sort of gets the 1080p ones to work, so it could be worth trying on the off chance. Also, just a reminder, if you have tweaked your config a lot, do backup before using the tool unless you are comfortable editing the system based retroarch.cfg files.

[Floob]

@sunshineh
Is this one helpful?

If not, let me know the parts that arent clear and I’ll try to do an update.

[Floob]

Which system are you trying.
To check it has applied, read the retroarch.cfg file in (for example)
/opt/retropie/configs/megadrive/retroarch.cfg

This should have all the updated code in it.

*MAKE SURE* you run the install option in the config menu though, or it wont work.

[Floob]

For reference, if I capture gameplay or EmulationStation I use an Elgato.
https://www.elgato.com/en/gaming/game-capture-hd60

I use the HDMI port to capture it.

[Floob]

Thanks for the feedback. I’ve just uploaded a new version.

[Floob]

Are you using RetroPie 3 (any of the betas)?

Here is a slightly updated version

https://mega.co.nz/#!2NAUwbAL!BrgkCCWMerAxKDDE_0LYtR2qKjkDN26QZbDrIuIJ_28

Put it in your home (/home/pi) directory and

unzip -o rp-video-manager-11-JUL-2015.zip
rm rp-video-manager-11-JUL-2015.zip
cd /home/pi/rp-video-manager
chmod 755 videomanager.sh
./videomanager.sh

[Floob]

What happens if you dont specify the joypad buttons in the system specific retroarch.cfg and instead use the auto controller file in /opt/retropie/configs/all/retroarch-joypads/ ?

If you just put the single SNES usb port in the top left usb port, dos it see both and assign them as player 1 and 2 (indicated by the yellow retroarch writing)?

[Floob]

I think this is a bug in that version of RetroArch.
If you backup your card, then try update the binary of RetroArch and update that retropie script. Then try again.

https://github.com/RetroPie/RetroPie-Setup/issues/905

[Floob]

Yes, slows down for me on a Pi B as well, although is better under gngeo than fba-libretro.
I havent tried it on mame4all, but should be better under that.
Which emulator are you using?

[Floob]

You could try this tool to make it easier:

How to get perfect video scaling and list of recommended resolutions

Its not finished but it should help you.
I’ll try to sort a video soon to explain how the data gets overwritten when you use RGUI.

[Floob]

Yes, make them in the specific system version of retroarch.cfg, like /opt/retropie/configs/megadrive/retroarch.cfg
And make the change at the top of the file, before the #include line.
If you add it after, it wont override the one in /all/retroarch.cfg

Lines with a hash, # are just comments, they can stay if you like as they are ignored. Just dont take out the #include line as that isnt a comment.

[Floob]

This partly answers why that happens:

Can´t save settings on Snes9x Next and Psx

The short answer to that is rip out the changes you need and manually add them into the retroarch.cfg, it should take about 5 mins when you get the hang of it, and you only have to do it once.
I’ll try to do a specific video for that. In the meantime, check this one:

[Floob]

Are you running a particular version of RetroPie?

Can you post details requested here? Thanks

Suggestion to get support with your problems

My guesses to the fix are, hold Select on your joypad and then press F1 on the keyboard (or whatever your x button on the joypad is)

Create a file (if it doesnt already exist) here
/opt/retropie/configs/all/retroarch-core-options.cfg

and put this line in it
gb_colorization = “enabled”

[Floob]

[quote=102215]rename -n "s/#//g" *

Can you please explain me this syntax? Just for a better understanding.

[/quote]

The -n part means “take no action” so it just shows what would happen.
When you want to run it, remove the -n option as buzz says.

The “s/#//g” part means
“substitute occurrences of the hash symbol with nothing, and the g means do this for every occurrence of the hash, so do it globally”

The * just means check all files.

[Floob]

Oh, I use the default libretro-pcsx-rearmed version which uses RetroArch. I’m afraid I havent tried the one in experimental.

If it helps, my setup is here:

[Floob]

I wouldnt recommend it because
– The formatting gets changed making it a nightmare to make manual updates to afterwards
– The file will then contain all of the retroarch.cfg settings making it contain far more info than you need, which makes it difficult to see what is really just needed for that emulator as opposed to all emulators.
– Any custom changes that you may have made to your pre-existing retroarch.cfg wont be held within there anymore
– There would no longer be an -include- existing in the file to reference the /all/retroarch.cfg which means that when you run a game, no changes in there would be looked at
– This could also risk losing the reference that /all/retroarch.cfg makes to the auto controller directory
– If it does keep looking at the auto controller directory, it has a conflict with the controller settings that are then showing in the newly created config file, making debugging controller issues very difficult.
– Any RetroPie based settings such as pre-setting the hotkeys to work in a certain way could get ignored as they would be in the /all/retroarch.cfg, although that may get carries accross.
– There are basically a lot of settings that would get ignored and/or duplicated

That said, it will most likely work, I would just despair at trying to debug any retroarch issues someone may have with that approach. Unless of course RetroPie wasnt being used and it was a standalone installation.

And no, I wouldnt add the file to the end of the existing file, as that would really complicate things as it would continue to pull in the main all/retroarch.cfg and then repeat the whole config file that had been generated, lots of conflicts then.

[Floob]

Are you talking about changing and saving settings with RGUI?

If so, make a save with and without the change, that will produce two new files in /opt/retropie/configs/{systemname}/

Use a diff file checker to see the difference, and put the resulting few lines (probably 2 or 3) into /opt/retropie/configs/{systemname}/retroarch.cfg

Or you could just bodge it by renaming the newly created file above to be retroarch.cfg, but I wouldnt recommend that.

[Floob]

Make sure you arent running ES when running the sselph scraper.

[Author]

Posts