Raspberry Pi 4

For information, Recalbox IS NOT compatible with Raspberry Pi 4 yet.
Pour information, Recalbox N'EST PAS encore compatible avec le Raspberry Pi 4.

The Recalbox Team.

February 2019 Beta Version



  • Hello. The Beta is running great but I am having an issue with NES roms specifically. I don't know if it's a recalbox issue or something else. All the default freeware NES roms work fine but when I add my own they go to the black screen and then back to the game list. I saw in the original post that if that happens then to remap the controller which I've done with the same result. Recalbox does recognize my controller so I assume that isn't the issue. The really odd thing is that my roms were working fine just yesterday. I have tried reflashing the card with a fresh setup and still nothing. I am using a Raspberry Pi 3B+ and running the roms from USB but does the same with internal storage.


  • Tester

    @JCreazy
    Hello.
    I didn't experienced any issue with NES Rom.
    Can you please tell us and provide on which dedicated Rom you had issue?
    Note: I done test on XU4 and RPI3B with and without USB card.
    All my Rom are unzipped.


  • Staff
    Moderator
    Team

    @pilafsama exactement.
    C'est quelque chose qu'il faudra note dans la documentation finale.



  • Hi first thank u for doing that Job.
    i use mix of rpi 2&3 and some of first generation
    for my test with ur beta build i use the rpi2 with enimax ew-7811utc (useless no driver support?) so i use TP-Link TL-WN823N
    But found some problem:
    no support for WLAN .AC WIFI dongle with chip RT8812au - i was buy some for increase my wlan and now all 3 are useless?
    Wifi key configuration no warn if i use symbols like ?!.%& and so i waste a lot of time.
    then i start in Kodi (i use libreelec on all my rpi to receive tv as sat>ip) i use an app on my android as remote control - some function i can't use, for example sound volume high and low (mute was working)
    next problem system (kodi) hang a lot and freeze sometimes only restart would help
    i think recalbox is a good idea with kodi inclusive - but please guys no driver for new wifi dongle? for tv i need a lot of bandwith to handle video data.
    in few days i will try the rpi3 image
    Greetings Sapiens



  • @olivierdroid92
    It seems I found the issue, for some reason none of the roms in the set I had would boot but after trying a different set they work fine.

    Also, on an unrelated note, on occasion when I try to scrape, I get an error saying no systems were found, sometimes if I reboot it will work fine and other times it won't, I haven't quite pinpointed why this is occuring.


  • Staff
    Moderator
    Team

    All image updated to include important fixes

    Please download and flash the beta version. There were important pad issues in the previous beta, mainly affecting Reicast, Moonlight and Kodi.

    Using this new beta version, if your pad/joystick/whatever is not automatically mapped and needs to be remapped manually, you can contribute to make the pre-configured database growing:

    • Map your pad the most logical way. Use select as Hotkey if there is no dedicated button. Leave button/dpad/joystick unmapped if they do not exist physically on your device.
    • SSH your recalbox and cat the file /recalbox/share/system/.emulationstation/es_input.cfg
    • Copy the latest <inputConfig> ... </inputConfig> block and post it in this thread.

    This will help future users to get their pad/jostick/whatever auto-magically configured. Thanks!


  • Tester

    @Bkg2k
    Image : 2019-02-24
    Board : RPI3

    USB Wired PAD : USB Wired iNNEXT SFC Snes
    <inputConfig type="joystick" deviceName="USB Gamepad " deviceGUID="03000000790000001100000010010000" deviceNbAxes="2" deviceNbHats="0" deviceNbButtons="10">
    <input name="a" type="button" id="1" value="1" code="289" />
    <input name="b" type="button" id="2" value="1" code="290" />
    <input name="down" type="axis" id="1" value="1" code="1" />
    <input name="hotkey" type="button" id="8" value="1" code="296" />
    <input name="left" type="axis" id="0" value="-1" code="0" />
    <input name="pagedown" type="button" id="5" value="1" code="293" />
    <input name="pageup" type="button" id="4" value="1" code="292" />
    <input name="right" type="axis" id="0" value="1" code="0" />
    <input name="select" type="button" id="8" value="1" code="296" />
    <input name="start" type="button" id="9" value="1" code="297" />
    <input name="up" type="axis" id="1" value="-1" code="1" />
    <input name="x" type="button" id="0" value="1" code="288" />
    <input name="y" type="button" id="3" value="1" code="291" />

    USB Wired PAD : Wired GameStop PS4 Fun Controller
    inputConfig type="joystick" deviceName="GameStop PS4 Fun Controller" deviceGUID="03000000c01100000140000011010000" deviceNbAxes="6" deviceNbHats="1" deviceNbButtons="14">
    <input name="a" type="button" id="2" value="1" code="306" />
    <input name="b" type="button" id="1" value="1" code="305" />
    <input name="down" type="hat" id="0" value="4" code="16" />
    <input name="hotkey" type="button" id="12" value="1" code="316" />
    <input name="joystick1left" type="axis" id="0" value="-1" code="0" />
    <input name="joystick1up" type="axis" id="1" value="-1" code="1" />
    <input name="joystick2left" type="axis" id="2" value="-1" code="2" />
    <input name="joystick2up" type="axis" id="5" value="-1" code="5" />
    <input name="l2" type="button" id="6" value="1" code="310" />
    <input name="l3" type="button" id="10" value="1" code="314" />
    <input name="left" type="hat" id="0" value="8" code="16" />
    <input name="pagedown" type="button" id="5" value="1" code="309" />
    <input name="pageup" type="button" id="4" value="1" code="308" />
    <input name="r2" type="button" id="7" value="1" code="311" />
    <input name="r3" type="button" id="11" value="1" code="315" />
    <input name="right" type="hat" id="0" value="2" code="16" />
    <input name="select" type="button" id="8" value="1" code="312" />
    <input name="start" type="button" id="9" value="1" code="313" />
    <input name="up" type="hat" id="0" value="1" code="16" />
    <input name="x" type="button" id="3" value="1" code="307" />
    <input name="y" type="button" id="0" value="1" code="304" />
    </inputConfig>

    BT Pad : 8bitdo SN30 Pro
    inputConfig type="joystick" deviceName="8Bitdo SN30 Pro" deviceGUID="05000000c82d00000161000000010000" deviceNbAxes="6" deviceNbHats="1" deviceNbButtons="16">
    <input name="a" type="button" id="0" value="1" code="304" />
    <input name="b" type="button" id="1" value="1" code="305" />
    <input name="down" type="hat" id="0" value="4" code="16" />
    <input name="hotkey" type="button" id="2" value="1" code="306" />
    <input name="joystick1left" type="axis" id="0" value="-1" code="0" />
    <input name="joystick1up" type="axis" id="1" value="-1" code="1" />
    <input name="joystick2left" type="axis" id="2" value="-1" code="2" />
    <input name="joystick2up" type="axis" id="3" value="-1" code="5" />
    <input name="l2" type="button" id="8" value="1" code="312" />
    <input name="l3" type="button" id="13" value="1" code="317" />
    <input name="left" type="hat" id="0" value="8" code="16" />
    <input name="pagedown" type="button" id="7" value="1" code="311" />
    <input name="pageup" type="button" id="6" value="1" code="310" />
    <input name="r2" type="button" id="9" value="1" code="313" />
    <input name="r3" type="button" id="14" value="1" code="318" />
    <input name="right" type="hat" id="0" value="2" code="16" />
    <input name="select" type="button" id="10" value="1" code="314" />
    <input name="start" type="button" id="11" value="1" code="315" />
    <input name="up" type="hat" id="0" value="1" code="16" />
    <input name="x" type="button" id="3" value="1" code="307" />
    <input name="y" type="button" id="4" value="1" code="308" />
    </inputConfig>

    BT Pad : 8Bitdo SF30 Pro
    <inputConfig type="joystick" deviceName="8Bitdo SF30 Pro" deviceGUID="05000000c82d00000061000000010000" deviceNbAxes="6" deviceNbHats="1" deviceNbButtons="16">
    <input name="a" type="button" id="0" value="1" code="304" />
    <input name="b" type="button" id="1" value="1" code="305" />
    <input name="down" type="hat" id="0" value="4" code="16" />
    <input name="hotkey" type="button" id="2" value="1" code="306" />
    <input name="joystick1left" type="axis" id="0" value="-1" code="0" />
    <input name="joystick1up" type="axis" id="1" value="-1" code="1" />
    <input name="joystick2left" type="axis" id="2" value="-1" code="2" />
    <input name="joystick2up" type="axis" id="3" value="-1" code="5" />
    <input name="l2" type="button" id="8" value="1" code="312" />
    <input name="l3" type="button" id="13" value="1" code="317" />
    <input name="left" type="hat" id="0" value="8" code="16" />
    <input name="pagedown" type="button" id="7" value="1" code="311" />
    <input name="pageup" type="button" id="6" value="1" code="310" />
    <input name="r2" type="button" id="9" value="1" code="313" />
    <input name="r3" type="button" id="14" value="1" code="318" />
    <input name="right" type="hat" id="0" value="2" code="16" />
    <input name="select" type="button" id="10" value="1" code="314" />
    <input name="start" type="button" id="11" value="1" code="315" />
    <input name="up" type="hat" id="0" value="1" code="16" />
    <input name="x" type="button" id="3" value="1" code="307" />
    <input name="y" type="button" id="4" value="1" code="308" />

    Desolé, je ne sais pas comment mettre tout ca en mode editeur



  • 	</inputConfig>
    	<inputConfig type="joystick" deviceName="Logitech Gamepad F710" deviceGUID="030000006d0400001fc2000005030000" deviceNbAxes="4" deviceNbHats="1" deviceNbButtons="13">
    		<input name="a" type="button" id="1" value="1" code="305" />
    		<input name="b" type="button" id="0" value="1" code="304" />
    		<input name="down" type="hat" id="0" value="4" code="16" />
    		<input name="hotkey" type="button" id="10" value="1" code="316" />
    		<input name="joystick1left" type="axis" id="0" value="-1" code="0" />
    		<input name="joystick1up" type="axis" id="1" value="-1" code="1" />
    		<input name="joystick2left" type="axis" id="2" value="-1" code="3" />
    		<input name="joystick2up" type="axis" id="3" value="-1" code="4" />
    		<input name="l2" type="button" id="6" value="1" code="312" />
    		<input name="left" type="hat" id="0" value="8" code="16" />
    		<input name="pagedown" type="button" id="5" value="1" code="311" />
    		<input name="pageup" type="button" id="4" value="1" code="310" />
    		<input name="r2" type="button" id="7" value="1" code="313" />
    		<input name="right" type="hat" id="0" value="2" code="16" />
    		<input name="select" type="button" id="8" value="1" code="314" />
    		<input name="start" type="button" id="9" value="1" code="315" />
    		<input name="up" type="hat" id="0" value="1" code="16" />
    		<input name="x" type="button" id="3" value="1" code="308" />
    		<input name="y" type="button" id="2" value="1" code="307" />
    	</inputConfig>
    </inputList>
    


  • @bkg2k

    https://forum.recalbox.com/topic/16576/february-2019-beta-version/17

    F710 controller working on latest beta thanks (recalbox.2019-02-23-beta.x86_64.)



  • @bkg2k

    https://forum.recalbox.com/topic/16576/february-2019-beta-version/18

    Issue still persists on latest build, Kodi also fails to start on x64 image (both by selecting it form menu and shortcut button Y). No error on es_launch_stdout.log

    /recalbox/share/system/logs/es_launch_stderr.log

    # cat es_launch_stderr.log 
    usage: emulatorlauncher.pyc [-h] [-p1index P1INDEX] [-p1guid P1GUID]
                                [-p1name P1NAME] [-p1devicepath P1DEVICEPATH]
                                [-p1nbaxes P1NBAXES] [-p2index P2INDEX]
                                [-p2guid P2GUID] [-p2name P2NAME]
                                [-p2devicepath P2DEVICEPATH] [-p2nbaxes P2NBAXES]
                                [-p3index P3INDEX] [-p3guid P3GUID]
                                [-p3name P3NAME] [-p3devicepath P3DEVICEPATH]
                                [-p3nbaxes P3NBAXES] [-p4index P4INDEX]
                                [-p4guid P4GUID] [-p4name P4NAME]
                                [-p4devicepath P4DEVICEPATH] [-p4nbaxes P4NBAXES]
                                [-p5index P5INDEX] [-p5guid P5GUID]
                                [-p5name P5NAME] [-p5devicepath P5DEVICEPATH]
                                [-p5nbaxes P5NBAXES] -system SYSTEM [-rom ROM]
                                [-emulator EMULATOR] [-core CORE] [-ratio RATIO]
                                [-demo DEMO] [-netplay NETPLAY]
                                [-netplay_ip NETPLAY_IP]
                                [-netplay_port NETPLAY_PORT] [-hash HASH]
                                [-extra EXTRA]
    emulatorlauncher.pyc: error: unrecognized arguments: ��
    # 
    

    Thanks again team recalbox.


  • Staff
    Moderator
    Team

    @gnubit @olivierdroid92 Thanks for your pad configurations ;)

    @gnubit We're investigating the configgen extra chars issue.



  • Hello ! Je viens d'installer la toute dernière bêta et j'ai deux soucis : le thème n'est plus le même après avoir mis en FR (slide de gauche à droite) - les consoles ne s'affichent pas correctement.

    2ème soucis : Dreamcast ne fonctionne toujours pas. Normal ? Bloqué à la config H/D et manette ne réagit plus.



  • Hi,
    Beta : 2019-02-24
    Board : Rpi3B+

    This is es_input.cfg for my PS3 Clone Pad. It works very fine with internal bluetooth !

     <inputConfig type="joystick" deviceName="PLAYSTATION(R)3 Controller" deviceGUID="050000004c0500006802000000800000" deviceNbAxes="6" deviceNbHats="0" deviceNbButtons="17">
       <input name="a" type="button" id="1" value="1" code="305" />
       <input name="b" type="button" id="0" value="1" code="304" />
       <input name="down" type="button" id="14" value="1" code="545" />
       <input name="hotkey" type="button" id="10" value="1" code="316" />
       <input name="joystick1left" type="axis" id="0" value="-1" code="0" />
       <input name="joystick1up" type="axis" id="1" value="-1" code="1" />
       <input name="joystick2left" type="axis" id="3" value="-1" code="3" />
       <input name="joystick2up" type="axis" id="4" value="-1" code="4" />
       <input name="l2" type="button" id="6" value="1" code="312" />
       <input name="l3" type="button" id="11" value="1" code="317" />
       <input name="left" type="button" id="15" value="1" code="546" />
       <input name="pagedown" type="button" id="5" value="1" code="311" />
       <input name="pageup" type="button" id="4" value="1" code="310" />
       <input name="r2" type="button" id="7" value="1" code="313" />
       <input name="r3" type="button" id="12" value="1" code="318" />
       <input name="right" type="button" id="16" value="1" code="547" />
       <input name="select" type="button" id="8" value="1" code="314" />
       <input name="start" type="button" id="9" value="1" code="315" />
       <input name="up" type="button" id="13" value="1" code="544" />
       <input name="x" type="button" id="2" value="1" code="307" />
       <input name="y" type="button" id="3" value="1" code="308" />
     </inputConfig>
    

    Dreamcast works correct for me! I will test more next days.



  • bonjour
    j ai installer la derniere beta et quand je veux lancer un jeux dreamcast , ca se bloque a la configuration de la manette que dois je faire pour contrer ce probleme ??? sinon pour la neo geo cd le bruit n est plus present


  • Staff
    Moderator
    Team

    @ViRuS-MaN reconfigure ta manette et on a pas de boule de cristal merci d etre precis.



  • J ai fait la configuration et ca fonctionne , mais je ne comprends pas ma manette etait reconnue je pouvais bouger dans les menus et lancer un jeux sur d autre systeme ca fonctionne , la j ai reconfigurer ma menette comme tu me la conseiller et ca fonctionne.
    merci



  • Bonjour !
    Merci pour le travail accompli.
    Ma config :
    Raspberry Pi 3b +
    Micro SD Sandisk 32 Go
    Config et roms sur clée USB
    recalbox.2019-02-23-beta.rpi3
    Voila mon souci ,impossible de sauvegarder mes shaders ainsi que les overlays dans retroarch .Je fais bien la sauvegarde via retroarch qui m'indique sav ok de la config puis quand je quitte le menu retroarch et que je relance une rom, il faut de nouveau reconfigurer les shaders ainsi que les overlays pour pouvoir jouer dans de bonne condition.


  • Tester

    Bonjour à tous ^^

    @Bkg2k voici les configurations pour différents pads avec la version BETA 2019.02.23 rpi3 sur un pi3b.

    La liste des pads :

    • XBOX 360 Filaire (Officiel MICROSOFT)
    • iBuffalo Classic USB Gamepad
    • 8Bitdo NES30 Arcade Stick (USB et sans fils)
    • PS4 Dualshock 4 (Officiel SONY) (USB et sans fils)
    • SNES "no name"
    • 8Bitdo SFC30 (USB et sans fils)
    • 8Bitdo SF30 PRO (USB et sans fils)

    --> Lien pastebin des configurations pad

    Le stick arcade "8Bitdo NES30" est configuré comme sur l'image en lien.

    Merci pour le travail accompli, au plaisir d'aider...

    PS : C'est normal que le pad 8Bitdo SF30 PRO utilisé directement en mode "filaire USB" soit détecté avec le nom "Microsoft X-Box 360 pad" (Ce n'est pas une erreur, j'ai vérifié plusieurs fois ^^) ?


  • Tester

    @Bkg2k
    Ordre pour appairer deux manettes BT.
    Board : RPI3B
    Image : 2019-02-24

    Y a t il un ordre pour appairer 2 manettes en Bluetooth ?
    Je suis en D-input mode (Start+B)

    Depuis une fresh installe, Micro SD uniquement, pas de WIFi, Rj-45 uniquement, pas de theme.

    Il m'est impossible d'appairer 2 manettes BT dans l'ordre suivant.
    1- Demarrage recalbox ; fresh installe
    2- Suppression de tous les liens BT
    3- reset BT manette 8bitdo SF30 Pro
    4- détection BT manette 8bitdo SF30 Pro
    5- demande de connection BT manette 8bitdo SF30 Pro = ok
    6- reset BT manette 8bitdo SN30 Pro
    7- détection BT manette 8bitdo SN30 Pro
    8- demande de connection BT manette 8bitdo SN30 Pro = impossible à appairer (cette manette se trouve en 2ieme position dans la liste)
    Dans la liste j'ai
    a) Mac SF30
    b) Mac SN30--> je clique OK ici

    Par contre en changeant l'odre ce fonctionne
    1- Demarrage recalbox ; fresh installe
    2- Suppression de tous les liens BT
    3- reset BT manette 8bitdo SN30 Pro
    4- détection BT manette 8bitdo SN30 Pro
    5- demande de connection BT manette 8bitdo SN30 Pro = ok
    6- reset BT manette 8bitdo SF30 Pro
    7- détection BT manette 8bitdo SF30 Pro
    8- demande de connection BT manette 8bitdo SF30 Pro = OK ca marche (cette manette se trouve en 1ere position dans la liste)
    a) Mac SF30 --> je clique OK ici
    b) Mac SN30

    Question : Y a t il une préférence des adresse MAC de détection BT pour appairer les manettes BT ?
    J'ai l'impression que lorsque la manette que l'on veut appairer se trouver en 2ieme position, on arrive sur "failed to pair" alors que si la 2ieme manette à appairer est lister en première position, ca fonctionne.
    Est-ce possible ?



  • @ddpiksen said in February 2019 Beta Version:

    Bonjour !
    Merci pour le travail accompli.
    Ma config :
    Raspberry Pi 3b +
    Micro SD Sandisk 32 Go
    Config et roms sur clée USB
    recalbox.2019-02-23-beta.rpi3
    Voila mon souci ,impossible de sauvegarder mes shaders ainsi que les overlays dans retroarch .Je fais bien la sauvegarde via retroarch qui m'indique sav ok de la config puis quand je quitte le menu retroarch et que je relance une rom, il faut de nouveau reconfigurer les shaders ainsi que les overlays pour pouvoir jouer dans de bonne condition.

    Hello friends! I noticed exactly the same problem. I have pretty much the same configuration except for my microSD card which has 128Gb and my roms are internal. In no one retroarch emulator I can save configurations of shaders. In the previous version (13.07.18) with R pi 3B this was possible. Thanks.


Log in to reply
 

Want to support us ?

229
Online

61961
Users

18647
Topics

140083
Posts

Looks like your connection to Recalbox Forum was lost, please wait while we try to reconnect.