Forum Replies Created

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

    duckclimber: Can you expand on your switch to shut off the Xin-Mo? Are you just cutting USB power? Does this require a reboot each time you want to switch controllers? I’m trying to do the exact same thing.

    hijinksensue
    Participant
    Post count: 17

    I’ve been running this setup with the custom kernel and command line file edits for a while, but I’m afraid to update to the most recent version of Retropie for fear of undoing all of these changes. Anyone have any experience with doing an update and keeping these customizations?

    hijinksensue
    Participant
    Post count: 17

    I’m in the exact same boat. I have a bartop machine running with the Xin-Mo dual arcade controls and I want to be able to plug in two wired Gravis Gamepads to play Sega, NES, SNES games, etc. Very interested to see if anyone has a solution for this.

    hijinksensue
    Participant
    Post count: 17

    I had the same problem, and the fix listed above worked for me. There must be a bug where some users are losing automapping of page up and page down.

    hijinksensue
    Participant
    Post count: 17

    @colinshare84

    I tried the changes you mentioned above and it initially just broke my es_input.cfg file. Then I realized editing the file in OS X Text Edit was changing the type of quotation marks used in the strings. I copied and pasted them from the line above, saved and I’ve got my page up and page down buttons back.

    More users are having the same issues. https://www.petrockblock.com/forums/topic/pageup-pagedown-retropie-3/

    There must be a bug that only affects some in 3.0.

    hijinksensue
    Participant
    Post count: 17

    This might be off topic, but ever since making all these fixes on 3.0 I can no longer scroll through games lists using the buttons assigned to L and R shoulder. Anyone else?

    hijinksensue
    Participant
    Post count: 17

    Finally did the cmdline.txt edit and nothing is different than before I made that change. The controller still shows up at 1 usb controller.

    Looks like I’m in the same boat as krauthaus above. If you examine his solution, you see that he’s just using the Xin-Mo as one big USB controller with a lot of buttons. In his config file both players are using js0. This solution DOES work, but it doesn’t address the Xin-Mo being seen as one controller vs. two.

    Any ideas?

    ####UPDATE#####

    Solved this myself. I put a blank line instead of a single whitespace between the original content of the cmdline.txt file and the new additions. When I switched it to a single space the Xin-Mo shows up as two controllers now. Leaving this here in case anyone else has the same problem.

    hijinksensue
    Participant
    Post count: 17

    Thanks for the suggestion.

    Looks like the proper command was:

    sudo dpkg -r xboxdrv

    hijinksensue
    Participant
    Post count: 17

    Bumping this. Hoping someone can help.

    hijinksensue
    Participant
    Post count: 17

    If we’ve already patched the kernel, should we somehow re-patch to the original kernel? Or would an apt-get update take care of that?

    I will try it on the THT-THT 2 player USB version of the controller that is being sold as the XIN-Mo and see if this fixes its problems as well.

    hijinksensue
    Participant
    Post count: 17

    @monchote Exactly! This hack DID fix my 2 player issue (in 3.0 beta). I never actually had the original auto fire issue in the first place. 3.0 (proper) seems to have undone that fix. Whether it was an accident or not, it worked.


    @feederchain
    I have the Xin-Mo 2 player (or at least that’s what I paid for) but it shows up in Retroarch as a “THT THT 2 Player USB.” From what I understand, they’re essentially the same hardware.

    Please let me know if I can be of help testing anything.

    hijinksensue
    Participant
    Post count: 17

    I might be confused, but in 3.0 they seem to have integrated the EmulationStation controls and the Retroarch controls. There’s only one set up as far as I can tell and it’s supposed to cover both. Am I missing something important?

    hijinksensue
    Participant
    Post count: 17

    As far as I can tell, this kernel hack doesn’t work with 3.0 for both players.

    I ran the upgrade binary script.
    Then I ran the new most recent Kernel hack update.
    Then I ran JSTest and it sees every button on the Xin-Mo individually, but still registers it all as one big controller (which is what I believe it always did).
    Then I ran the input config option within Retropie. It said it detected 3 controllers (I assume Xin-Mo one and two plus the keyboard?), but no matter which button I held down it said I was configuring for player one.
    Same happened when I used the old school controller config option within the Retropie settings.
    At least for now, my player 2 is dead.

    hijinksensue
    Participant
    Post count: 17

    I was wondering the same thing. Im about to run the 3.0 update script but not until I know if A) Xin-Mo comes pre-patched B) I need to Rematch it after the upgrade and C) if the current kernel patch will even work for 3.0.

    hijinksensue
    Participant
    Post count: 17

    Thanks for the reply. I don’t remember doing an apt-get update before shutting it off, but it’s entirely possible that I did. I’m going to turn it off and kill the power to the power strip tonight and see how it behaves tomorrow.

    2 questions:

    1) Should I NOT being running apt-get update any more? Will that kill the patched kernel?

    2) Is there any chance of getting this patched kernel built into the main release of Retropie?

    hijinksensue
    Participant
    Post count: 17

    I applied Feederchain’s 2nd updated custom kernel patch and it totally fixed all the problems I was having with my Xin-Mo (actually THT THT) usb 2 player set up.

    I used it for about 2 weeks, then turned off my Retropie arcade for a week while I was on vacation. When I got home, the custom kernel had reverted to the original and the 2 player controls behaved like one giant player one controller again.

    I reapplied the patched kernel and everything is fine again. Does this make any sense at all? Is there anyway that powering down the RasPi for a week could undo this kernel patch? Did I not use significant enough privileges when I applied it? Any help would be appreciated.

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