@wizardling Shucks, I'm blushing here. But seriously no problem at all, just browsing the forum and saw your post and noticed you were using apt and was aware it sometimes can cause issues like this.
The "problem" is that Linux will do exactly what you tell it to do and if you aren't fully versed in exactly how things work it can cause problems. I honestly couldn't tell you why it works, other than it handles installation of packages and dependencies differently.

@jonceramic said in Disconnected bluetooth controller causes freezes on regular intervals:

I'm assuming possible that the controller needs to be on when the system is booted under this setup so it can be discovered immediately

That's not necessary, if the pairing is ok, you can turn your controller on/off anytime. You didn't give any details about your system/controller, so it's hard to say if it's the same problem or not.
FWIW I have a 8bitdo SN30 controller that doesn't have any problems. It was updated to the latest firmware version available and I didn't have to fiddle with any bluetooth settings on the PI, it even goes into stand-by then reconnects back on a button press.

Just wondering if you ever figured this problem out? I too am having the same problem. It worked fine for a while, then it just stopped working. I'm not sure what changed to cause it.

@hex sorry - as you probably already figured out I messed up the fake code conditions. I think it should likely be

Velocity == 0 and (NOT using VLC OR NOT in gamelist view)

But you know how PS works better than I do, so definitely don't trust me on this and check if it makes sense. :)

@hex Hi sorry for the delay ... i don't know what was update but i don't have any crash from more than 15 days now !
I think it is ok.
I have update to Retropie 4.3 yesterday, i will try it too.

@joshbgosh10592 the script is just the one that runs mupen64plus in retropie -you're already using it :) i was just showing how it forces the show fps stuff, if you're running GLideN64. i can't see how you'd avoid it.

@hermit Looks like if you launch and exit the pixel desktop it fixes the issue. I'll try to find another workaround.

I've reported the issue, so hopefully we'll have a solution soon. We are starting to run out of memory when compiling.

@Hex Glad to hear it works as an option :)

Thanks for putting this together, and thank you for helping with the testing!

I'm bumping this because I found a solution. It's not the best possible thing to do but seems to have solved my issue.

I edited my .cfg file on /opt/retropie/configs/all/retroarch/autoconfig and added

input_l_y_minus_axis = "-1"
input_l_x_plus_axis = "+0"
input_l_y_plus_axis = "+1"
input_l_x_minus_axis = "-0"

in order to set the digital inputs as analogue (in addition to keeping them as analogue too).

It appears that the current fba core accepts only analogue (thumb)stick inputs for arcade machines that used analogue hardware such as wheels, joysticks, pedals, etc, something that wasn't a case previously and still isn't on MAME.

For anyone having the same problem (and doesn't use analogue sticks) this seems to be the only solution currently but I'm not sure if this will interfere with anything else.

Just to add a bit of info, I had this problem and @herb_fargus helped me fix it by telling me to try the enable/disable (which worked well). Thanks @buzz and @herb_fargus!

Link to my post in case there's any useful info there: https://retropie.org.uk/forum/topic/12750/01_retropie_copyroms-seems-broken-won-t-sync-bios-and-configs

Did you use the official 4.2 image from the site? Did you read about the info you should post? It's not requested just for the craic. Help us to help you...

@Spectreman I agree that the white screen bug is not fixed, however it has been improved immensely. The performance after the upgrade was significant, so I would consider it a major performance upgrade, but not necessarily a fix. More work still needs to be done for sure, but there are a lot of cool projects going on right now as well. You should be able to run trokyfran on a Pi3 with standard configs with 14 systems without an issue. I would again try to adjust your VRAM up or down in small amounts. Maybe 120 or 80 would work. You never shared what pi model you are running, power supply, do you have any modifications to your settings? Have you changed your gpu settings? Overclocked?

@StormJH1 Hi! Yeah, it was the most recent update. I'm pretty sure I was connected to the internet, and even if I wasn't, the scraper shouldn't crash emulationstation like it is right now. :P I'm just glad sselph's works, but I still find it strange the scraping functions inside ES crash it completely.

@pjft Thanks, but once again you were major help! You pointed me right to I needed to be and I just pushed a few buttons.

I was actually just about to post when you replied.

I decided to just read through the man page and found that the syntax that the GitHub repo suggests, while works in some cases, was incorrect. At least in that it didn't work for me, I ended up using:

$user $machinename = NOPSSWD : ALL

Thanks for the help! Guess I should have just read that in the first place before asking.

@joaovlg map the c controls to your right analog (-2, +2, -3, +3)