[4.1-Unstable] Bug reports

[voljega]

@acris just curious but does this mean that from now on (4.1+) every ps3 pad (official, shanwan and gasia included) should use the bluez driver ?

[Substring]

@voljega
original is required for gasia, should also work with genuine
bluez works for shanwan and genuine

[Substring]

@treacle said in [4.1-Unstable] Bug reports:

My understanding was that PS3 controllers are automatically added as BT device after pairing via cable, right?

Yep, DualShock3 don't follow a regular pairing process (whereas DS4 do). You don't pair through ES with DS3

[Juan Carlos Leal Payá]

i cannot find the psp and c64 folder inside the roms folder

[Dwarf]

I wasn't able to configure psp controls, and dreamcast games don't work, i put the cd_boot.bin and dc_flash.bin files in the bios folder, is this it's place?

Also, I was at 4.1 unstable and upgrade an our ago, now the rpi3 won't start, kernel panic.

[Juan Carlos Leal Payá]

@Juan-Carlos-Leal-Payá i created it and works very well

[Substring]

@Dwarf i had no problems updating

[Mercvtio]

I'm having trouble with Dreamcast games. They launch allright and run smoothly, but I can't save (not enough blocks, whatever the game) and whenever I hit the hotkey, Reicast crashes and sends me back to EmulationStation. Can anyone save ?

I put the bios matching the OP md5 in the Bios folder, but it changes nothing.
I'm a bit lost.

[voljega]

@Mercvtio reicast doesn't seem to be a retroarch nor libretro core so what you describe is perfectly normal

[Mercvtio]

@voljega OK, so that's the normal behavior. Thanks !

Any idea about my saving issue, anyone ?

[Mercvtio]

Never mind, I just had to format the VMU by launching a game and soft resetting (A+B+X+Y+Start). Everything perfect now!

[Substring]

@Mercvtio start the bios, create save slots. Maybe we should add some memory slots out-of-the-box ...

[Dwarf]

@Substring One friend same as me, kernel panic after upgrade.

[sevenx]

I have done all Update to 4.1, then i pressed one more time the "Check Update" button and it installs another one, after the Update was done, i got an Kernel Panic Error on boot

Is this issue known?

[Substring]

@sevenx I guess your updates type was set back to stable. Can you mount your sd card on a linux and check ?

[jthemad]

Hi all, I'm testing the last 4.1 unstable on rpi3 and I can't solve the 'retroarch square' bug.
I tried to remove the ~/configs/retroarch/retroarchcustom.cfg and Recalbox generates it again, I restarted the system but I have the same problem. I know other people solve this bug, could you please tel me the extact procedure? Thanks all and sorry for my english

[Substring]

@jthemad If your're using custom configs, you should manually add the required line. And your english is just fine

[jthemad]

@Substring hi! Thanks for your answer..
I don't understand what do you mean with 'add the line manually'.. I deleted config file and Recalbox generated a new one, where am I wrong? What do you mean with custum config? Another issue I found: with Xbox 360 controller wired, I can't exit to main menu (hotkey + start). I tried to configure again the keys but same problem. With another pad all ok. I was using the same Xbox controller with 4.0.2 and all was working fine..
anyway great work with this release, waiting for stable release..
thank you

[Substring]

@jthemad All apologies, what i said doesn't work in the case of an upgrade from 4.0
So add to your retroarcCustom.cfg :

menu_driver = rgui
video_font_path = /recalbox/share_init/system/.emulationstation/themes/recalbox/data/ubuntu_condensed.ttf

This will restore retroarch as before

Regardnig your xbox pad : was this pad the 1st player ? The xbox 360/one driver changed in 4.1, you do need to reconfigure your pad. Was your pad the 1st player ? HK is not used on players others than the 1st

[jthemad]

@Substring thanks again.. ok I'll try to add the lines later.. regarding the controller I tried to set player1 and it doesn't work, tried to set default same issues. Looking in cfg file I noticed that I have controllers.xboxdrv.enabled=0, could it be the problem? (I had the same setting in 4.0.2 and it worked)