@jimbo will test and up swap if needed.

A bit more expensive than the Chinese ones but may have to use it. Thanks for that.

@mitu no, i did not...

I was trying to map 0 and 1 to the l2 and r2 bumpers.

I added these lines to /opt/retropie/configs/videopac/retroarch.cfg above the inclue:

input_player1_l2 = "num0"
input_player1_r2 = "num1"

and tried going into the emulator's "Quick Menu / Controls" by pressing Start + X

lr-o2em Controls Menu

and no luck.

There is just no option for anything other than direction and fire. the retroarch.cfg changes I can see in the menu, but don't actually work to select a game

@mitu Thanks! I will try it.

I have found that arcade games using lr-mame2003 have vary wildly in their audio volume. Onw example, is Xevious which is much louder than other games and some games end up being much quieter. I know I can adjust the volume under settings / audio but that isn't persistent. I know about the hotkeys for volume up/down but again, I would have to raise adjust the volume every time I play Xevious for example.

Is there a way to adjust and save an individual game's volume? I checked the mame menu for Xevious and didn't see a volume option. I guess my other option is to figure out how to install a volume knob in my cabinet so I can just adjust on the fly but that's not much different than using the hotkeys other than a quicker way to dial in the volume. It sure would be nice to just be able to save a +/- db per game and be done with it though.

@koogelpotato Are the files listed when you ssh/SFTP to the snes rom directory on the pi? If so, check if they are all the accepted file extensions. If you've confirmed the files are indeed on the USB drive, you may want to check your freespace on the pi with df -h to see if you are out of space on the SD card.

@mitu

Awesome man!!! Thanks, was that suckin show metadata only.

Thanks a lot

The Pixel desktop is actually LXDE, it's probably the new version that's different a bit from the previous one. If you wish to install Chromium, then open a terminal/command line and install it by running

sudo apt-get -y install chromium-browser

@radiusxe

The best you can hope for is to load the save state from the previous core version and work your way to an area that allows for a normal memory save. Afterwards, update the core load the save and make a new save state. I realize this wouldn't be possible for all games and it's a major hassle, but it's really the only option. It's best to only utilize save states for very casual use and at no time when it's crucial to keep them for long periods of time. Save state formats can change at any time depending on development. You might see an emulator/core keep its format throughout its lifespan, or you might see it change several times a year.

@zerojay
Ok, thank, too bad.

For what it’s worth...I ftped into my pi and downloaded the entire rom directory and Bios directory. Reflashed the card with 4.4 and uploaded the rom and bios directories. It took some time, it was easy and it worked.

Best bet, back up the entire card before you reflash so you have something to go back to.

As @TheDataCereal said, open the RA menu (Select + X) while in a game and change your Input settings, you probably want Player 1 to be the NES gamepad instead of the arcade Joystick. I don't think this is caused by the auto-save-on-exit settings.
As an alternative, use @meleu's joystick configuration and you can configure - per system - which controller is which player.

I go the other way. Connect my 8bitdo controller then install the ps3 drivers. The 8bitdo still works and my ps3 controllers connect fine and vibrate etc like they should

Never tried the other way.

dear
thanks for the response and the info
I will have it.

thanks and regards.

@christiang

Here you go.

https://retropie.org.uk/docs/Updating-RetroPie/#making-a-backup-option-1

@ss3000

Try setting the overscan in /boot/config.txt using:

overscan_left= overscan_right=

Edit: Of course if that works, you may have to reconfigure your RetroArch display settings to accomodate.

@epicrean said in Bezels and sizing basic question:

I went through Retroarch and changed the X and Y position

Every overlay is made for a specific screen resolution (not for specific TV); e.g. 1080p, if both TVs are set to 1080p the overlays must display correctly on both.
On top of that each overlay has a viewport (actual game area) that is sized for specific game area scale (e.g. integer scale, 3x, etc). If your retroarch settings for a specific core are different than the settings the overlay was intended for then it will not display correctly.