• 0 Votes
    2 Posts
    722 Views
    J

    @jdoc I reached out to Xarcade, and this was their response:

    Hi John,

    Thank you for your interest in our Tankstick Max.

    To address the issue with the trackball/spinner for Raspberry Pi, we have two solutions:

    Custom Script: We have designed a custom script specifically for switching in the Raspberry Pi system. You can find the details here:
    I've attached the instructions for installing and using the spinner/trackball switching script on your RetroPie system. This document will guide you through setting up the script and provide details on how to utilize it effectively.

    Trackball/Spinner Mixing Adapter: We are releasing a trackball/spinner mixing adapter that combines both the spinner and trackball into a single device. This will resolve the issue for Raspberry Pi users. The adapter will be available at a low cost and ready for purchase in 1-2 months.

    I hope this helps!

    Best regards,

    Xgaming Support

    From the attached PDF:

    INSTALLATION INSTRUCTIONS

    AUTOMATIC INSTALLATION
    From terminal (press [F4] from EmulationStation to enter terminal) or, using SSH, enter the following
    commands EXACTLY as they appear:
    • cd
    • wget https://downloads.sourceforge.net/project/build-a-cade/xarcade.sh
    • chmod +x xarcade.sh
    • sudo ./xarcade.sh
    When the installation completes, you will be prompted to cleanup installation files (optional) and to
    reboot for changes to take effect.
    After the system is reloaded, load a game of your choice. Ensure the correct device (SPINNER or
    TRACKBALL) is active for the game. If not, press the RED BUTTON and then reload the game (exit with
    HOTKEY+START). After reloading, the correct device should be active. The current device remains active
    until the RED BUTTON is pressed, which switches input to the OTHER device. MANUAL INSTALLATION
    From terminal (press [F4] from EmulationStation to enter terminal) or, using SSH, enter the following
    commands EXACTLY as they appear:
    • cd
    • sudo apt update
    • sudo apt-get install python3-pip
    • sudo pip3 install evdev
    • wget https://downloads.sourceforge.net/project/build-a-cade/switchmouse.py
    • wget https://downloads.sourceforge.net/project/build-a-cade/red-button.sh
    • chmod +x red-button.sh
    • sed -i '1i sudo python3 /home/pi/switchmouse.py &' /opt/retropie/configs/all/autostart.sh
    • sudo reboot
    USAGE INSTRUCTIONS
    After installation and reboot, pressing the red button on the X-Arcade Tankstick MAX changes the
    input_player1_mouse_index in retroarch.cfg for the ARCADE system. Changes to the file are made
    instantly, but, if pressed while a game is running, the newly selected mouse won’t be active until the
    game is reloaded.
    To disable or reenable this feature, exit emulationstation by pressing [F4] on the keyboard, and enter the
    following command: sudo ./red-button.sh
    FILE DESCRIPTIONS
    xarcade.sh
    This Bash script automates the installation process for setting up X-Arcade switchmouse.py, a script used
    for changing the active mouse device in Retroarch between a Spinner and a Trackball using the RED
    button on the X-Arcade Tankstick MAX. Here's a breakdown of what the script does: Download Script: Downloads the switchmouse.py script and red-button.sh script from a
    specified URL. Update System Files: Updates the system's package lists to ensure it has the latest information
    about available packages. Install Dependencies: Installs necessary dependencies for running the switchmouse.py script,
    including python3-pip and evdev. Modify autostart.sh: Checks if the line sudo python3 /home/pi/switchmouse.py & is already
    present in the autostart.sh file. If not, it adds this line to the beginning of the file. Set File Ownership: Changes ownership of files to ensure they are owned by the user pi. Cleanup Installation Files: Offers the option to remove the installation files (xarcade.sh, which is
    the current script being executed) after installation. If the user chooses not to remove it, informs
    where the script is stored for manual deletion. Prompt for Reboot: Asks the user if they want to reboot the system to apply changes. If the user
    agrees, initiates a reboot; otherwise, informs the user that changes will take effect on the next
    reboot.
    Additionally, the script provides information on how to disable or enable the feature in the future by
    running sudo ./red-button.sh from the terminal.
    This script automates the setup process, making it easier for users to configure their systems for using X-
    Arcade switchmouse.py functionality.
    switchmouse.py Change Mouse Input for Retroarch: This script is designed to change the
    input_player1_mouse_index configuration in Retroarch between a Spinner and a Trackball using
    the RED button on the X-Arcade Tankstick MAX (middle mouse button). Create Configuration File: The script checks for the existence of the Retroarch configuration file
    (retroarch.cfg) in /opt/retropie/configs/arcade/. If the file doesn't exist, it creates it and sets
    the default value for input_player1_mouse_index. Find Next Mouse Device: It finds the next available Tankstick MAX mouse device in the system.
    This is done by looking for devices with the identifier "1241_1111" in the /dev/input/by-id/
    directory. Update Configuration File: The script updates the retroarch.cfg file with the index of the next
    mouse device found. It modifies the input_player1_mouse_index configuration line accordingly. Find Middle Mouse Button Event Device: It searches for the event device corresponding to the
    middle mouse button on the X-Arcade Tankstick MAX. This is done by scanning the /dev/input/
    directory for devices that support the middle mouse button event. Main Function: The main function of the script continuously monitors events from the middle
    mouse button device. When the middle mouse button is pressed, it triggers the process to
    switch to the next available mouse device and updates the Retroarch configuration file
    accordingly.
    Overall, this script automates the process of switching between Spinner and Trackball inputs in Retroarch
    using the middle mouse button on the X-Arcade Tankstick MAX, providing a convenient way for users to
    toggle between these input devices during gameplay.
    red-button.sh
    This Bash script automates the process of enabling or disabling mouse switching functionality using the
    red button the X-Arcade Tankstick MAX. Here's what the script accomplishes: Check Current Status: The script checks if the line sudo python3 /home/pi/switchmouse.py is
    present in the autostart.sh file located at /opt/retropie/configs/all/autostart.sh. This line
    initiates the functionality responsible for toggling between different mouse inputs. Toggle Functionality: If the line is found, indicating that mouse switching is currently enabled,
    the script prompts the user to confirm whether they want to disable it. Conversely, if the line is
    not found, indicating that mouse switching is disabled, it prompts the user to enable it. Update autostart.sh: Depending on the user's response, the script either removes or adds the
    line responsible for mouse switching to the autostart.sh file. This modification is performed
    using sed commands. Reboot Prompt: If any changes are made to the autostart.sh file, indicating a modification in
    mouse switching status, the script prompts the user to reboot the system for the changes to take
    effect. It ensures that the user's response is validated and provides appropriate feedback. Feedback: If no changes are made, the script informs the user that no modifications were
    performed.
    This script streamlines the process of managing mouse switching functionality, providing users with a
    convenient way to enable or disable this feature using the red button on their X-Arcade Tankstick MAX,
    with clear prompts and feedback throughout the process.
  • 0 Votes
    11 Posts
    3k Views
    mituM

    Mame2010 appears to have savestate = false in their config, so maybe the 'cannot save' message is normal. Other MAME cores do have 'savestate = true' though (MAME2003, MAME2003+, MAME).

  • 0 Votes
    18 Posts
    2k Views
    dankcushionsD

    @rogeriol said in Fullscreen is always on when starting an arcade game:

    If I leave the resolution adjust to best fit the tv, 4k is selected and I believe this could tax the rendering on performance in RetroArch.

    https://retropie.org.uk/docs/Pi4/#4k-video-display

    @rogeriol said in Fullscreen is always on when starting an arcade game:

    I changed resolution on raspi config to 1280 720 to be easier on the rendering

    pi4 is very capable of doing 1080p so i would use that, using the method in the previous link.

  • 0 Votes
    3 Posts
    418 Views
    duglorD

    @sleve_mcdichael said in Shader Activation text in Retroarch.cfg?:

    video_shader = "/path/to/shader.glslp"

    Edit: if you want them enabled by default, use also:
    video_shader_enabled = "true"

    THANKS!

  • 0 Votes
    3 Posts
    1k Views
    T

    @dankcushions You absolute legend! That has resolved my problem. Many, many thanks!

  • 0 Votes
    3 Posts
    1k Views
    D

    @mitu Thank you. I will never try that. Might have saved a lot of time if I did that in the first place :-)
    Happy Christmas

  • 0 Votes
    6 Posts
    484 Views
    TPRT

    @mitu Ok, I think I figured this one out. I added the following line to the retroarch.cfg in the /opt/retropie/configs.hdmi/c64/ folder:

    input_player1_select = "nul"

    and that seems to have fixed it.

    Thanks for your help! It did actually make me start looking at a few other things and pointed me in the correct direction!

  • Retroarch Menu is not shown anymore

    Help and Support
    10
    0 Votes
    10 Posts
    2k Views
    windgW

    @daubsi said in Retroarch Menu is not shown anymore:

    @windg Ok, understood! So you’re saying that retroarch itself sometimes corrupts the config when using its own function to save?

    It is not corrupted, but changed from the default settings that selected for the proper RetroPie operation and it happens everytime you save the settings from RA menu.

  • From where is retroarch.cfg seeded?

    Help and Support
    5
    0 Votes
    5 Posts
    977 Views
    BuZzB

    @daubsi Yes. The .rp-dist files are created when an emulator is installed or updated and the default config has been changed (as it won't overwrite your custom config).

  • 0 Votes
    2 Posts
    336 Views
    BuZzB

    @2Play Yeah - I will sort this.

  • 0 Votes
    2 Posts
    346 Views
    mituM

    @noneononeo said in Three player button/joystick setup is not configured properly - don't have a linux computer to edit the file on. Is there another way?:

    Built From: (Pre made SD Image on RetroPie website, Berryboot, or on top of existing OS etc.. - please provide the filename of any image used): Not sure as this was purchased from a facebook seller.

    We don't support 3rd party images and selling a RetroPie image is against its license. Ask the seller for support or start with the image from retropie.org.uk/download and we'd be able to provide support.

  • 0 Votes
    7 Posts
    1k Views
    V

    Hi @mitu ,

    I'm returning to advise you of my good fortune and to help any others who may have been in the same situation as me.

    I had been using my Xarcade tank stick controller in "Mode 1" with the Xarcade2Jstick driver which meant that Retropie was recognising it as a keyboard (iPac-type encoder).

    I have now switched the controller to "Mode 4" and omitted the driver which means that Retropie recognises the controller as two separate XBox 360 controllers.

    I can now configure each side of the controller with identical mappings and any game/platform I wish to use the right side instead of the left side of the controller, I simply change the Port 1 binds for in Retroarch.

    When I do this, Hotkey+Start (even on the righthand side) performs correctly and exits the game.

    Thank you once again for your help mitu.

  • Retroarch Configuration (solved)

    Help and Support
    3
    0 Votes
    3 Posts
    848 Views
    sirhenrythe5thS

    @dankcushions thanks a lot!!!
    Sorry, i read a lot of documentation over the years, but in this case i was too blind to have a look into the specific chapters...i only read the doc about "Configuration Editor", my fault!
    Thanks a lot for your help & patience!

  • 0 Votes
    5 Posts
    1k Views
    T

    @iandaemon yes it should be blank

  • 0 Votes
    3 Posts
    898 Views
    N

    @mitu Thanks for the reply! I’m not at my Pi at the moment but when I get situated, I’ll give that a shot and report back!

  • 0 Votes
    16 Posts
    2k Views
    F

    Thank you everyone for your feedback and suggestions! I think I figured out what is causing the conflicts I am experiencing, for which I'll reference the following screenshot of the mame input configuration for sf2.zip:

    sf2-210802-174734.png

    My rebindings are attempting to "relocate" buttons, assigning buttons 1->2, 2->3, 3->6, etc... (as noted before). The end result is that only the RetroPad bindings changed, not the keyboard key bindings. The OR clause in the mame mappings thus maps one key/button to two events and that ends up breaking things!

    @dankcushions said in Unable to configure per-ROM input override for MAME:

    point of order, but they do, but it relies on you using the correct physical location or your buttons:

    B A R
    Y X L

    I had not considered this, but this seems very sensible given mame's default inputs (key or retropad event). I had have wired things using the IPAC switch numbers, which won't be hard to change.

    1 2 3
    4 5 6

    EDIT
    Here is a post descripting this same problem, which is due to the "simultaneous" core input setting in retroarch:

    https://retropie.org.uk/forum/topic/29976/mame-button-mapping-conflicting-with-retroarch-button-mapping

  • 0 Votes
    2 Posts
    423 Views
    S

    Hotkey is set during initial controller configuration. You should be able to have a different one for every (type of) controller you use. Configure additional controllers through the EmulationStation start menu.

    Edit: oh but I guess you want to do this only for NES, so the shoulder button still works when using the SNES controller for SNES games... maybe not so simple then. The docs do say that hardcoded configurations are "locked to a specific core and controller," but in the example they give, I don't see anything that does tie it to a specific controller.

  • 0 Votes
    10 Posts
    4k Views
    jamrom2J

    @mitu Everything that is mapped to my controller works if Game Focus is turned off. Problem is now with 1.9.4. the keyboard doesn't work until Game Focus is turned on. Once Game Focus is on, I loose all the mappings, I can't even open the Retroarch menu. What was the need for the change. Before this version, I never saw this happen.

    It doesn't effect any games that do not use a keyboard until you get to Amiga, A800, AtariST and DOSbox-pure.

    I don't know a way around this without plugging in a true USB keyboard that has a scroll-lock key. My BT unit doesn't have one. I opened the retroarch.cfg and tried to remap the Game Focus key to another key, but it keeps automatically reverting back to scroll-lock as the entry.

    I've deleted Retroarch and reloaded it by source thinking maybe some file is still hanging around from a previous build, but it didn't change anything.

    I'm not sure what else to do with this other than buy a new, portable BT keyboard that has a scroll-lock key on it.

    Update....nevermind... I found this on reddit and see there is a way to reassign the on/off toggle. I set mine to page-up key. All good.

    https://www.reddit.com/r/RetroArch/comments/kv06im/psa_just_a_reminder_that_toggling_game_focus/

    Works fine. Now I can toggle it on and off and use both the hotkeys and keyboard as needed. Works great.

    Thanks again.

    JamR

  • 0 Votes
    5 Posts
    2k Views
    M

    @mitu You're totally right, the ROMs I have just aren't the two control set versions, I just tried Gauntlet and everything worked fine. Thanks for your help!!!