This bug report was migrated from our old Bugzilla tracker.

Reported in version: 2.0.3
Reported for operating system, platform: Windows 8, x86_64

Comments on the original bug report:

On 2014-06-27 16:47:27 +0000, wrote:

I've just implemented a rumble system for my xbox 360 controller support. Problem is that SDL_JoystickIsHaptic reports as the controller not having a force feedback system and initializing it without caring with SDL_HapticOpenFromJoystick also returns null.

I'm using the SDL2# binding by flibitijibibo but it shouldn't change anything since it's calling the same functions.

I came here because the mighty internets does not seem to know about this problem.

On 2014-06-28 09:46:53 +0000, wrote:

I want to add that the implementation I'm using has been tested by a friend and his playstation 3 controller combined with the xbox controller essentials suite (which I also used to test) was being detected and rumbled just fine. (so this is with an xbox driver)

Also my controller is not broken in any way and several games can utilize it's rumble features too.

On 2014-07-08 07:31:47 +0000, Sam Lantinga wrote:

Can you see if this is fixed in the latest snapshot?
http://www.libsdl.org/tmp/SDL-2.0.zip

Thanks!

On 2014-07-08 10:25:23 +0000, wrote:

Yeah it works perfectly now!
Also thanks for writing a detailed guide on how to build on visual studio, it's helped a lot =)

On 2014-07-08 23:57:08 +0000, Sam Lantinga wrote:

Great, you're welcome! :)

On 2014-08-15 01:05:59 +0000, Joe Sopko wrote:

I had the exact same bug, but the snapshot build sent does not fix my problem. Is there any additional information I can provide to help?

On 2018-08-06 21:20:20 +0000, Ryan C. Gordon wrote:

Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.