`JoyDeviceEvent`'s `SDL_EVENT_JOYSTICK_ADDED` `which` field does not refer to a `SDL_JoystickID` about sdl HOT 9 CLOSED

Even when calling SDL_GetGamepadInstanceID after the controller is opened would for example output 1, but when consuming the remove event I get 0x8BCBD361 from which

from sdl.

For SDL 2.0 this was intentional design. For SDL 3.0 we've rethought that, and it's an instanceID everywhere.

from sdl.

For SDL 2.0 this was intentional design. For SDL 3.0 we've rethought that, and it's an instanceID everywhere.

Well this doesn't appear to be the case.

SDL_EVENT_JOYSTICK_ADDED gives me 0x01, whilst removed gives me 0x8BCBD361

from sdl.

For SDL 2.0 this was intentional design. For SDL 3.0 we've rethought that, and it's an instanceID everywhere.

Could you let me know what I'm doing wrong here? Instance id appears to still be index on added

from sdl.

From debugging my application, this is what it currently looks like:

SDL_JoystickID[] joysticks = SDL_GetJoysticks();
for (SDL_JoystickID jid : joysticks) {
	LOGGER.info("Controller discovered: {}", jid.intValue()); // Controller discovered: 1
}

SDL_Event event = new SDL_Event();
while (SDL_PollEvent(event)) {
	switch (event.type) {
		case SDL_EVENT_JOYSTICK_REMOVED -> {
			SDL_JoystickID jid = event.jdevice.which;
			LOGGER.info("Controller removed: {}", jid.intValue()); // Controller removed: -1818745232
		}
	}
}

This very clearly shows the problem here

from sdl.

The ID I'm seeing is 3, which is correct. What operating system and controller are you using?

from sdl.

Windows 11 with a Dualsense Controller. No additional software

from sdl.

Yeah, the ID is still 3 here when using a DualSense controller, both over USB and Bluetooth. I'm not sure what's happening here, other than maybe the memory layout doesn't match between C and whatever language you're using?

from sdl.

It was indeed a misaligned struct, sorry for bothering you with this.

from sdl.