Forum Replies Created

Viewing 10 posts - 36 through 45 (of 45 total)
  • Author
    Posts
  • taalas
    Participant
    Post count: 56

    Hi Buzz,

    I have

    – changed retroarch.cfg to include my Xbox 360 Controller setup (mainly because I followed the steps on the wiki), I can easily redo this though

    – changed some controller settings for specific lr cores in the respective retroarch.cfg because I wanted 2 button systems to be B/Y instead of A/B

    – removed some systems from es_systems.cfg (the home computers and ScummVM)

    taalas
    Participant
    Post count: 56

    This will only let me choose video mode for emulator and video mode for rom.

    I might not have the necessary updates set for the new emulator selection mechanism. What exactly do I need to update and what configuration files will be overwritten?

    taalas
    Participant
    Post count: 56

    I ran into the same problems when updating/installing lr-genesis-plus-gx.

    I previously had updated ES and the simple theme, installing emulator cores breaks es_systems.cfg due to the new emulator choosing mechanics I think.

    If I perform a binary update (meaning the first point in the setup script, right?) what do I loose in terms of configuration?

    Thanks!

    taalas
    Participant
    Post count: 56

    Yes, those files are added after loading the full retroarch.cfg and any lines overwrite the original ones.

    taalas
    Participant
    Post count: 56

    [quote=91734]The latest default snes emulator (as of about a week ago) is snes9x-next, which is far superior to pocketsnes in terms of accuracy, but it struggles a bit with certain Super FX games like Star Fox.[/quote]

    Is there a way to change this default behavior on a 2.6 SD image install without manually changing the core that is defined in the es_systems,cfg? Do I just install the lr-snes9x-next LR core?

    taalas
    Participant
    Post count: 56

    It seems to be AngelScript installing a file as /usr/local/include

    Is this intended behaviour?

    taalas
    Participant
    Post count: 56

    No ideas on this? Should I post the questions as seperate topics?

    taalas
    Participant
    Post count: 56
    in reply to: Boot problems #91703

    Yes it is a 2A PSU.

    I am not sure what is happening with the card but I ordered another one (a Sandisk Ultra this time) to see if that improves the situation. I am doing most of my card imaging in OS X so cloning it to the new card should not be a problem. My question was more in the line of: should I be afraid that the data on my old card is corrupt or is it more of an access problem and I keep using the data on the new card…

    taalas
    Participant
    Post count: 56
    in reply to: Boot problems #91461

    Yeah, it seems that the Samsung Evo cards don’t play well with the new Pi 2s. What I am uncertain about is whether I should just copy my data to the new card or rather reinstall everything for fear of data corruption somewhere on the card…

    taalas
    Participant
    Post count: 56
    in reply to: Boot problems #91427

    Hi Floob,

    yes, it is the RetroPie image for the Pi 2 and I am using a power supply that should be sufficient. It is one of the ModMyPi compatibility rated ones.

    I don’t have another micro SD card, but I could order one, since I was planning to have a spare to try other distros on the Pi. If the card is faulty I will RMA it with ModMyPi.

    If I just clone the card to another one it doesn’t have to be the exact same card, right? Do you have recommendations?

Viewing 10 posts - 36 through 45 (of 45 total)