@darknior i think the language bios’ have to be loaded as carts on an msx. There has been discussions on doing this on the pi

something seems off aobut Williamsmith007's reply, should it be flagged as spam?

@jborges you're providing so little detail here, and you asked the question a few hours back so I wouldn't be surprised by it.

Do provide more details per the post that's present on every single page in the forums and that every user acknowledges when they sign up.

@drrevan it's most likely an issue with the emulation then. Try it with a different emulator/plugin.

@wihaedud

Hi. What did you reconfigure in RetroArch to solve your XBox One Controller problem? I think I have the same problem.

I have already tried all of what you tell me.
Anyway thanks for trying helping me.
If someone has the same problem, the solution for me is to download retropie 4.3... - -‘

@sixstring396 this is normal behavior. The pi should start to boot, then detect that the switch is in the off position and shut back down.

@steptoe I think you didn't read the entire post. It was the Power Supply that came with my Pi. "The LED may be drawing far too much power", that could be the Case, if I hadn't told in this post multiple times that the LED is not even connected to the Pi anymore. And, my Power Supply is enough for my Pi. My Pi worked flawless with Overclocking and with the Reset Switch. I just damaged my Pi with sodering the LED.

@m2306 You bought that controlblock so I'm not sure how you can overclock properly. Should've bought a zero delay usb encoder, connect your joystick to that so then you can buy a flirc case or a heatsink+fan combo.

Do you need to overclock? No. Should you, if you had the ability to? Oh YES. Snes requires all the power it can get. The latest snes emulator, lr-snes9x, requires even more. If you want bleeding edge snes emulation the pi can handle, then you have to use that one. It's actively supported so any bugs will get worked on faster than the rest. MSU-1 support as well. As an example: I still get slowdowns on kirby3 at 1.5ghz. There's also a setting to speed things up to fix the original emulation slowdowns. So games like super r-type don't get slowdowns anymore.

Arcade games need it too. It's such a hassle testing each game to see which one runs the fastest and with proper emulation. In a perfect world, if the pi could run the latest mame, then one arcade emulator would be so awesome. As it is now, I have to juggle between four arcade emulators, other people even more. A faster speed would help the situation a bit. I'm still slowly moving games from mame2003 to fba and I need to re-test the 4player konami games again to see if I still get slowdowns, so I can eliminate using fba2012.

I forgot about lower end emulators like nes and genesis. They can also benefit by having the ability to enable the run-ahead setting to shave off a few frames of input lag. That feature requires tons of power too.

I would've gone with something more powerful like an odroid xu4, but the level of support will always make me stick with pi's....that and I have no idea if my original snes pad driver will work on the odroid. I would want a silent cooling solution and I heard the giant heatsink version doesn't cool properly.

@Nextus
Make sure you've purchased the NESPi Case +, the latest revision from RetroFlag.
There were issues reported with the previous case and the higher power requirements of the Pi 3+.

@angry_bucket
I don't think that's correct, but curious to know more about your experience.

RetoFlag's safe shut-down script advises to set this to On before installing the scripts. I followed this and everything works fine (as long as EmulationStation is running).

https://github.com/RetroFlag/retroflag-picase

[Edit] I purchased one of these a month ago - love it.

@douga said in Screwed up sizing of EVERYTHING playing with MAME:

Looks like I was a bit slow, but anyway, you can force whichever resolution you want by uncommenting the hdmi_mode line again and setting the value. You had it set to VGA resolution, according to that link.

Yeah. Thanks man.

Strange thing is that I never un-commented either of those lines. I know that there is some strange resolution changes that happen when entering and exiting games in MAME and FBL, so I'm thinking that the commenting/un-commenting of those lines must happen while using those emulators and I just happened to freeze the Pi after the un-comment, so it wasn't going to be fixed until I figured out what needed to be done manually.

Thanks for that link. Bookmarked. :)

@douga @mitu I've wired them the same way and it workds, so thanks everyone!

@benjiman You can use the File Manager - in the RetroPie system menu - to look in the file directly on the Pi, but it's easier if you have a PC and connect via file shares at \\retropie\configs\all\emulators.cfg.

@fitz43

With the exception of MAME variants, bezels are a feature limited to RetroArch.

@jrpohlman39 good news... I had the exact same problem a while ago with Robotron. Please see the discussion here:
You can map this in mame menu. Within the game it can be accessed via keyboard by pressing TAB key. You can map player 2 joystick to player 1 inputs.

Even better: with the new and very cool mame2003-plus-libretro emulator there is a core option implemented for this. Once set, it enables this control scheme for all dual joystick games. See this github issue 278 and github issue 216

There is a dedicated thread in this forum for mame2003-plus here

@mitu sorry about that it's Retropie v.4.4 with emulation station 2.7.5

Anyone have one to test out also?

I ended up just going back to the 3.5mm jack for audio in my cabinet. Based on the linked article, I just made sure I had the following settings in my config.txt:

disable_audio_dither=1
audio_pwm_mode=2

For some reason my pwm_mode was set to 0 in my config and changing that to 2 resolved all my issues with the 3.5mm jack.

Unfortunately, I was never able to get the crackle / hiss / static noise issue resolved when sending audio out HDMI to my HDMI to VGA adapter.

Well, first you have a lot of addons installed that might be related to "piracy", I don't care about it, but that might cause problems, especially because many of them are done by people with little experience in coding and/or with malicious intents, be carefull about what you add to Kodi.
Second, you have a lot of errors (besides the ones from the addons I mentioned above) that Kodi cannot read or says that the file is read only:

1:43:30.972 T:1631396784 ERROR: SQL: [Textures13.db] Attempt to write a readonly database

This generally indicates that your system suffered file corruption, or most likely, your microSD card is broken or faulty.
This isn't easy to fix, and is impossible if your card is broken.
Try to move or delete your Kodi settings (/home/pi/.kodi) to start fresh with default settings.