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

[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/

[PapaTriman]

installé à l'instant sur un bartop, sticks et boutons branchés sur les gpio. J'ai activé les gpio sur recalbox.conf, mais je ne parviens pas à mapper les controles dans ES.

[0x77696e]

@substring I'm using an Artlii (video projector) with prefered mode "mode 39: 1360x768 @ 60Hz 16:9, clock:85MHz progressive"/DMT but it also supports 1080p/CEA
I dont understand why it fails when returning from Kodi but not if I restart ES from command line or at first boot.
For the tests I am using the archive listed on top of the topic (the wetransfer one).

[Substring]

@papatriman english please support archive too please

[Thomas Kings 0]

https://i.imgur.com/oS4wCXX.jpg

I don't understand this step
do I have to change updates.type=stable to one of these links?

[MikaXII]

@thomas-kings-0

You need to edit your recalbox.conf and set updates.type to:
First update with: https://review-master-slwsz0-archive-review-prod.recalbox.com
Then update with https://review-507-b*mp-b-0jn0c0-archive-review-prod.recalbox.com

So first update with updates.type=https://review-master-slwsz0-archive-review-prod.recalbox.com
When the first update is complete, make a new one whith this link
updates.type= https://review-507-b*mp-b-0jn0c0-archive-review-prod.recalbox.com

[PapaTriman]

@substring ok

So i used to install it on a bartop. I usually use retropie on it, with gpio controllers.
I activate the gpio driver on recalbox.conf but non mapping possible on Émulation Station.

Are there any change in the gpio connexions?

(Sorry for the Bad english level )

[Substring]

@papatriman yep, major upgrade on the gpio driver, but it's supposed to work as before. I'll take a look in the next days. Don't forget ypur support archive please

[joinski]

I did the remapping of the Controller again (this time i was able to map L3 correctly by navigating up and repeat until the right button was recognized), and now control in Games is possible!

Did also test Wifi, but with no success.
I enabled Wifi first, then went to WIFI SSID and there is no WIFI recognized.
When i go to "Manual Input", then the window with the letters seems to be cut. You can not see every letter.
Here a Picture:
https://abload.de/img/img_54852seys.jpg

I was able to enter the SSID and password anyway (if you move the cursor to the hidden area, you still know which letter is currently highlighted, because it is shown below).

But it did not connect. Maybe the Wifi-Card from the NUC is not recognized/compatible.

Support Archive:
https://file.ac/Bn0LdEaqNL4/