@myst Seems you always have a solution Works perfectly!
Core didn't have to be changed for segacd/sega32, just had to add extensions.
Thank you!

@mYSt as always, works fine! thx

Would be good to know, anybody already tested?

Most important question to me:
Is the known Bluetooth controller lag of Pi 3 gone with this new model?

Hi guys,

As I've tried everything I found at the forum and also Google, I have to ask for your help and experiences:

My 8Bitdo SF30 PRO works like a charm after pairing, but when I reboot Recalbox, it will not connect with my Pi anymore. Sometimes already after first reboot, sometimes after 10 reboots.
I have to delete all bluetooth configuration and pair it again when this happens. I use "forget all bluetooth controllers" in EmulationStation and also delete the tar-file where paired bluetooth devices are stored, that's the only way that allows me pairing this controller again.

I'm using latest stable version of Recalbox.

I've tried almost everything:

• Tried internal bluetooth (instead of dongle with CSR bluetooth chipset)
• Paired controller both in Switch- and Android-Mode, where controller seem to work fine (Windows and Mac modes seem to have issues, in Windows-mode L2-R2 buttons won't work, in Mac-mode no button, stick and d-pad will work at all).
• Paired using shell (bluetoothctl) - Pairing worked, but same issue afterwards
• Switch controller on only when EmulationStation is loaded already
• Did a complete fresh install of latest Recalbox stable

I can exclude any hardware issue on Pi-side, because I have paired many bluetooth devices and none of them has this problem (8Bitdo N30 PRO controller, Playstation 4 controller, Logitech keyboard, Microsoft mouse)

Because of 8Bitdo SF30 PRO is the best controller I've ever tried for retro gaming, I would appreciate if you have a hint or solution for me!

Thanks to all in advance!

Hi, this theme is great!! If you have time left, I'd be very happy when you could add following systems:

• coleco
• dos
• dreamcast
• fba_libretro
• fds
• pcenginecd
• psp
• sg1000

Thanks

Here screenshots what happens exactly:

Gamelist BEFORE I run the game (for example tetris & dr. mario, snes):

AFTERWARDS (after restarting emulationstation and es has written <lastplayed> data, hash is messed up. same with super mario kart, see below):

Really strange thing....

@scavy
Hi, thanks for answer, but it's exactly the way I tried (next to other ways I described):

"Android-Mode" = "d-input" = Start+B

And I also know that I have to switch off the gamepad and switch it on again when I reboot - Same way I do it with my other working 8Bitdo pad, the (older) 8Bitdo N30 PRO!

My problem is, that the pad just does NOT connect anymore after reboot, even though I switch it off and on again, stay in mode "d-input" and even don't connect it to other devices, just to Pi/Recalbox. First LED keeps flashing instead of staying just on and no shock feedback as usual.

Maybe you have another idea? If it works on your side, maybe I got a defective one... I've already sent it back to Amazon, in the meanwhile. Maybe I'll give it another try with a new one...

Very exciting changes in last releases, I'm following development of this theme continuously
Unfortunately, due to a lack of time, I currently can't install new version. Looking forward to final new RB version, then I'll go for install of latest Next Pixel version too.
Also curious about your suggestion switching Pi to 720p mode, can't wait to try
Thanks again for your work!

@foxzflow
CSL should use CSR chipset, I‘m using the same! Before I tried a Digitus dongle, also CSR. As it didn‘t fit in Superpi case because of its size, I removed housing of both and both modules look quite similiar, just the CSL has a very bright LED compared to the Digitus Also MAC adress tells me it‘s from the same Chinese manufacturer.

I also tried an Asus dongle with Broadcom chipset, but here I had same problem like with Pi3 B‘s internal Broadcom chipset: Inputs where much too sensitive, for example at steering at Mario Kart.

But as discussed, also tried with internal Broadcom chipset of Pi3 B+ in beta and there it seems work fine. (Not too sensitive and also no known input lag of Pi3 B)
So I hope there is a final version for B+ soon too. I‘m really looking forward because for me there is no real alternative to the really good, new 8bitdo controllers!

Hi,

I'd like to add cummulate games in each one folder/system as follows:

Folder/system "megadrive":

• Sega Megadrive games (.gen, .md,... files)
• Sega Mega-CD games (.bin, . cue,... files)
• Sega 32x games (.32x files)

Folder/system "pcengine":

• PC Engine games (.pce files)
• PC Engine CD games (.bin, . cue,... files)
• SuperGrafx games (.pce files)

The reason I want to do this is that the theme I use needs too much RAM on Pi, if I activate too many systems. So I had to remove some systems to make ES running smoothly again.
And as Mega-CD, 32x, PC Engine CD, etc. are only addons of main consoles, my idea was to cummulate them in these 2 "main systems" written above and solve the problem this way.

It seems that emulator is the same for both systems and its sub-systems (add-ons), but I guess my plan won't work without any modification? Just tried SuperGrafx yet because of same file extension - this seems to work in folder "pcegine" though!

Thanks for your help!

@Akkeoss Sorry, posted too quickly. There's a new section "GPU Plugin" in settings, found it there. Thank you very much for the update!

@Akkeoss Hi, I've updated from RB 8.1.1 to 9.0 an still can't find the option (again). Has there gone something wrong? Thanks

@tobiwan_1984
I've found a workaround, at least partially... If you press both L2 and R2 button, after loading the game, it will work. But sometimes there occurs a malfunction that enables a shader.

@lhari84
Some more details, in my case it's a SF30 Pro, with latest firmware released for it, 1.34.
Futher, it's set to Android mode (like recommended?)

@tobiwan_1984
Hi, I got same issue. In my case I recognized that when I configure the controller, Buttons R2 and L2 are recognized as "Axis" and not "Buttons". So I exluded them for testing and afterwards it worked.

Anyway, I would like to use these controllers including L2+R2 buttons. In the past they worked, but I can't remember if recognized as "Axis" or "Buttons". Hope the Recalbox Team has a solution for it.

@karlo8321 To get rid of my BT problem - too low BT range with Pi 4B and/or RB 8 - I've tried 3 different USB BT dongles that worked fine in past with Pi 3B. None of them is working at all with Pi 4B and/or RB 8. Not any bluetooth device is found, as soon I connect one of these dongles.

I hope it's just a software issue, as I would prefer using the interneral BT of Pi 4B anyway. I've never had a range issue in the long past, just used BT dongles with Pi3 B (non +) because of the bad latency. With Pi 3B+ everything was fine. I switched to RB 8.0.x in parallel with the switch to Pi 4B, so I can't tell if hardware (Pi 4B) or software (RB 8.0.x) causes the range issue. Anyway, the fact that my USB dongles do not work at all should be caused by software.

@zing said in Pi 4 Bluetooth controller range issue:

Are your dongles on the compatibility list?
https://wiki.recalbox.com/en/hardware-compatibility/compatible-devices/usb-dongles

Not at all, only the "Asus USB-BT400 Bluetooth 4.0". But even though the green checkmark, there is note "Works with customizations to the Broadcom firmware - doesn't work from stock." - So it really may not work out of the box.

Anyway, I have two dongles with CSR-chipset, one from deleyCON, one from tinxi, which worked perfectly in Recalbox versions about 2-3 years ago, even though they are not on list.
I'm sure this is because they are using the same chipset as other dongles that can be found on the list, for example the Digitus:
https://shop.okluge.de/digitus-bluetooth-4.0-tiny-usb-adapter-class-2-csr-chipsatz-bluetoothstick-stick.html

Best solution would be if it's really a bug and I don't even need a dongle as a workaround at all
My current workaround is to use the 8Bitdo SF30 Pro only, as it provides a larger range then the other ones for any reason (not as large as before with Pi 3B+ and RB 7.2.2., but sufficient for my needs).

@zing
This seem to be other issues. My main problem is just the low range. If I'm close enough (too close for my needs), everything works as it should.

Anyway, I also could not pair a Logitech keyboard. No PIN request at all - so no pairing. In the past (about 2 years ago), it worked by connecting by SSH while pairing process. There the PIN was shown up and could be entered on keyboard and confirmed by return. Currently nothing appears in CLI.

Another experience I've made:
No external bluetooth dongle seem to work: I have 4 different BT 4.0 dongles with 3 different chipsets. In Pi 3B (no +) times, where internal BT was very crappy, it was enough to connect the dongle and it worked. Now, not any controller is found in pairing mode when any dongle is connected to USB port.
I've tried to use one of the dongles as a workaround for my range issue.

Thanks for your answer anyway.

Found some hint that USB 3 can cause issues and plugged SSD into USB 2 Port. It made things better but it's still not like it used to be with Pi 3. It's so annoying when a new piece of hardware only makes troubles

Hi,

I got another issue with my new Pi 4 & NesPi 4 Case & Recalbox 8.0.2 setup:
Today I've paired all of my Bluetooth controllers:

• Sony DualShock 4 (v2)
• 8Bitdo N30 Pro (v1)
• 8Bitdo SF30 Pro

Now the problem is that first 2 have only a range of about 1,5 meters, maximum!!
The 3rd one (SF30 Pro) offers a normal range, it works without issues in the whole room.

With my Pi 3 B+ & SuperPi Case & Recalbox 7.2.2 setup, I didn't have this issue with this same set of controllers.
Further, I have completely reinstalled Recalbox 8.0.2 and also tried both bluetooth drivers. I'm out of ideas why this happens. Are there any known issues with RB 8.0.2 / Pi 4 regarding that?

Thanks for your help!