Of course I'm still very pleased with the progress zzattack has made so far in adapting the xpad driver. I have tried both 5. However, I tried 5. Anything I can do to help investigate the issue? Awesome zzattack , thanks for working on this!
I'm excited about this ticket. I also have wireless xbox controller and a xbox one controller if you want me to do some testing. I have a wireless and a wired XBox controller on for my Pi2. If there is anything to test I would like to help! Please search. Skip to content. Star 1. New issue. Jump to bottom.
Xbox wireless controller not working anymore since OE 3. Copy link. I'm new to openelec. But I am having the same issue. I can't see the option to enable it. Where can I find this setting? Thanks for the help! Enable Joystick support Is the fact that I'm running it on Raspberry Pi have anything to do with it?
Just to be clear, I am using the xbox wireless controller. Any help, insight is greatly appreciated! Thanks in advance! Hi, I'd like to update this bug report! Apparently the controller is recognized from the beginning on see line and subsequent ones; at this time I've pressed some buttons on the controller which got reported in the log file but nothing happened. As stated above the controller doesn't work until I switch joystick and gampad support off and on again.
After having done this it works see line and subsequent ones; I could navigate with the controller from there on i. If you're wondering about the log entries of the controller button presses: Every button press results in two log entries, one for pressing the button down and one for releasing the button again. Will be able to test on Thursday night, hopefully. Tonight I found some time to test zzattacks newest build. Here are my findings: The blinking LED ring problem seems to be basically fixed yeah!
It occured right after the first bootup after updating to the new build. I gotta add that other navigation methods were affected too at this point i.
Then I performed a cold reboot and everything worked like a charm. Powering it on again doesn't help: It's not working at all and the LEDs are blinking again! This happens in a reproducible manner after every warm reboot and also if I manually power the controller off and on while openelec is running. But if I manually switch off the controller, then perform a warm reboot and afterwards power the controller on again it works fine same applies if I switch it off manually during a warm reboot.
A probably closely related issue I observed: After shutting down my openelec system the controller stays on as well as the receiver which obviously still gets power through the USB port.
I gotta add that I usually completely disconnect my openelec system from current by a separate power switch when not using it — so I normally don't run into this bug.
It seems to me that some kind of not resetting the controller properly after losing the connection to the controller and while shutting down the system lies at the root of the above decribed problems. Thanks for the reports, I'll debug and reply in more detail sometime this weekend!
Update valve's xpad rework patch Hey fellas, I've skimmed the thread and I have a few questions; will wireless Xbox controllers be natively supported from now on? Cheers and thank you for the hard work. As for multiple controllers, I can verify that this custom build works well with my setup: One wired xbox controller, original One wireless ditto When the wired is connected it takes position 1, and connecting the wireless gives it position 2 just as expected.
I haven't tested with more than two controllers. Thanks The builds are generic x Will they work on the Pi? I"ll add a build for ARM. I allow to create an account. When you login first time using a Social Login button, we collect your account public profile information shared by Social Login provider, based on your privacy settings. We also get your email address to automatically create an account for you in our website. Once your account is created, you'll be logged-in to this account. Disagree Agree.
Notify of. I agree to the Privacy Policy. The comment form collects your name, email and content to allow us keep track of the comments placed on the website.
Please read and accept our website Terms and Privacy Policy to post a comment. Inline Feedbacks. Hooray, Windows can finally see the controller. We fire up the control panel tool for gaming devices and confirm that all buttons and axes work. XBMC even helpfully includes keymappings for the xbox controller by default! We should be pretty much plug-and-play from here! I open up XBMC and…. The controller does nothing. I smash all the buttons, and still nothing. This means that XBMC can see the controller.
So I copied one of them and pasted it into the user keymappings folder. And the right analog stick was working as a volume control though the axis was inverted. The next task was getting the D-pad to work for navigating menus. Let me take this time to say that like most people who grew up with Nintendo controllers, the d-pad on the Xbox controller is a source of scorn and hatred.
At this point I turned on debugging in XBMC and then proceeded to methodically press every button on the controller and swivel each stick axis exactly once. This worked great for the buttons but none of the axis data showed up in the debugger at all. Only in the process of writing up this post did I find someone who had actually taken the time to map out which buttons, hats, and axes where which.
I wish I had found that post last night, it would have saved me about two hours. And I will say, navigating with the Xbox controller feels nice, much nicer than breaking out the clunky keyboard.
0コメント