[4.1-Unstable] Bug reports

[Substring]

@grgohr @peterpan123123 Guyz could you paste the resultat of sdl2-jstest -lplease ? Regarding your PSP problems

[peterpan123123]

@Substring What the... Not easy to post and not getting a spam warning:-(

"Found 4 joystick(s)

Joystick Name: 'Xin-Mo Xin-Mo Dual Arcade'
Joystick Path: '/dev/input/event0'
Joystick GUID: 03000000c0160000e105000001010000
Joystick Number: 0
Number of Axes: 2
Number of Buttons: 10
Number of Hats: 0
Number of B***s: 0
GameController:
not a gamepad
Axis code 0: 0
Axis code 1: 1
Button code 0: 288
Button code 1: 289
Button code 2: 290
Button code 3: 291
Button code 4: 292
Button code 5: 293
Button code 6: 294
Button code 7: 295
Button code 8: 296
Button code 9: 297

Joystick Name: 'Xin-Mo Xin-Mo Dual Arcade'
Joystick Path: '/dev/input/event1'
Joystick GUID: 03000000c0160000e105000001010000
Joystick Number: 1
Number of Axes: 2
Number of Buttons: 12
Number of Hats: 0
Number of B***s: 0
GameController:
not a gamepad
Axis code 0: 0
Axis code 1: 1
Button code 0: 288
Button code 1: 289
Button code 2: 290
Button code 3: 291
Button code 4: 292
Button code 5: 293
Button code 6: 294
Button code 7: 295
Button code 8: 296
Button code 9: 297
Button code 10: 298
Button code 11: 299

Joystick Name: 'DragonRise Inc. Generic USB Joystick '
Joystick Path: '/dev/input/event2'
Joystick GUID: 03000000790000000600000010010000
Joystick Number: 2
Number of Axes: 5
Number of Buttons: 12
Number of Hats: 1
Number of B***s: 0
GameController:
not a gamepad
Axis code 0: 0
Axis code 1: 1
Axis code 2: 2
Axis code 3: 3
Axis code 4: 4
Button code 0: 288
Button code 1: 289
Button code 2: 290
Button code 3: 291
Button code 4: 292
Button code 5: 293
Button code 6: 294
Button code 7: 295
Button code 8: 296
Button code 9: 297
Button code 10: 298
Button code 11: 299
Hat code 0: 16

Joystick Name: 'DragonRise Inc. Generic USB Joystick '
Joystick Path: '/dev/input/event3'
Joystick GUID: 03000000790000000600000010010000
Joystick Number: 3
Number of Axes: 5
Number of Buttons: 12
Number of Hats: 1
Number of B***s: 0
GameController:
not a gamepad
Axis code 0: 0
Axis code 1: 1
Axis code 2: 2
Axis code 3: 3
Axis code 4: 4
Button code 0: 288
Button code 1: 289
Button code 2: 290
Button code 3: 291
Button code 4: 292
Button code 5: 293
Button code 6: 294
Button code 7: 295
Button code 8: 296
Button code 9: 297
Button code 10: 298
Button code 11: 299
Hat code 0: 16"

[Substring]

@peterpan123123 d**n "not a gamepad" ... I'll have to do like i did with my very first ppsspp configgen

[Skazz]

@Substring After the last unstable release (26.02.) i got a black screen on dreamcast games. Sound is still there and the game is running. An idea?

Unstable version 26.02. // rpi3 // 64gb

[Substring]

@Skazz no probs here

[Skazz]

@Substring on sat**day I changed some parts in the Emu.cfg but nothing happened. But after the update I got a Black Screen. Can you send me the original emu.cfg? Thx!

Edit: found the file and test it tomorrow.

[kelv]

@Substring Not for being a nightmare but there is something wrong in the latest 4.1 unstable release. I noticed in the fresh vanilla instalations I did in both sd cards that when you change something in recalconfig.conf is not reflecting well on the menu after rebooting. Even when changing things on the menu are not persisted or reflected after rebooting.

For example the kind of setup is always back to stable, no matter it's changed on the file or on the menu. The same with the overclock. That back up my theory with kodi that is also not persisting the changes. Pls could it be any folder or mount that is only r instead of r,w?

THX

[Substring]

@kelv Most of the sd card is RO (for read only), but this never prevented kodi from working. That is UNLESS your share is mounted as read-only because of a file system error (check dmesg)

Regarding the updates, and what really surprises me, is that the new unstable we released on sunday has a very important feature : updating the recalbox.conf. We made it the good way : it retrieves your previous settings of course. So if you set to unstable, and after updating to the last unstable, it still forces stable, i'm getting veeeeeeery suspicious, as my 4.1 SDs work flawlessly

[Skazz]

@Substring I found the "bug".

In the new recalbox.conf there is a new line for dreamcast (at the end):

dreamcast.videomode=DMT 9 HDMI

When I set the videomode to DMT4 HDMI then everything works again.
For the future it could be nice to have a documentation of the changes of the recalbox.conf.
Is there a documentation about these videomodes?

[Update]
Found this one:
https://github.com/recalbox/recalbox-os/wiki/N64-:-return-to-ES-(EN)
Which videomode was before?

[Substring]

@Skazz a documentation about these video modes ? Dude, it's just common raspberry stuff ... You can have a look at https://github.com/recalbox/recalbox-os/wiki/Video-configuration-detailled-(EN) also

[badges3000]

I have problems with Dreamcast emulator too. It plays only windowed, not in fullscreen. I had to set the config to CEA 16. It there a other way to play in fullscreen? I reset the config to get a clean one, but nothing changed.

[Substring]

@badges3000 same trick as N64 : we use lower resolution for performance. You should check how your tv/monitor upscales, it's not a bug on recalbox side

[Skazz]

@Substring

Suggestion: the videomodes (especially for PSX DC N64) could be changeable via the Recalbox menu. Like the selection of the emulation in the actual releases.
It would be another great feature.

[Substring]

@Skazz such a thing could be done for ANY emulator, but this is definitely not a priority in ES. I'd rather have it in the web manager for now + it requires a little knowledge + tvservice must get the good EDIDs (which is not always the case).

[jackalpret]

Hi, i'm using in pendrive unstable version for pc 64 bits.
I burn the image twice, and i have the same problem, doesnt save the config changes, and If I connect in pc with linux the "share" partition isn't created/accesible ... I thought the first boot is not creating well the share partition.

[starmagoo]

@rockaddicted how do I activate the driver correctly?
I use controllers.xboxdrv.enabled=0 to deactivate the xboxdrv. After the upgrade to 4.1 my Xbox Controller doesn't work correct.

[rockaddicted]

You have nothing to do, just to remapp your controller in ES.

[Substring]

I'd need mappings of wired xbox360 controllers, wired xbox one controllers. For this purpose, the easiest for you is to go to http://recalbox/help then launch the script and paste here the generated link.

Thank you very much

[rockaddicted]

@substring wired xbox360 controllers with xpad, are already up to date on repo.

[styletwo-wan]

Has the "bluetooth major improvement" been integrated into the build 11402041 ? Thank you.