Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • wilstorm
    Participant
    Post count: 5

    That’s awesome to hear it’s an easy fix, thanks Buzz and have a great day! :)

    wilstorm
    Participant
    Post count: 5

    I am having different issue related to the same option:

    “Press a key (or joypad button 0) to configure launch options for emulator/port ($emulator).”

    What I am using is an XBOX 360 wireless dongle as per these instructions:

    https://github.com/RetroPie/RetroPie-Setup/wiki/setting-up-the-xbox360-controller

    It works perfectly except for one small issue. Usually buttons A, B, C & D map to 0, 1, 2 & 3 on the XBOX 360 controller. When using wireless controller as per the instructions buttons A, B, C & D map to values 4,5,6 & 7.

    I tried pressing all buttons on the controller but none of them will let me select/change the emulator. The keyboard works fine but I’m trying to access this feature via the controller so I don’t need a keyboard plugged in. Is there a way to change the button from 0 to 4 so it works with the wireless setup to change the emulator?

    I see the code area you pointed out in the /opt/retropie/supplementry/runcommand/runcommand.sh file but I don’t quite understand what to change.

    check for x/m key pressed to choose a screenmode (x included as it is useful on the picade)
    clear
    echo “Press a key (or joypad button 0) to configure launch options for emulator/port ($emulator). Errors will be logged to /tmp/runcommand.log”
    IFS= read -s -t 1 -N 1 key </dev/tty
    if [[ -n “$key” ]]; then
    get_all_modes
    main_menu
    dont_launch=$?
    clear
    fi

    if [[ -n $__joy2key_pid ]]; then
    kill -INT $__joy2key_pid
    fi

    if [[ $dont_launch -eq 1 ]]; then
    exit 0
    fi

    switch_mode “$mode_new_id”
    switched=$?

    [[ -n “$fb_new” ]] && switch_fb_res “$fb_new”

    config_dispmanx “$save_emu”

    Any help would be greatly appreciated.

    wilstorm
    Participant
    Post count: 5

    You shouldn’t need the ROMs in both locations. I just loaded RetroPie 2.3 from a fresh image download and mame4all-pi works perfectly. I did NOT need to modify any files (i.e. – es_systems.cfg and mame.cfg are now configured correctly to dump ROMs into /home/pi/RetroPie/roms/mame/ and just go!

    What has been missing from mame4all-pi directory in the RetroPie builds is several folders. I just download mame4all-pi from the original website and move the missing folders into /opt/retropie/emulators/mame4all-pi/. I don’t think that is the problem though. It’s nice to do as they don’t even have the artwork or samples folders (samples are nice for games like Donkey Kong, etc.) Maybe they will correct all the missing directories in a future build.

    When you used ClrMamePro to verify your sets did you use split-merge, non-merged or merged? From the list of ROMs in your original post you’re still missing kof94_p1.rom in the zip. I still don’t think that’s your problem as it’s not finding ANY of the ROMs in that list and it is almost the complete list of ROMs needed for that game. They all show missing. It’s also a parent/master game so no additional files would be required to run it.

    Here’s the list with file size, CRC and ROMset name:

    kof94_c1.rom | 2097152 | b96ef460 | kof94 |
    | kof94_c2.rom | 2097152 | 15e096a7 | kof94 |
    | kof94_c3.rom | 2097152 | 54f66254 | kof94 |
    | kof94_c4.rom | 2097152 | 0b01765f | kof94 |
    | kof94_c5.rom | 2097152 | ee759363 | kof94 |
    | kof94_c6.rom | 2097152 | 498da52c | kof94 |
    | kof94_c7.rom | 2097152 | 62f66888 | kof94 |
    | kof94_c8.rom | 2097152 | fe0a235d | kof94 |
    | kof94_m1.rom | 131072 | f6e77cf5 | kof94 |
    | kof94_p1.rom | 2097152 | f10a2042 | kof94 |
    | kof94_s1.rom | 131072 | 825976c1 | kof94 |
    | kof94_v1.rom | 2097152 | 8889596d | kof94 |
    | kof94_v2.rom | 2097152 | 25022b27 | kof94 |
    | kof94_v3.rom | 2097152 | 83cf32c0 | kof94 |

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