Game Development Stack Exchange is a question and answer site for professional and independent game developers. It only takes a minute to sign up.
Sign up to join this community
The com.badlogic.gdx.controllers.Controllers API only supports getting the input data (which works fine).
Is there a way to make my controller rumble/vibrate, possibly using some other classes?
I tried using the org.lwjgl.input.Controllers class, which supports this, but the controllers don't get indexed there and I can not access them.
Is there a way to make my controller rumble/vibrate, possibly using some other classes?
It's not a feature libGDX itself supports, and it seems unlikely (based on the discussion on the issue linked in the comments) to happen any time soon. You'll have to use third-party libraries.
Unfortunately most of those third-party libraries (like JXInput) map to the native XInput API to provide vibration (for 360 controllers), which means they don't function on non-Windows system. Regular JInput seems like it may be hampered by the same issue, and doesn't seem to expose vibration anyhow. There are native libraries like libstem_gamepad you could wrap, but they don't support vibration either.
With the caveat that I haven't really tried it, your best bet might be to use the Java binding for SDL, possibly only for the controller APIs, and try to leverage the haptic feedback API therein.
For using SDL with libGDX desktop, you can use Jamepad. It supports rumbling. There are wrappers for Jamepad to use it as a drop-in replacement for the libGDX controller implementation, for example gdx-controllerutils.
Now, a problem is that you can't trigger rumbling with the existing implementations: libGDX' controller interface just don't have a method for doing so. The task still to do is:
instanceof in your core code if you have an Controller implementing your interface and then rumbleBest was if the libGDX' controller interface would be extended. There are other methods lacking as well, for example requesting how many buttons and axis are present. Apparently, there is not much interest in the controller extension by the maintainers, so you are better off with an own solution described above.
