Posts by moroi

    regarding controller, retroarch gives me this:

    es_systems.cfg is clear, but retroarch.cfg line 2908 is:

    video_message_pos_y = "0.050000"


    ..there's probably an "audio*" line I need to edit, right?

    wait, one of the game starts, complains about the lack of bios and warns about compatibility issues - right, the sound is jagged is skips a lot.


    I can't use the controller, so I can't really play it.


    my bioses:

    buro:~ # md5sum emulators/bios/scph*

    924e392ed05558ffdb115408c263dccf emulators/bios/scph1001.bin

    6e3735ff4c7dc899ee98981385f6f3d0 emulators/bios/scph101.bin

    8dd7d5296a650fac7319bce665a6a53c emulators/bios/scph5500.bin

    490f666e1afb15b7362b406ed1cea246 emulators/bios/scph5501.bin

    32736f17079d0b2b7024407c39bd3050 emulators/bios/scph5502.bin

    1e68c231d0896b7eadcad1d7d8e76129 emulators/bios/scph7001.bin

    buro:~ #

    Hi,


    I followed steps 1-8 (hopefully correctly), no joy.


    The only out of the ordinary thing was step 4 - once I got into retroarch gui my controller stopped working completely, and when trying my other input method (bluetooth mouse), only scroll wheel working - never mind, I connected a keyboard and hit escape to get out of retroarch gui.


    Now, when started emulationstation the psx game list has every game twice (presumably once for the cue file and the second for the bin/img)

    The bigger problem was that no game was launching - screen would turn black and come back to emulationstation psx game list.


    I tried going again in retroarch using keyboard and went to the online updater and downloaded a few random things - after that rebooted and started emulationstation again - this time the game would start, I could hear the game sounds but the screen remained black, with the exception of a frame counter on the lower left that was incrementing continuously (not a frames-per-second but a frames-since-starting-the-game thing)


    I couldn't get out of the game using the usual select+start or any other way, managed to kill emulationstation via ctrl-alt-del using keyboard.


    Note about the bioses: copied over all the files I had on RetroPie, don't know if the same ones are expected here. Maybe it's looking for slightly different names, or different case...is there a way to check retroarch is finding the expected ones?


    (and yeah, running everyting from microsd card)

    Thank you robmcc83 , I really do appreciate!


    Based on your earlier hint I went and chosen a different path: installed AEL from a zip file and the desired emulators: snes9x2010 and pcsx-rearmed from standard LE/Kodi repos, then proceeded to define the launchers that called RetroPlayer (at least to my still shaky understanding that's AEL/RetroPlayer approach that none of your 3 alternatives cover).


    This worked like a charm for SNES, but for PSX not so much.

    I first had the issue where PSX roms would start (although complaining about missing bios) but the buttons would be dead, pads/joysticks funtional - can't even start a game without working buttons..

    I can't see where it tells me to upload the bioses, it's showing up briefly on a upper-right bubble when I start a rom, but it goes away before scrolling to show the whole message.

    I managed to place the bioses to ~/.kodi/addons/game.libretro.pcsx-rearmed/resources/system and the missing-bios message goes away, but the emulator now core-dumps :(


    In AEL configuration there's a "Check retroarch BIOSes" option that if you point your Retroarch system directory to the place you copied the BIOSes to it checks them and in my case the checksums for what's expecting for PSX (5500, 5501 and 5502) match.

    But this is what Retroarch would expect, and as far as I understand I'm using RetroPlayer...

    Am I too far in the woods?


    I'm not tied to the current approach, I simply chose it as it was looking like the minimal amount of fuss. The fact that it did work for SNES was encouraging..

    I'm going to look closely at your options and re-evaluate my approach, probably emulationstation seems best since I've seen it working with RetroPie...

    Thank you, robmcc83 I got it playing SNES roms via AEL/Retroplayer. The whole process was confusing, at least for a newbie like me who's missing a lot of context.

    Also had to mess around for a bit to get my no-name PS3 compatible controller to work correctly in-game. Not that it works flawlessly with the LE interface either...


    No artwork for now, as it's looking to take too much effort.

    I'll see about geting the PSX roms to work, this one has the added complication of having to supply as bios as well..

    Hi,


    I'm using stock LibreELEC 9 on a RPI 3B+ and I have some SNES and PSX roms I'd like to play.

    Currently alternating between LibreELEC and RetroPie by swapping microSD cards and would like to get rid of that.
    I am aware that I can install Kodi on the Debian Stretch installation RetroPie runs on, but to be honest I enjoy LibreELEC and the just-enough-OS concept (not to mention generally Debian lagging behind with sofware packages versions) to want to keep using.


    I have seen there's a custom LibreELEC 9 RR build for this purpose, but I'd like to stay with the stock image...is there some documentation on what needs to be done to get the gaming going?

    Of course I appreciate it's going to require some manual work at this stage.

    setup: LE v8.90.006 on RPI3, Kore 2.4.4 on LOS 15.1 (Android 8.1) + F-Droid


    Using Kore to navigate LE v8.90.006 works, except entering text which gets LE stuck; then Kore loses connectivity ("connecting..."). I have to reboot the PI to get LE back.

    I don't have any peculiar configuration or add-on installed; in fact it is a brand new install for evaluation purposes.


    I went and installed LE v8.2.5 which works perfectly with Kore; in fact I'm using Kore as the main navigation tool.


    For now, I'm just staying with the stable release, which is working very well. But I have to say the alpha release with the recent kernel looks tempting. It did seem to run a bit too hot compared to stable, though.