Testers wanted: major system upgrade (Pi3b+, KODI 17 and much more ...)

[Gaetan]

@oyyodams My sfc30 pro are pairing and I can map them correctly the first time, no problem.
If i map L2 R2, I can't play any retroarch games, if I map everything but L2 R2, I can play retroarch games.

With my PS3 pad, i had to remap 3 times the pad to have my configuration right. I noticed that i had to map the pad very fast to make it. It's like, if i take to much time to configure it, I will have an axis instead a button in the configuration.
Hope you anderstand this part
Once it's done right, i can use it in game too.
So i confirm, L2 R2 are messing up something with retroarch games

[Choum]

@gaetan Same on 8bit Nes 30 pro L1 R1 is sometime see as axes as L2R2 for SFC 30 pro.

Bluetooth and Wifi problem seems gone for me.

[vdeolive]

Hello,

I confirm. Despite several tries to plug, unplug, remap, forget bt config, remap etc..., connection stil remains lost between ES & Retroarch and this version is not playable with SFC30pro in wireless mode when combined with dongle bt (mine at least) supposed to reduce inputlag.

Let's see on next update.

Thanks

[Choum]

@vdeolive I have absolutely no problem with my SFC30 Pro on the internal Bluetooth of the 3+, as long as you make sure that the R2 L2 are correctly map as buttons and not axe.
I have the 1.29 firmware on the gamepad

[vdeolive]

Hello Choum

And with a bluetooth dongle, it works for you?

I am using it to play with less input lag for game such as Super Mario World of Street fighter II Turbo where timing is essential. You don"t have any input lag on internal BT?

Thanking you

Regards

[Choum]

I don't use a dongle.

I have made some try on SF2 Turbo snes.
with the l2ping command (to see ping time from the gamepad)

Internal Bluetooth with wifi on : 7.75ms
Internal Bluetooth without wifi : 7.99ms
tested during around 140s (2-3 round each)

It seems that the input lag caused by wifi like on previous 3b model are gone on 3b+.

[Gaetan]

@choum your conclusion about lags gone on B+ could deserve to be verified. On the B it was horrible

[Marcos Breviglieri]

Hi, following emulators did not work in the latest beta version:
BLUEMSX - Returns to the menu
FMSX - Stop on a black screen
HATARI - Returns to the menu after error message

EDIT: RPI3 version

[Gaetan]

@choum I could try the bluetooth input lag performance on B and B+, could you tell me how you did to mesure it ?

[Choum]

@gaetan on putty :
hcitool con -> To list gamepad mac adress

You should see somthing like "ACL AA:BB:CC:DD:EE:FF handle 11 state 1 lm MASTER"

Then
l2ping AA:BB:CC:DD:EE:FF
This will run a infinite ping on the gamepad each second.

[Gaetan]

@choum thanx ! Will try this

[simba51]

I am testing this beta version with the new Raspberry Pi 3 A + card, with some update of some files in the Boot.Tout partition working properly as its big brother Rpi 3 B +. WiFi is functional as well as bluetooth with 8Bitdo SFC30 Pro controller.
On the other hand, in spite of the modification in recalbox.conf of:
update = https: //review-507-b*mp-b-0jn0c0-archive-review-prod.recalbox.com
the last update does not start.

[Gaetan]

Hi @simba51 ! It's interesting test. What did you modify in Boot to make it work ?

[simba51]

@gaetan
I replaced the files:
"Bcm2710-rpi-3-b.dtb"
"Bcm2710-rpi-3-b-plus.dtb"
"Bcm2710-rpi-cm3.dtb"
"Bootcode.bin"
"Fixup.dat"
"Start.elf"
by those of the boot of the last update of RASPBIAN "2018-11-13-Raspbian-stretch".
The first 3 files may not be required to replace I think. to test again on new installation.

[Gaetan]

@simba51 Thanx !

[vincent-84]

détail : recalbox manager affiche une mémoire à 495MB.
J'imagine qu'il faut juste actualiser cela.

[Norde]

I've measured internal bluetooth input lag with an Xbox one S gamedpad on both Rpi 3 and 3+*.

I did not notice any difference.
With 100 ping, mean is around 16ms with a min of 14min and a max of 27 in both case.

On the other hand I noticed a difference when I change the driver.
By moving from xpad to xpadneo, input lag goes from a mean of 16ms to a mean of 22ms (min of 19ms and max of 48ms, from 100 ping).

So I guess the difference observed by choum is due to software and not hardware. Have you tried this on a fresh install ?

*The tests were carried out with l2ping command on a blank installation of raspbian lite (last version: 2018-11-13), after a sudo apt-get update upgrade.

[vincent-84]

@vincent-84 said in Testers wanted: major system upgrade (Pi3b+, KODI 17 and much more ...):

détail : recalbox manager affiche une mémoire à 495MB.
J'imagine qu'il faut juste actualiser cela.

Sorry, wrong language :
I said : recalbox manager shows a memory at 495MB.
Seems to be just a small mistake

[wilfrid]

@oyyodams Hello la team et merci pour votre travail !
Je viens de flasher une carte fraiche sur ce nouveau build de beta 2018/11/12 pour tester le wifi. Problème toujours présent pour moi : une fois que je l'active, je sélectionne mon SSID et je tape mon MDP mais impossible de se connecter.
J'ai aussi essayé en mettant directement les infos dans le recalbox.conf mais j'ai le même résultat. Du coup, je suis revenu en cable.

[paradadf]

@vincent-84 no mistake. The rest ist reserved for the GPU.