See https://forums.raspberrypi.com/viewtopic.php?t=58151 for potential issues during boot. It details most problems and how to find them based on the led blinking pattern.

@DJ151 Not to worry, you weren't disrespectful.

@jbsapp
Great information.

I was curious and managed to locate a little detail on the fuzz and other arguments.

https://stackoverflow.com/questions/16110515/explanation-of-fuzz-and-flat-in-input-absinfo-struct-in-input-h

You can find that

fuzz: specifies fuzz value that is used to filter noise from the event stream.

Which means that the input system in linux will drop events generated by the device driver if the difference from the last value is lower than the fuzz. This is done in the input layer.

Another user posted:

So it would seem that any changes less than fuzz are should be filtered out / ignored.

Also,
https://python-evdev.readthedocs.io/en/latest/apidoc.html
The Device section talks about the fuzz argument.

If the heating is still present if you exit EmulationStation, then the problem is somewhere else - just exit EmulationStation and leave the system to run for a while.

Is the problem with the theme? Or because I'm using Retropie 4.3?

I don't think the version has any influence, but why use such an old version ? Do you have anything running in the background besides EmulationStation (music scripts, input handling scripts) ?

Did you do any soldering/modifications on the Pi ?

Thanks, both - it turns out it is a quirk of the emulator and doesn't like it if there is an extension on particular types of roms. A .sh solution has worked though! Thanks again.

Just for a test i set a 90-second duration.

on my Pi0W the splashscreen was shown for about 75-seconds.

on my Pi3B the splashscreen was shown for about 80-seconds.

So the timer is working for long durations, but it is just not accurate :)

No worries. I can live with it. As I mentioned, i just need about 30-40 seconds.

thanks again.

@dominoman2 said in Changing audio output from 3.5mm Headphone to USB Headset, using RetroPie Menus <tag>audio</tag>:

When I run the scripts I have to restart EmulationStation for the sound output changes to take effect

I guess that for EmulationStation to pick up the changes you need to modify the audio settings for the sound to be re-initialized, but for emulators it shouldn't be a problem.

Press the M key to open up the drastic menu and configure your keyboard.

You can back-up your ROMs and configurations from the old system and then restore them on the new system via file shares - see https://retropie.org.uk/docs/Updating-RetroPie/#backup-option-2.

@trecuu said in 8bitdo Ultimate Bluetooth Controller Compatibility:

@mitu
Managed to fix it by downloading a beta firmware for the receiver to be able to change to D-Input.
It does not work while on X-Input, only on D-Input.

Thx for the help.

Hi @trecuu I’m in the same situation as you but I’m not able to find the beta firmware you mentioned. 8bitdo Support informed me that it was no longer available. What version number is the beta? Any chance you still have a copy of the beta firmware? The latest controller firmware is V1.03 and V1.02 for the usb dongle receiver. I appreciate your time and your help,
Best Regards

That did the trick, uninstall IMP using the install script to do the uninstall.
Check all the sound was working as expected and it was
Reinstall of imp and I have audio goodness coming out of my Arcade Machine again :)

I figured it out, or at least why it wasn't working in Tempest or Centipede. Having it work in Marble Madness threw me off by making me think that the correct mouse index was already set. It was not. My trackball is at mouse1.

In the main retroarch.cfg I set:
input_player1_mouse_index = "1"

That fixed it.

Just a heads-up: removing xpad might break the controller in emulationstation and elsewhere. In my case, the triggers weren't being properly parsed, and as such they couldn't be properly mapped. Hence, I wasn't able to simply remove said driver. That being said, the original solution by @tuxophil DOES work properly, and as such I would still recommend it. Keep in mind, though, that the command at step "8" requires a declaration about which controller you want to map. As such, a correct command might be ./controllermap 0 >> ~/my360.txt, if your X360 gamepad is in slot 0. Running just ./controllermap will show which controllers are connected, so use your gamepad's slot from that list.

@mitu I've been editing the XML manually. I looked around for some of the common errors mentioned (illegal characters like &, etc) and didn't see any of those issues. If the XML was "bad", the file wouldn't load at all in ES.

I'll look at the file and see if I have any empty elements, that would explain the "" I suppose.

It is a Rasp Pi 3.
The install was done quite awhile ago, I believe I just did an install of ES and mame

@mitu said in Migration of retropie libretro Mame 2003 to Mame 2003 plus:

different

yeah... it could be an idea.

@Striderx99 I don't see the point in installing pulseaudio and then disabling it, but RetroPie will use the audio system you have configured in your system - you can install and configure PulseAudio using the Ubuntu package repositories, just like on any other Linux distro.

OK thank you it's still a bit complicated :) why RetroPie has not evolved like Batocera or RetroBat ?

For example:

there are no bezels ? the themes are not complete ? there are no new machines added ?

@mitu great thank you it works :)