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

[vdeolive]

Hello,

Fresh installation of 11/12/2018 beta with the p3+ link yesterday. I am using recalbox on sd card 16go and usb key sandisk256go / system parameter on any external source.

1. virtual keyboard to fullfill wifi key does not appears.
   Impossible to set the wifi without keyboard.

2. kintaro ursus scripts to pilot safe stop + reset button + fans not integrated

So far, emulation is ok. Extrem overclock 1500mhz works.
Still testing.

Thank you guys for your hardwork and dedication in making us happy.

Regards

[vdeolive]

3. Gamepad loss while entering in retroarch. The gamepad (sfc30pro) works on emulation station interface but the inputs are not communicated to retroarch. You have to reinitiate the system manually

[OyyoDams]

@vdeolive about the virtual keyboard: known issue, just go back and enter again, the virtual keyboard will appear.

I've played with a sf30pro yesterday on the latest build without any issue. Be sure to reconfigure the mapping.

[mi7chy]

Thanks for the 11/12/2018 update. These are the issues I've run into so far:

• Controller setup glitches with genuine Sony PS3 six axis controller once you get to the trigger buttons. It's working fine in the stable release and one of the reasons I switched to Recalbox.

• Atari ST .ipf images in compressed .zip still no longer work and just return to menu like with previous test versions. Stable version works fine.

[mi7chy]

Added some additional roms and after updating game list through Start menu it's been stuck at "PLEASE WAIT" on Recalbox Emulation Station white screen. Can ping the IP but can no longer SSH into it to do proper restart. Updated from stable release 18.07.13.

[Guy Don]

Hi !
I'm using recalbox rpi3 12/11/2018 beta (4ad393af) on a Rpi3B+,
OS is runing, but can't launch any game ( game build in ) . Black screen and go back menu.
Kodi not running black screen ...

[OldGreg]

@guy-don : Have you remap your gamepad after upgrade ? It's the solution, most of the time...

[vdeolive]

Hello,

To be more precise i am playing with bluetooth dongle (i've bought the recommanded one on your shop) in order to reduce input lag. Sfc30pro is updated on last firmware from 8bitdo.

The sfc30pro is recognised and i can configure it.
It works on emulation station but when you enter retroarch, pad is not recognised anymore. I have tried several times to forgot the pad and reconfigure it but still same issue. Pad connected with cable works.
Only with bt, gamepad is lost on retroarch.

Any idea?

Thanks

[OyyoDams]

@vdeolive my latest test was with internal BT of the B+. I'll make a test with the BT dongle and check if it works.

[vincent-84]

@OyyoDams

For me, the new version of the beta doesn't solve the bluetooth pad (SF30pro, fireware updated) issues, without dongle :
_ deconnexion from ES to retroarch. Sometimes, waiting several minute allow the reconnexion of the pad.
_ some L2/R2 issues

remapping the pad doesn't solve the problem, but USB-C connexion does.

Maybe "retroarch input driver" in config could solve this issue ?

[Jesper Ammitzbøll]

Thanks for the update. wondering if HDMI to dvi is fully implemented, coz i tested on my old 19" 4/3 screen, and it just vent black. tested on my newer 24" also over dvi, no problem there.

[Jesper Ammitzbøll]

@jesper-ammitzbøll said in Testers wanted: major system upgrade (Pi3b+, KODI 17 and much more ...):

Thanks for the update. wondering if HDMI to dvi is fully implemented, coz i tested on my old 19" 4/3 screen, and it just vent black. tested on my newer 24" also over dvi, no problem there.

After some more testing. im only able to boot up on the 19" with

hdmi_group=2
hdmi_mode=4

[DVI DMT (4) RGB full 4:3], 640x480 @ 60.00Hz, progressive

[vincent-84]

@OyyoDams

I tried the overlock using Extrem mode.

Recalbox OS (not only ES) crash after several second each time (and I need to make an "hard restart" by unplug my Pi).

[Gaetan]

@vincent-84 I use extrem too and everything is fine. I guess it depend on some boards that can support better oc than others

[Bkg2k]

That's why there is a Warning when you select Turbo/Extrem O/C.
There are many Pi manufacturers and they have all different quality checks. Some chineese manufacturers have no QC at all.

When playing with O/C options, I highly recommend to put a good cooling system (at least a large heatsink).
Sarting immediately with the Extrem mode is not a good idea. Start with the "High" mode, check if everything is fine, then try the next level and so on...

[vincent-84]

@bkg2k you're wright : that was an heat issue (solved by opening my superpi case and use and external fan for test).
I had to add some direct fan on the pi (and change my case).

[Gaetan]

@vincent-84 you can see the temperature with the webmanager, over 80 degres your pi will become instable. I have my B+ in a snespi case with heatsinks and fan, lt's oc at 1500 and it's 60 degres.

[GrigaNyasha]

I have the latest version of RecalBox Beta and Raspberry Pi 3B+

I do not know how to make remount partitions as RW:
@substring said in Testers wanted: major system upgrade (Pi3b+, KODI 17 and much more ...):

• know the very basics of Linux:
  • remount partitions as RW

So most errors are likely because of this.
The following errors I noticed:

• After adding the game to favorites and shutting down, it freezes on a black screen (below the build number)
• In Locoroco (psp), the videos do not work, the sound goes. However, the game itself is going well!
• After the reboot, wifi does not work, you have to write the password again. It feels like he can not decipher the key.
• YouTube is not working in KODI
• Saved to PSP did not work, but after installing assets in configs it worked
• WinSCP error: Incoming packet was garbled on decryption w/ winscp (FileZilla works great)

[vincent-84]

@Gaetan thanks for the tip, I didn't know that (good) tool.
Last crash (with case close) doesn't see any anormal temperature, have to try again.
Maybe I was just lucky during my test with open case....

What is the main objective of the "step by step OC" ? Seeking the maximum value of the OC for each pi or try to stabilized the OCing mode ?

P.S.: my objective (and test) : running goldeneye64 (it seems to work but only at 1500).

[OyyoDams]

A bug has been identified with some pads (8bitdo for example), making them work in Emulation Station but not in Retroarch emulators. We're working on fixing it, but here is a "quick fix" as a workaround:

1. Restart the pad mapping
2. Check before saving, and be sure L1R1 / L2R2 / L3R3 buttons are NOT recognized as "AXIS".
   Here it's wrong for L2R2:
   
3. If needed, remap these buttons:
   

Then your pad should work