SDL_HINT_JOYSTICK_HAPTIC_AXES(3)

✨ NAME ✨

okay so bestie, this is SDL_HINT_JOYSTICK_HAPTIC_AXES — a variable holding a whole little list of devices and how many haptic (that's force feedback, the rumbly stuff 🫨) axes each one should have turned on. It's giving "guest list but for vibrations" 💅

---

🌸 SYNOPSIS 🌸

#include <SDL3/SDL_hints.h>

#define SDL_HINT_JOYSTICK_HAPTIC_AXES "SDL_JOYSTICK_HAPTIC_AXES"

---

🎀 DESCRIPTION 🎀

So the string format is literally a comma separated list of USB VID/PID pairs written out in hexadecimal form, and then plus the number of desired axes you want. Like, for example:

0xAAAA/0xBBBB/1,0xCCCC/0xDDDD/3

See the pattern? VID/PID/how many axes, comma, repeat. iykyk 💖

This hint also supports a "wildcard" device 🧚 — and no cap, what that does is it sets the number of haptic axes on all initialized haptic devices that weren't defined explicitly in this hint. The catch-all bestie:

0xFFFF/0xFFFF/1

⚠️ Important vibe check: this hint should be set before a controller is opened. Timing matters, bestie, don't be late 🙈

Also, the number of haptic axes won't exceed the number of real axes actually found on the device. So like, don't ask for more than the device physically has, it's not going to manifest extra motors for you ✨

---

🌈 AVAILABILITY 🌈

This hint has been available since SDL 3.2.5. Periodt. 👑

---

That's the whole thing, and it came to you straight from Simple Directmedia Layer, version SDL 3.4.18 — the SDL_HINT_JOYSTICK_HAPTIC_AXES(3) page, no less. Go forth and rumble responsibly, my love 🦋💜