Once again, thanks so much.

You can switch shaders on using the configuration tool here:
https://github.com/retropie/retropie-setup/wiki/Configuration-Editor

Or you can manually customise your retroarch.cfg files, some info here:

Broadly speaking, a very popular shader is from davej, which is included in RetroPie.
http://libretro.com/forums/showthread.php?t=4937
https://retropie.org.uk/forum/topic/897/updated-crt-pi-shader

Do you have more info:
https://retropie.org.uk/forum/topic/3/read-this-first

and have you checked the Wiki?
https://github.com/retropie/retropie-setup/wiki/Nintendo-64

Please note the comment about BerryBoot support here:
https://retropie.org.uk/download/

In the configs originally there is stuff hashtagged out at the top of the files originally. I thought i would remove that stuff and only have the stuff i needed. My files kept getting changed. I ended up redoing my cfg files keeping the hashtagged stuff in the top of the file and strangely enough retroarch stopped overwriting the files

@auswear Once I got the Shanwan controller actually paired it works flawlessly.Although it took nearly two months to get there,and without the most generous help of @luetzel and @BuZz it would NEVER have happened.It's absolutely crazy with this new controller I now have the exact opposite problem,the controller pairs fine and has a rock solid connection....but now the controls simply don't seem to be recognised!! I really cannot envisage spending another two months trying to get this working without actually being declared clinically insane.

@thechefpi123 nevermind my problem was solved here, apologies for wasting time

@BuZz It is interesting, are you running the latest version of akismet?
Maybe try going back a version if it was upgraded recently and see if the problem persists? I am also curious that so far only myself and @pimpmaul69 @edmaul69 have had this issue occur or at least we are the only two who bothered to report it. I would think this would be a much more widespread issue if it wasn't something specific to our accounts, IP addresses, posting habits, or something else unique to us.

@Floob Yep that was the trick. Downgraded to 2.67, removed the controllers, then re-paired them. Ran the setup in ES and all is working. Thanks again for the help.

@Floob said in Load/Save state in Zelda (SNES):

This may also help:

Those video's were quite helpful, the interval save is a nice feature, thanks Floob. :)

SOrted. Have to go into it SFTP.

@thrussmeister

I haven't given linux configuration software my full attention. I used WinIPAC to configure my older IPAC4, but you might not need to configure anything--unless you are planning to re-flash the firmware. The IPACs default to sending MAME keys for each player (although newer firmware apparently looks like a joypad instead of a keyboard).

I have done a LOT of per-game arcade configs on my 4-player cocktail setup and it's definitely easier using the actual pushbuttons and sticks as wired instead of trying to remember what control sends what key. So, I would say do this:

Figure out KEYBOARD vs. Joypad firmware first. Get support from Ultimarc as needed.
a. Deal with any Ultimarc configurations using WinIPAC if you need to. Wire the IPAC Configure emulators on the Pi.

Maybe the guys here can help you:
https://retropie.org.uk/forum/topic/2250/emulationstation-fork

In the end I figured out how to grant the local pi account the necessary access to the samba share instead.

See post for details: http://ubuntuforums.org/showthread.php?t=2330238

Regards,
Rob.

@justinbeaird A side note, if you use Kodi or RasPlex, they both have a very easy setups for video calibration. You move the a marker in the top left and bottom right until it fits your screen. Then they show you a square, and you stretch and expand it to make it a perfect square. These two methods allow them to maximize your screen space and have the proper aspect ratio for videos.

As I mentioned above, you shouldn't have any issue getting everything on the screen. It just doesn't look right. The black bars at the top and bottom aren't the end of the world, but are noticeable when the 4:3 games have a black border visible on all sides of the image.

Here is an image so you know what to expect.

alt text

The black box and green box are both 4:3. The red box represents the 3:2 (720x480) signal being sent. Which the GBA emulator assumes is completely visible.

The black and green boxes are the typical 4:3 area on a CRT TV, and again the red area is the 720x480 signal. From my understanding most TVs work like the green box shown above. The signal is a little wider, so you lose a little on the sides, but there isn't any critical information.

The problem is, that red box is the area Gameboy Advance uses, so you lose view of lives and health meters that are in the corners of most games. My setup last night was like the black box shown, where the red box fits entirely within it, and appears like a letter box. You can see there are small gaps at the top and bottom. When a SNES game played in the middle, it isn't 4:3, but really 8:7, so it's slimmer than the green box shown in the middle. You can see though, the green box has a gap on all sides within that black box. So imagine a square image within the green box, but the black box representing your view area. That is what you'll experience unfortunately. It's what I'm hoping to resolve.

Personally I think the GBA emulator should shrink the red box to be within the green box, when a GBA game is launched, otherwise leave the display as the green box so that 4:3 games fill the screen top to bottom. :)

I have updated Retropie-Setup this morning, but find no install from binaries in mame2010 installer, only from sources? I'm on a Pi Zero, but see no armv6 restriction in lr-mame2010.sh?

@GadgetJax said in Retroarch.cfg files for PSX:

Alright, and what would I need to do to re-install?

https://github.com/retropie/retropie-setup/wiki/Updating-RetroPie#updatinginstalling-individual-packages

So, fresh install seems to fix the problem? Mine was actually a 3.7 -> 3.8 -> 3.8.1 upgrade path. I'll try it tonight.