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

@Mamemeister said in Emulators bring up Retroarch:

Getting no luck with any of the FBA emulators. I've tried a few versions of the rom too with no luck. Does this game require a bios file per chance?

yes. pgm.zip. all required BIOS will be in a verified set.

sorry for late response i was a bit busy this days, where should i put this post?

So if i understand correctly, you have it running arcade stuff with arcade controls but if you want to play something like n64 you want to be able to use that controller correct? If that is the case all you need to do is plug in your usb controls in the correct usb ports to set the order. The usbs on the pi have a boot order so if you have all three controls plugged in you want the extra controller to be seen as the first controller so put that controller in whatever usb port makes it the first controller. Now if you dont have that controller plugged in your arcade stick will be seen as the first controller but once you plug the "extra" controller in to the correct usb port it then automatically becomes the first controller

@leeevans

That method is not very reliable and may be causing your issues. The recommended technique can be found here. Along with potentially unreliable mounting issues, modifying the es_systems.cfgwill actually break functionality with a few emulators, as some facets of RetroPie are hardcoded to use ~/RetroPie/roms/ and don't reference es_systems.cfg for a possible new location.

Hi All,
Im still struggling with the button lay out.
I bought a RPI3,2.5a psu and heatsinks.
Fresh sd image of 3.8.1
Xin-Mo dual arcade.
I have all the buttons mapped in Emulation station, and all register in Jstest, js0 and js1.
The fresh install got rid of the Xinmo not configured error when loading roms in FBA-next and mame.
When I load FBA i can bring up the RGUI and map the input binds for users 1 & 2 and Bind hotkeys, save the configuration, tried switching on save on exit, but reloading fba has lost the mappings?
Has anyone else experiencing the same?
I am also confused with the button layout best to map for FBA, reicast, and N64.
I have chosen a six button layout, see image below of the JStest outputs, wired as described in the Xin mo help thread. USBQuirks line was all that was needed to see two users.
https://drive.google.com/file/d/0B8fb44oek14BRzZQUmZ0bU1PSlE/view?usp=sharing
This image is my proposed six button SF FBA Mame button map;
https://drive.google.com/file/d/0B8fb44oek14Bc3g5cHFrN3QxTXc/view?usp=sharing
And final image is where I am confused how to map the buttons to be most compatible with Reicast and N64 and Vice etc, two proposed maps, which would work best in your experience?
https://drive.google.com/file/d/0B8fb44oek14BZ0YxUFJZOFI1Mk0/view?usp=sharing

Can anyone help uploading an actual working mapped retroarch.cfg and reicast emu.cfg files please?
Many thanks for reading.