Recalbox 6.0 RC2 is released

[OyyoDams]

@gustavolima I've just tested on a fresh install and I can confirm you Kodi works on this version.

[SeatFreak]

I installed on my Raspberry Pi 3b+ RecalBox 6.0RC1, then upgraded to 6.0RC2, since then Kodi has stopped working. When I start Kodi everything is still normal, but when the Kodi main page comes, the mouse pointer is in the corner on the top left and everything is frozen. I also have the problem that when I start the Raspberry Pi 3b+, not equal to the network is there, must first enable and disable Wi-Fi until then until sometime the WLAN works. Router is FritzBox 7490.

[acris]

Hello @SeatFreak
Have you reconfigure gamepad ?

[SeatFreak]

Hello acris

No, I did not have that. Do I have to do this after every update?
Thanks for the tip, I tried it right away.
Kodi works now again, after reconfigure the Gamepad.

many thanks.

[lhari84]

@seatfreak said in Recalbox 6.0 RC2 is released:

I also have the problem that when I start the Raspberry Pi 3b+, not equal to the network is there, must first enable and disable Wi-Fi until then until sometime the WLAN works. Router is FritzBox 7490.

Regarding wifi, set wifi region to DE in recalbox.conf (or FR, or AT; just something european, instead of US).

Also had same issue with my FritzBox. I can‘t understand why this is set to US by default. A developer told me it‘s to be complient in US, because they use less channels/frequecies. But many users have these problems and don‘t know what to do. I would set European setting as default, as it‘s European software. If US citizens use it, they can change if necessary. Just my point of view...

[SeatFreak]

Yesterday I followed the tip to reconfigure the controller then Kodi went again,
but after a recalbox restart and game list update in the options,
after Kodi was frozen again.

[lhari84]

@OyyoDams Hi, since version 6.0 I got some warnings about invalid CRC in es_log.txt. No big deal, but would be interesting where these come from. Examples:

[2019/04/03 00:31:48.413] (WARN!) : Invalid CRC32 FD7B1BE33ath
[2019/04/03 00:31:48.414] (WARN!) : Invalid CRC32 FE43FE586ath
[2019/04/03 00:31:48.414] (WARN!) : Invalid CRC32 02FAD2B66ath
[2019/04/03 00:31:48.415] (WARN!) : Invalid CRC32 FA8DF0BA3ath
[2019/04/03 00:31:48.415] (WARN!) : Invalid CRC32 FF9ED9819ath

Thanks for all the work you guys do, version 6.0 RC2 is working very well here on Pi3 B+!

[Bkg2k]

@lhari84 check the corresponding gamelist.xml file.
What did you use to generate those CRC? An external scraper? The internal ES tool?

[lhari84]

@bkg2k Hi, I used external scraping tool (Skraper). Afterwards I run internal solution in netplay-section.

[lhari84]

I want to report another minor issue:
I wanted to compress pcengine and sega cd roms (bin/cue) and used a tool named chdman to create chd-files.
Now pcengine is working fine with those chd-files, but sega cd only runs into a black screen for about 10 seconds and quits to ES then. (Of course i tried the old bin/cue rom before compression and it worked too)

I used tool version from this manual. Maybe I have to use another version? Or is it a bug in sega cd's chd support?

https://www.reddit.com/r/RetroPie/comments/72kh6q/stepbystep_guide_how_to_convert_sega_cd_or_pc/

(I know it's a manual for retropie, but I guess emulator is the same and for pcengine it appearantly works in recalbox)

[lhari84]

Three more findings:

recalbox.conf
I have already read about from other user during beta phase and don't know if it should be fixed in meanwhile:
When enabling (uncommenting) power/reset switches on Pi 3B+' GPIO, in my case line with "PIN356ONOFFRESET", the same entry appears many times (all uncommented) in recalbox.conf. Seems that all other (still commented) entries are replaced by any reason:

------------ A - System Options -----------
Uncomment the system.power.switch you use
system.power.switch=PIN356ONOFFRESET # https://github.com/recalbox/recalbox-os/wiki/Add-a-start-stop-button-to-your-recalbox-(EN)
system.power.switch=PIN356ONOFFRESET # https://github.com/recalbox/recalbox-os/wiki/Add-a-start-stop-button-to-your-recalbox-(EN)
system.power.switch=PIN356ONOFFRESET # https://github.com/recalbox/recalbox-os/wiki/Add-a-start-stop-button-to-your-recalbox-(EN)
system.power.switch=PIN356ONOFFRESET # https://github.com/recalbox/recalbox-os/wiki/Add-a-start-stop-button-to-your-recalbox-(EN)
system.power.switch=PIN356ONOFFRESET # https://github.com/recalbox/recalbox-os/wiki/Add-a-start-stop-button-to-your-recalbox-(EN)
system.power.switch=PIN356ONOFFRESET # https://github.com/recalbox/recalbox-os/wiki/Add-a-start-stop-button-to-your-recalbox-(EN)
system.power.switch=PIN356ONOFFRESET # https://github.com/recalbox/recalbox-os/wiki/Add-a-start-stop-button-to-your-recalbox-(EN)
system.power.switch=PIN356ONOFFRESET # https://github.com/recalbox/recalbox-os/wiki/Add-a-start-stop-button-to-your-recalbox-(EN)
system.power.switch=PIN356ONOFFRESET # https://github.com/recalbox/recalbox-os/wiki/Add-a-start-stop-button-to-your-recalbox-(EN)

es_log.txt

Here appears an error saying config file missing. + systems are listed double-named like "3do3do".

2019/04/04 00:20:15.340] (ERROR) : /recalbox/share/system/.emulationstation/es_systems.cfg file does not exist!
[2019/04/04 00:20:15.340] (INFO ) : Loading system config files /recalbox/share_init/system/.emulationstation/es_systems.cfg...
[2019/04/04 00:20:15.349] (WARN!) : Key: 3do3do
[2019/04/04 00:20:15.350] (WARN!) : Key: amiga1200amiga
[2019/04/04 00:20:15.350] (WARN!) : Key: amiga600amiga
[2019/04/04 00:20:15.350] (WARN!) : Key: amigacd32amiga
....and so on....

[lhari84]

@bkg2k said in Recalbox 6.0 RC2 is released:

@lhari84 check the corresponding gamelist.xml file.
What did you use to generate those CRC? An external scraper? The internal ES tool?

Sorry for this one, should have opened my eyes before.
Indeed there was text "ath" in the end of the hash. Must have come form Skraper (Screenscraper) I guess...

Maybe you can have a short look on the other issues I found above.

Thanks for your support!

[Bkg2k]

@lhari84 don't worry about such "errors", that's normal, and we'll remove thos logs in the next release.

[lhari84]

@bkg2k ok regarding error messages

But do you have an idea why sega cd isn't working with chd files made from bin/cue roms that work perfectly, though?
Readme says .chd is supported and pcengine cd chd files converted the same way from bin/cue work fine!
I don't know if chd support is new in 6.0 or if it was implemented before. I just can say I don't manage to get it working without a visible reason...

[paradadf]

@lhari84 check if changing the core allows you to launch segacd in chd format. It might be that the default core doesn’t support chd, but the other does.

[lhari84]

@paradadf
I've tried already tried switching to genesis plusgx yesterday, no success.
But it's a good hint, appearantly it only works with genesis plusgx core and that's the point. It seems this core needs other bios files (or at least renamed ones), than picodrive core:
https://github.com/RetroPie/RetroPie-Setup/wiki/Sega-CD
I guess I have to approach from this side.
I'll try when I'm at home and report when I get it working.

[abunille]

@lhari84

Yep, only Genesis Plus GX support .chd extensions.
For both Emulators you need following name convention:

bios_CD_E.bin for Europe Region
bios_CD_U.binfor USA Region
bios_CD_J.binfor Japan Region

Just rename your old Bios filenames to work on both Cores.
(example: eu_mcd2_9306.bin -> bios_CD_E.bin)

[acris]

Hello
this bug has been fixed for the next version.
https://gitlab.com/recalbox/recalbox/merge_requests/561

[paradadf]

@abunille nice seeing you around buddy. Prepare for the stable!!!

[lhari84]

@abunille said in Recalbox 6.0 RC2 is released:

@lhari84

Yep, only Genesis Plus GX support .chd extensions.
For both Emulators you need following name convention:

bios_CD_E.bin for Europe Region
bios_CD_U.binfor USA Region
bios_CD_J.binfor Japan Region

Just rename your old Bios filenames to work on both Cores.
(example: eu_mcd2_9306.bin -> bios_CD_E.bin)

Yeah, this worked, thanks!