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

[Substring]

by the way, xu4 and C2 tests are also welcome

[olivierdroid92]

@Substring
Yes with dpad I was able to go back and selecte to correct button assignation. After a while these issue was solved.
Is there a specific duration timer afer we put on a button ? if yes maybe we can increase it.

[Substring]

@olivierdroid92 that's why i ask if it was a trigger or a button. Your prblem loooks like you had triggers, it's a usual problem in ES then whay you've faced, but we never really found a good solution to it yet.

Don't forget to make a support archive once all your pads are reconfigured, i need the pads' new configuration !

[Substring]

@mikozzz wifi does work

[olivierdroid92]

@Substring
Please find archive support on RPI3B+ done just after my wired pad is reconfigured.
Link : https://file.ac/knEKVRNyWV0/
ROMS & BIOS on USB.
No wifi, running on RJ-45
Screen : LCD Samsung
Hope it can helps

[joinski]

Tested the x86_64 image with my Intel NUC D54250WYK and an Original Sony PS3 Controller (Sixaxis Model CECHZC1E).
Installed the image with Etcher on a new/fresh USB 3.0 64GB USB Stick (Sandisk).

Result:
No Sound/Music in EmulationStation Main Menu and the default (out-of-the-box) Controller Mapping is messed up.
By testing/try and error i found out that:
L1 = Up
L2 = Down
Square = Start
Down = Select (SNES B Button)

Went to "Controller Settings", "Configure A Controller" and did the mapping (but within mapping, "L3" was immediately skipped, so i was not able to map L3-Button correctly by pressing the left Thumb-Stick of my PS3-Controller, but all other buttons i was able to map correctly)

Then started SNES Game Classic Kong, but no sound/music and no control possible, no button works (even Hotkey + Start to exit also does not work)

With another PC i started a browser and went to "Recalbox Manager", "Support" and did launch the recalbox-support.sh:
Download URL: https://file.ac/iPisUJahqEE/

Did a reboot through Recalbox Manager, then went to "Sound Settings", "Output Device" and i could choose between:
[0:3] HDA-INTEL - HDA INTEL HDMI + HDMI
[0:7] HDA-INTEL - HDA INTEL HDMI + HDMI
[0:8] HDA-INTEL - HDA INTEL HDMI + HDMI
[0:9] HDA-INTEL - HDA INTEL HDMI + HDMI
[1:0] HDA-INTEL - HDA INTEL PCH + ALC283

I selected the first one and then music in Emulation Station Menu worked.
Then started SNES Classic Kong again. Sound now works, but still no controls possible (had to reboot again through recalbox manager).

After reboot i started Kodi and in Kodi control and sound works

Then tested other Systems (Gameboy, NES) and no control possible
So control in Kodi works but not in Emulators.

[0x77696e]

Maybe something to report:
On rpi3b+, on starts, all is ok, ES feets the whole screen.
Running Kodi from here is ok, all is working great here.
But returning from Kodi to ES crops the screen (all is working, but the resolution is a lot smaller and some parts on the corners are not displayed).
Rebooting ES fixes the bug...

[Substring]

@joinski thank you for the feedback!

Regarding sound, that's not a "bug", the default device may not be the right one on PCs

For your controller stuff, i'm suprised ... Can you make the support archive AFTER returning to the emulator ? You'd need to killall retroarch on SSH. Thank you

[Substring]

@0x77696e can you tell me more about your monitor + support archive ? I haven't experienced such behaviour with Kodi

[joinski]

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

@joinski thank you for the feedback!

Regarding sound, that's not a "bug", the default device may not be the right one on PCs

For your controller stuff, i'm suprised ... Can you make the support archive AFTER returning to the emulator ? You'd need to killall retroarch on SSH. Thank you

You mean while running a Game?
I just started Classic Kong again and while in Game i made the support archive:
https://file.ac/yMlS9BDDl4c/

Then did the "killall retroarch" on SSH and made a support archive again:
https://file.ac/csmWp_fHcug/

Hope this helps

If you need further help/tests, please let me know.

[Substring]

@joinski The second is what I need !

As you have a NUC, does wifi work ?

@abunille you have the same kind of configuration as joinski (NUC + DS3) : do you have the same problems as him ?

[abunille]

@substring

Today im testing a clean install.
The autoconfig PS3 is how @joinski said above, but after remapping i see no errors at the moment.
Testing snes, psx, gamecube, neogeo right now. All ok

Remapping:
Problems with mapping L2 and R2. you have to press the button "only a little bit and keep it back" (quickly).
With L3 or R3 Buttons no problems.

Sound i cant test at the moment.
No Network over Wifi at the moment. troubleshooting in progress

[joinski]

@substring

Did not test wifi yet.
Will do, when i am at home again in the evening (i'm at work right now).

@abunille

What PS3 Controller do you have exactly?
I have several Original Sony Sixaxis and DualShock3 Controllers.
Will do a clean/fresh install later and test my other PS3-Controllers.
I also have Original MS Xbox360 Controllers and can test them also.
And i have an 8bitdo SF30 Bluetooth Controller, which i will test also.

[Substring]

@joinski oh do triggers get mapped like axis ? If yes, i'll try to have a look at drivers and see if i can hack them to be turned into buttons (just like with xbox360).

Anyway, if you failed a mapping, use the dpad to move up and remap (this is explained at the top ofnthe window)

[abunille]

@joinski

DS3 CECHZC2E (A1)

[Gaetan]

@Substring Here are the things I found :

(Raspberry Pi 3b+ , fresh install, Sandisk SD, genuine PS3 controller)

• When configuring the pad the first time, L2 was Axis 6. Then i remapped it and it work normaly.

• I don't know if it was before, but when I hash the roms, it stops when ES enter in sleeping mode (5 minutes)

• I rejoined a netplay game that is showing a blue indication, the first time it goes back to ES then black screen :
  https://file.ac/qbv8ww0rJmU/
  then hotkey+start, goes back to ES and black screen again :
  https://file.ac/eMqUMrt6MYI/
  At this point I had to restart the Pi

The second time, I rejoined a netplay game that is showing a blue indication, black screen again :
https://file.ac/9hjkC3STM3s/
then hotkey+start, goes back to ES and black screen again :
https://file.ac/N7mWm5OshwA/
At this point I had to restart the Pi

• I did test lightgun on B+ and it's working like on regular B

• Also, I notice that there is no improvement with 3d games, I'm not waiting for miracles that the xu4 can't even do, but it seems to me that it's even running slower than my regular B at 1300mhz.
  B+ is 1400mhz right ? So it should be at least the same.
  Tested on difficult games to run like Tekken 6 and Gods of War on PSP (I know they can't run well, but they are good for testing)
  The worst was Dead Or Alive on Dreamcast, it was clearly slower and had a strange behaviour. The time for fights is set to O secondes, so impossible to play (Time Up immediatly)

[Substring]

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

@Substring Here are the things I found :

(Raspberry Pi 3b+ , fresh install, Sandisk SD, genuine PS3 controller)

• When configuring the pad the first time, L2 was Axis 6. Then i remapped it and it work normaly.

Already reported by joinski and abunille, see my previous comment

• I don't know if it was before, but when I hash the roms, it stops when ES enter in sleeping mode (5 minutes)

I tjink this was the case before. I don't think it stops, just the screen is frozen. Why do you believe the hasing process is frozen ?

• I rejoined a netplay game that is showing a blue indication, the first time it goes back to ES then black screen :
  https://file.ac/qbv8ww0rJmU/
  then hotkey+start, goes back to ES and black screen again :
  https://file.ac/eMqUMrt6MYI/
  At this point I had to restart the Pi

The second time, I rejoined a netplay game that is showing a blue indication, black screen again :
https://file.ac/9hjkC3STM3s/
then hotkey+start, goes back to ES and black screen again :
https://file.ac/N7mWm5OshwA/
At this point I had to restart the Pi

I'll read the logs back home

• I did test lightgun on B+ and it's working like on regular B

• Also, I notice that there is no improvement with 3d games, I'm not waiting for miracles that the xu4 can't even do, but it seems to me that it's even running slower than my regular B at 1300mhz.
  B+ is 1400mhz right ? So it should be at least the same.
  Tested on difficult games to run like Tekken 6 and Gods of War on PSP (I know they can't run well, but they are good for testing)
  The worst was Dead Or Alive on Dreamcast, it was clearly slower and had a strange behaviour. The time for fights is set to O secondes, so impossible to play (Time Up immediatly)

3D games are a mix of CPU and GPU. Hard to tell which one is more efficient than the other. But slow fba games like killing blade should run a little better (even the PGM logo at boot doesn't run at full speed). Anything arcade is 99% CPU dependant

[Gaetan]

@substring Yes, for the hash it maybe just frozen screen but I can't say.
Juste made a few Netplay tests, I was playing with Lionsquall and it was difficult to connect, it seems that the snes cores are not b*mped as the regular B

[Substring]

@gaetan no core b*mped, but different kernel

Pi3 is 1.2GHz vs 1.4GHz pi3b+

[Gaetan]

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

@gaetan no core b*mped, but different kernel

So it could be the reason of the core errors ? Will you b*mp it in a beta update ?

Pi3 is 1.2GHz vs 1.4GHz pi3b+

Yes, I this I know, but it seems that my Pi3 overclocked at 1.3GHz run faster that the piB+ at 1.4GHz, I will investigate

Also, I got a black screen when refreshing the gamelist, after adding sms roms :
https://file.ac/BMeNICzzry8/

and return to gamelist after launching a PSP game (certainly the same issue as with the regular B) :
https://file.ac/SXwJ5mxsk7A/