Yuv444 is a known problem for OMX player. There are at least two scripts to fix that for multiple videos, one by myself and one from @hiulit. May be worth a try if most scraped videos work, but some don't.

Yep! Thank you :)

It should be fixed now, just need to update the RetroPie-Setup script to get the fixed version.

Think I figured it out. Disabled the splash through Emulation Station. Didn't realize it was in there, thought it was changed in the config script for RetroPie. Now everything works.

Me too. That option in settings/retropie setup/configuration-tools/autostart/emulationstation at boot saved my day!!! Thanks!!!

@martelfab said in Game Button Mapping:

@mitu im using name libretto . This menu is fairly difficult to understand. Not really sure how select the choices ? Any thoughts?

You just select a button and then tell it what you want that button to be assigned to. So you click on the button for start and then tell it which button will be used to press to start a game. There are a set of controls defined for the user interface and the menu you are in, will only work if those user interface controls are configured correctly. ie select and cancel need to be right so that you can select a control to define it.

Hi all,
Found a solution. Under custom controls found Joy1 Fire/left mouse button. Thanks go to someone on the WHD load Facebook group.

Dwarfboysim

Hi all,
Looks like the creators of VICE did an update and resolved the issues. Performed an update from binary and all fixed :) The turbo setting under speed did manage to get turned on. Turned this off and now running great!!

Dwarfboysim

@Robotechvfx That’s a really nice image- I hate to ask, but can you post a link to it? I’d love to use it on my system.

So chances are I'll probably not be able to get the audio working without some converting. Bummer. I wonder if anybody can confirm if these games are ALL ape or maybe just a few of them. I don't want to share the location where I can get it but it's pretty well known. I just don't want to blow +100gb getting the collection if it's not going to work.

@Retribution Please add more details about your setup, as requested in https://retropie.org.uk/forum/topic/3/read-this-first. What method are you using to run your ROMs from the disc ?

@blujumanji when I recently loaded a new retropie image I was really confused because I had the same bios files on my older image and suddenly with the new image the PSX ROMS wouldn’t load. Oddly once I updated the lr-pscx-rearmed emulator from binary it suddenly worked with no other changes. I had thought that wouldn’t be necessary to update because I had just downloaded the “brand new” retropie 4.4 image and the PSX emulator is part of the image so I figured it would be “up to date.” But apparently that is not the case. So maybe try putting both bios folders in again and updating the emulator (go to retropie setup, manage packages, I think lr- psx rearmed is under either main or optional, and then update, update from binary) and see if that works.

@chubsta You should give Skyscraper a try - it's part of the RetroPie script, just like Steven Selph's scraper - https://retropie.org.uk/docs/Scraper/#lars-muldjords-skyscraper.

@MajorDangerNine Thanks - I'll check it out.

@StuMcBill Well, if it's a controller problem (the 8Bitdo) and the timeout comes from it, try pairing it with a different 'mode' (it supports Android/PC/Switch/Mac ?). There was a topic a while ago from people testing various modes and the problems each one has.
I'd try using a different mode to pair the controller (PC/Switch) - remove the current pairing mode and try re-pair while starting the controller in a different connection mode.

Anyone! I’m really desperate to fix this.

I also have the same condition with the Pi 3B+ and NESPi+ case running most recent RetroPie 4.4 release. It seems to happen with all wireless dongles connected in to the NESPi case ports (wireless Keyboard, and Xbox 360 adapter for sure). I found a couple different threads in the forum about it and I believe they found the reason, https://github.com/raspberrypi/linux/issues/2408, and I believe they were working on a fix, but I have not seen the true fix anywhere.
(If anyone has it and a step-by-step, I'd be grateful)

**I did find a temporary workaround though, without having to revert to previous Pi versions-
Use another USB hub (like a laptop 4-port) to connect to the NESPi case, and then connect your devices in to that. It appears to cancel out whatever mismatch there is between the pi and NESPi USB hub.

It's a bit unsightful but it prevents a lot of re-imaging and reversion to a previous release. Hopefully a solution will be embedded in to the next release as the NESPi case is great!

*I have been successful using either an Insignia 4 port USB2.0 Hub (N5-PCH5420) and also with a Sabrent 4 port USB3.0 Hub (HB-MNBW). Not sure if a powered USB hub will do the same but worth a try before frustrating yourself to no avail looking for a solution.

My devices connected were a Microsoft Xbox 360 Wireless adapter, and Logitech K400r wireless USB keyboard.

Good luck out there..

@noobsaibot It depends, you still haven't provided any info about your system.