XBOXDRV Guidance Needed

hansolo77

Hmm, never tried that. I'm actually shocked I didn't think of it. I used to be Tier 3 tech support. Going "off the script" and thinking of absolutely everything to eliminate all possibilities is just how I operate. I think that's why I'm probably able to grasp this better than other people. I've been trained on detective work, in a sense.

I've turned off my system for the night. I gotta eat dinner real quick and head to bed, work early tomorrow. Thanks for the suggestion, I'll give it a go when I get home tomorrow!

hansolo77

Ok, just got home, tried running the game from within EmulationStation (rather than my test script). Pressing num0 and num9 doesn't register in RetroArch. The EVTEST I ran yesterday confirms it's at least sending it. So the problem must be that RetroArch doesn't recognize that as a valid mappable key. I did some Googling, as RetroArch has NOTHING on a list of available keys. Turns out the left shift (shift) and right shift (rshift) ARE available, so I edited the retroarch.cfg file and changed Start to shift and select to rshift. Loaded up the game, and it works! So, either you're using an outdated keymap list for your player 2, or maybe you just never encountered a need to press Start on Player 2. After thinking about it, there was no reason to do that in my tests on the NES. I was testing with Bubble Bobble, because I knew it had a 2 player option, but that 2nd player is set up from the opening menu, rather than you pressing a button to activate it.

I'm glad I got it figured out. That would have been a hex on the whole thing if I couldn't make it work. Thanks again for that suggestion to test it. Had I not done that, I would have been completely lost.

mediamogul

@hansolo77 said in XBOXDRV Guidance Needed:

or maybe you just never encountered a need to press Start on Player 2

This is most likely the case. Looks like I'll have to switch things up a bit myself.

Thanks again for that suggestion to test it.

Not a problem. I'm glad it helped lead to a solution.

hansolo77

@mediamogul - Off another day tomorrow (typically Sundays and Thursdays) so that means more XBOXDRV time. :) I have a further need of your assistance, but I'm getting close to nailing this! Have you managed to map any "shifted" button combinations? The only thing my mini Sega Genesis hub is missing is a RESET button (which I have configured to exit out of games on my NES full size case). Since I'm primarily using the Sega hub with some USB controlled Sega 6-button controllers, I don't have a good clean way to exit out of games that aren't automatically supported through RetroArch. I'm speaking, of course, of the "Streets of Rage Remix" port. The only way I can exit out of that game right now is by having a keyboard attached and hit the ESCAPE key on the main menu, or turn the system off. I'd like to program (in XBOXDRV) a similar escape method of START+BACK (mode in Sega's case). Since the Start and Mode buttons are already mapped in the system, I wasn't sure how to set up a combo. Would it work if I did something like:

--ui-buttonmap start=KEY_A,back=KEY_B,start+back=KEY_C

Where I have a key for start, a key for back, and a third key for start+back? I thought I read in the official documentation for the driver (not the RetroPie wiki) that this is possible. I might have the commands wrong though. I'm just looking for confirmation that this is a viable option (I'll fix the commands proper later).

mediamogul

@hansolo77 said in XBOXDRV Guidance Needed:

Have you managed to map any "shifted" button combinations?

Sure. I actually have all my emulators and ports mapped to exit out by pressing 'Select+Start'.

I might have the commands wrong though.

Your instincts are in fact right on the money. Also, if you should ever need to map this functionality to an emulator/port that uses a key combination to exit (let's say 'ctrl+q'), then the formatting is no more difficult than:

--ui-buttonmap back+start=KEY_LEFTCTRL+KEY_Q

hansolo77

So this will still work even I have those buttons mapped to something else individually? Awesomesauce!

mediamogul

@hansolo77

yesireebobbyjimbo.

hansolo77

Grumble Grumble

@mediamogul

I hate opening up old threads, but it looks like I'm back into this whole XBOXDRV again. Turns out, I'm having issues where the RunCommand menu won't trigger with my Xbox controller on any of the systems I configured in the runconmmand-onstart.sh file. To counteract this, I tried adding a mapping inside the if/then statements to include the Xbox controller. But that doesn't work. I wonder if it's a mapping issue, and not necessarily a driver issue. I just did a simple cut and paste without really thinking about it.

For starters, I'm having trouble with NES. Originally, I only had the Xbox controller, and it sent over proper autoconfigs from EmulationStation into RetroArch. I could also access the RunCommand menus with it just fine. Then I added the XboxDRV into the mix to use the original NES controllers. While they worked fine with the remapping, I lost the ability to access the RunCommand. This might be due to the re-working of my plugs on the Pi, and having to move them around. Right now, I can navigate ES, RetroArch, and play games with my Xbox Controller, but I can't access the RunCommand. If I attach an NES controller, I can access the RunCommand, but then I can't navigate inside it, nor does the controller work inside a game. The only way I can navigate RunConmmand is by using a keyboard, after triggering it from the NES controller.

Sounds confusing.

Xbox Controller - Works in ES, Doesn't Trigger RunCommand, Doesn't work in RunCommand, Works in RetroArch/Games
NES Controller - Works in ES, Triggers RunCommand, Doesn't work in RunCommand, Doesn't work in RetroArch/Games
Keyboard - Works in ES, Triggers RunCommand, Works in RunCommand, Works in RetroArch/Games

Perhaps you can take a look and help me? :)

Example from runcommand-onstart.sh :

if [ "$1" = "nes" ]
then
sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv > /dev/null 2>&1 \
    --evdev /dev/input/by-id/usb-Â©Microsoft_Xbox_360_Wireless_Receiver_for_Windows_E1594E70-event-joystick \
    --detach-kernel-driver \
    --silent \
    --force-feedback \
    --deadzone-trigger 15% \
    --deadzone 4000 \
    --mimic-xpad \
    --dpad-as-button \
    --evdev-absmap ABS_X=x1,ABS_Y=y1,ABS_RX=x2,ABS_RY=y2,ABS_Z=lt,ABS_RZ=rt \
    --evdev-keymap BTN_SOUTH=a,BTN_EAST=b,BTN_NORTH=x,BTN_WEST=y,BTN_TL=lb,BTN_TR=rb,BTN_THUMBL=tl,BTN_THUMBR=tr,BTN_MODE=guide,BTN_SELECT=back,BTN_START=start,BTN_TRIGGER_HAPPY3=du,BTN_TRIGGER_HAPPY4=dd,BTN_TRIGGER_HAPPY1=dl,BTN_TRIGGER_HAPPY2=dr \
    --ui-buttonmap x=KEY_X,a=KEY_C,b=KEY_V,lb=KEY_A,Y=KEY_S,rb=KEY_D \
    --ui-buttonmap guide=KEY_B,start=KEY_ENTER,back=KEY_ESC \
    --ui-buttonmap du=KEY_UP,dd=KEY_DOWN,dl=KEY_LEFT,dr=KEY_RIGHT \
&
sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv > /dev/null 2>&1 \
    --evdev /dev/input/event3 \
    --detach-kernel-driver \
    --device-name "NES Pad Player 1 (xboxdrv)" \
    --evdev-absmap ABS_X=x1,ABS_Y=y1 \
    --evdev-keymap BTN_TRIGGER=a,BTN_THUMB=b,BTN_THUMB2=back,BTN_TOP=start \
    --dpad-only \
    --ui-axismap x1=KEY_LEFT:KEY_RIGHT,y1=KEY_UP:KEY_DOWN \
    --ui-buttonmap start=KEY_T,back=KEY_E,b=KEY_B,a=KEY_A \
&
sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv > /dev/null 2>&1 \
    --evdev /dev/input/event4 \
    --detach-kernel-driver \
    --device-name "NES Pad Player 2 (xboxdrv)" \
    --evdev-absmap ABS_X=x1,ABS_Y=y1 \
    --evdev-keymap BTN_TRIGGER=a,BTN_THUMB=b,BTN_THUMB2=back,BTN_TOP=start \
    --dpad-only \
    --ui-axismap x1=KEY_G:KEY_H,y1=KEY_I:KEY_J \
    --ui-buttonmap start=KEY_LEFTSHIFT,back=KEY_RIGHTSHIFT,b=KEY_M,a=KEY_K \
&
fi

I checked the input devices, and can confirm that even though I moved their locations physically on the Pi, the evdev /dev/input/device ## is stll the same.

hansolo77

DERP - I think the problem with the controller INSIDE a game might be because I had to restore the original default retroarch.cfg file because the latest update to RetroArch was broke. GRR now I have MORE work to do. :(

mediamogul

@hansolo77

Good to see that you nailed down what the problem was. Half the time that's the hardest part.

hansolo77

@mediamogul Yeah, but I'm not much closer now than I was a couple hours ago. Back to the old starting grounds.

mediamogul

@hansolo77

My memory on this is a bit wobbly, but I believe I've always had trouble with xboxdrv mappings triggering and navigating the Runcommand window and I just used my little wireless keyboard for these occurances. Was this something that was previously working for you?

Keep in mind that the Runcommand window's control scheme is limited to up, down, left and right, as well as 'A' on a standard controller and up, down, left and right, as well as 'Enter' on a keyboard. If the xboxdrv mapping differs from these two schemes, it's unlikely to work.

hansolo77

@mediamogul I thought I had it working, but I could be mistaken. I don't really need to get into the RunCommand window, other than when I need to try an experiment with an alternative LibRetro core. Realizing I couldn't do it with my Xbox controller led me to discover that it works with an NES controller. But even then, navigating doesn't work, or at least, not correctly. I press up on the NES controller, and the selector scrolls down. None of the A/B/Start buttons work. It's a bummer for sure. I guess there's no happy solution. I'm looking at "KEYBOARD ONLY" for RunCommand navigation, and "ORIGINAL CONTROLLER" (not Xbox) for triggering it.

mediamogul

@hansolo77

It sounds like a mapping issue that may originate from the base xboxdrv controller map, where you might have accidentally mapped the physical 'Up' button to the virtual 'Down' button on the simulated xbox controller that xboxdrv creates. If this is so, when you then mapped 'Up' inside of Emulation station, it would set the 'Down' direction as being 'Up', which would work fine in all of the RetroArch emulators, but still be read as 'Down' in any software that doesn't use the configuration that ES created, such as the Runcommand menu. Of course, it's just a guess. These types of issues can be a bit like untangling Christmas tree lights.

hansolo77

Well, I started off today with NOTHING working. Now I'm back to at least the NES controllers working correctly through XboxDRV. It's the strangest thing. I still can't do much inside of RunCommand other than press UP to go DOWN. Not sure what that's all about. But I also can't do the START+SELECT to exit a game with the NES controller. I think it has to do with the SELECT button not registering in RetroArch as the hotkey.

Is there a way to override a key mapping per emulator? I know, that's a stupid question. But it seems like if I'm using XBOXDRV, there's no way to access the Controller Remap functionality for RetroArch. Or is there? I think I need to experiment more. Maybe it works like it's supposed to, but I have the SELECT button mapped wrong.

mediamogul

@hansolo77 said in XBOXDRV Guidance Needed:

But it seems like if I'm using XBOXDRV, there's no way to access the Controller Remap functionality for RetroArch. Or is there?

It should work all the same. RetroArch should map the simulated XBox controller to it's own 'RetroPad' and allow it to be remapped from the GUI just like anything else. Even if you're keymapping, RetroArch should map those keys to it's 'RetroPad' so long as they correspond to the keyboard controls you set in Emulation Station.

hansolo77

OK new problem... :(

How can I get it to pull the USB EVENT by-id? I get it working like I want it, then turn the system off and back on, and its not working. Every time I reboot, the /dev/input/event## changes. Sometimes its /dev/input/event3 other times it's /dev/input/event4. So to get around that with my Xbox controller way back with SORR, I set it to use /dev/input/by-id. The problem is that the controller is one of 2, and the event-joystick only offers 1 choice. When I evtest that, it only gives me the keys for Controller 2. :( UHG!

mediamogul

@hansolo77

Your controller's ID can be discovered with ls /dev/input/by-id/. However, if it doesn't have an ID, you can also call out to the USB path where you know the controller is. For example, by adding:

--evdev /dev/input/by-path/platform-3f980000.usb-usb-0:1.2:1.0-event-joystick

you're telling xboxdrv to map the controller in the upper, left USB port on a Pi 3. To discover the other path listings, plug a controller into whichever port you're looking to use and type ls /dev/input/by-path/.

hansolo77

I am figuratively pulling my hair out. Because I wasn't getting anywhere, I decided to start completely over. I deleted all the controller config files that RetroArch uses. I then disconnected the USB hub that the Mayflash Sega/Atari adapter and Raphnet NES adapter were connected to. I then replaced the retroarch.cfg file with the default. I then went into the RetroPie-Setup scripts and triggered the ES function to reset ALL controllers (removing them and prompting for a re-configure). That should put me back to bare minimum with no configured controllers right? Well...

With everything still disconnected, except for the Xbox controller, I turned the machine off then back on. ES prompted for input. I configured ONLY the Xbox controller. I then tried to load up a game. The game loads, but none of the controls do. WTF. OMG I can't believe it. Not even the USB keyboard I have is being recognized by RetroArch.

This is crazy. I'm restoring my backup SD card and just living with it the way it was. I can't figure out what's going on, and it's really upsetting me. With NOTHING connected, bare essentials, it should work with whatever is picks up is connected. It used to work fine until I updated RetroArch. Now I got nothing but trouble.

mediamogul

@hansolo77

I can definitely relate. It's situations like your having where you almost start believing in poltergeists or gremlins. I hope it works out. Just tag me in if you decide to give it another go down the road.