Forum Replies Created

Viewing 16 posts - 1 through 16 (of 16 total)
  • Author
    Posts
  • dkcdocdos
    Participant
    Post count: 20

    It’s retropie 2.6 and mame … um … the version that comes with the sd-image :) I haven’t changed anything regarding mame.

    dkcdocdos
    Participant
    Post count: 20

    Are you using 3.0 or 2.6?

    If 2.6, have you completed the retroarch joyconfig? No? Do this:

    Press F4 to exit ES

    sudo chown pi /opt/retropie/configs/all/retroarch.cfg (only once)
    
    cd /opt/retropie/emulators/retroarch/bin
    
    sudo ../retroarch-joyconfig -j 0 >> /opt/retropie/configs/all/retroarch.cfg

    For the 2nd controller use -j 1 >> and so on…

    dkcdocdos
    Participant
    Post count: 20

    I have the same problem (using an xbox360 controller); some psx games can’t be run with analog sticks, dpad works sluggy or not at all:

    You can switch the modes ingame, using a toogle button on your controller (you have to set one before) + F1. It opens RetroArch’s menu (see my linked thread, there’s a video); but it’s quite a nag changing it everytime.

    A sort of launch option would be cool…

    dkcdocdos
    Participant
    Post count: 20

    I’ve changed

    input_libretro_device_p1 = “5”

    to

    input_libretro_device_p1 = “RETRO_DEVICE_ANALOG”

    (the expression is from libretro.h)

    and the error won’t show up anymore!

    Sadly, the behaviour is unchanged; certain games won’t take any input from the controller.

    dkcdocdos
    Participant
    Post count: 20

    try this (for psx):

    open

    /opt/retropie/configs/all/retroarch-core-options.cfg

    change

    pcsx_rearmed_pad1type = “standard”
    pcsx_rearmed_pad2type = “standard”

    to

    pcsx_rearmed_pad1type = “analog”
    pcsx_rearmed_pad2type = “analog”

    dkcdocdos
    Participant
    Post count: 20

    I’ve did all this, and the relevant lines in the libretto.cfg afterwards seem to be:

    input_device_p1 = “0”
    input_player1_joypad_index = “0”
    input_libretro_device_p1 = “5”
    input_player1_analog_dpad_mode = “0”

    When searching for it in the retroarch.cfg it’s even documented:

    # Sets which libretro device is used for a user.
    # Devices are indentified with a number.
    # This is normally saved by the menu.
    # Device IDs are found in libretro.h.
    # These settings are overridden by explicit command-line arguments which refer to input devices.
    # None: 0
    # Joypad (RetroPad): 1
    # Mouse: 2
    # Keyboard: 3
    # Generic Lightgun: 4
    # Joypad w/ Analog (RetroPad + Analog sticks): 5
    # Multitap (SNES specific): 257
    # Super Scope (SNES specific): 260
    # Justifier (SNES specific): 516
    # Justifiers (SNES specific): 772

    BUT: When starting up, screen says

    RetroArch [WARN] :: Input device ID 5 is unknown to this libretro implementation. Using RETRO_DEVICE_JOYPAD.

    And it’s behaves like an all analog controller (with the known errors in certain games).

    So, i guess it’s the correct way (THX!), but since retroarch claims to not know the device id, it’s a bug…

    dkcdocdos
    Participant
    Post count: 20

    Or put to put it this way:

    Is there something like a startup option for psx games to use either “standard” or “analog”?

    dkcdocdos
    Participant
    Post count: 20
    dkcdocdos
    Participant
    Post count: 20

    There’s an automatic option? I only knew “standard” or “analog” for the core options…

    Actually i prefer to set either dpad or analog for each single game, kind of like a launch option.

    dkcdocdos
    Participant
    Post count: 20

    Yes, you may have to rebuild from multiple locations to get a complete working ROM

    That just did the job, Varth runs like a charm now!

    I took all the varth roms i could find super-duper legally own and ran the process again, clrmamepro fixed 3 zips and discarded one. The 3 remaining all work (in case i want to play the j-version – one day)

    thx!

    dkcdocdos
    Participant
    Post count: 20

    So i’ve followed these fine instructions by the letter with varth.zip, it didn’t work out as expected, the game still isn’t running.

    I noticed clrmamepro even removed some files, the zip ended up even smaller than before.

    Do i required multiple, different sets of the same game, so clrmamepro can rebuild them into one working romset?

    Or is it something else i haven’t thought of?

    dkcdocdos
    Participant
    Post count: 20

    Follow up question: how do i tell which romset a rom is? Try and error? Or is there a way to tell beforehand?

    dkcdocdos
    Participant
    Post count: 20

    Thx for the answers so far, great community here!

    The alternative’s performace is really poor, wonder why it’s in the image…

    As far i’ve understood, that romset-thing is like the “version” of the rom. I don’t have to do anything with MAME itself or some config, but only *cough* ;) find the “correct” rom for M4A.

    Right?

    dkcdocdos
    Participant
    Post count: 20

    See, i hate bumping threads, but this one is real important to me, so *bump*

    tl;dr of my first post:
    #1: Is MAME4ALL already part of 2.3 (since there’s a folder already)?
    #2: Is using the alternative MAME <command> in es_systems the right way to make it work?

    sry for bumping :~

    dkcdocdos
    Participant
    Post count: 20

    I’ve tried over the last weeks, but either ended up with the controller not running or still blinking or the pi freezing. No big deal though – at least better than 3 red leds :O

    Finally i’ve got it to work. Dunno where i went wrong exactly, guess i didn’t chmod the directory and never noticed…

    dkcdocdos
    Participant
    Post count: 20

    Ah great, haven’t found this one before. I’ll try… ;)

Viewing 16 posts - 1 through 16 (of 16 total)