@wholee said in XPADNEO error on Update:

When you have the time, would you be able to update the Retropie Setup script?

It will happen at some point.

@mitu
Thanks. I guess I just want the error suppresed and any other errors as trawling through a gamelist.xml for mame is going to take some time.

Could someone explain to me why amiberry is seen as more plug and play compared to puae, and is the recommended emulator here? Everything I've thrown at puae (lha and hdf) seems to work, I get access to the lovely CRT shaders, and I'm probably going to have to mess about with config on a per game basis for either anyway? Amiberry seems way more of a pain in the arse on several levels, to me - and that's not even considering the strange resolution switching issue I'm getting.
I'm considering just binning it off and going with puae; am I going to regret that for some reason I've yet to experience?

@mitu said in runcommand verbose logging:

Since this is a RetroArch option, I guess you can enable it from the RetroArch settings or add it to its configuration file.

Thats what I did. But, as a shot in the dark I added verbose = "1" to the /opt/retropie/configs/all/runcommand.cfg file and that seems to work. Undocumented feature?

@pjwentink It worked ! Thanks so much

@iazrt The Showcase theme (my favorite) does the same thing as well and also has a blank tag which I just removed. Just search for >< and you'll easily find a blank.

@brand said in Retroarch crashes when launching games (ES Windows 10):

What should I do?

Make sure your RetroArch works, this is not an Emulationstation problem. Also, this is a RetroPie forum, not a general RetroArch forum - you might want to try the libretro forums if you have problems using RetroArch on Windows.

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

hofnarr132 created this issue in raspberrypi/linux closed F/W 4.14.x causes dwc_otg_handle_mode_mismatch_intr:68: messages on boot with C-Media Electronics Inc. USB PnP Sound Device #2408