A gamepad related bug

[ara]

STK 0.9.3 is crashed because I pressed a right button in loading screen.

Call stack:

gamepad_device.cpp:GamePadDevice::resetAxisDirection:130
gamepad_device.cpp:GamePadDevice::processAndMapInput:249
device_manager.cpp:DeviceManager::mapGamepadInput:391
device_manager.cpp:DeviceManager::translateInput:469
input_manager.cpp:InputManager::dispatchInput:657
input_manager.cpp:InputManager::input:907
event_handler.cpp:GUIEngine::EventHandler::OnEvent:239
cirrdevicestub.cpp:irr::CIrrDeviceStub::postEventFromUser:226
cirrdevicewin32.cpp:irr::SJoystickWin32Control::pollJoysticks:411
cirrdevicewin32.cpp:irr::CIrrDeviceWin32::run:1564
irr_driver.cpp:IrrDriver::update:1758
main_loop.cpp:MainLoop::run:242
main.cpp:main:1805
exe_common.inl:__scrt_common_main_seh:283
BaseThreadInitThunk
RtlUserThreadStart

[Auria]

I have created a ticket to track this issue : https://github.com/supertuxkart/stk-code/issues/3840

[Auria]

Oops I missed the version number (0.9.3), could you please try the latest version (0.10-rc1) to see if it still happens? https://sourceforge.net/projects/supert ... /0.10-rc1/

[ara]

This bug is still existed in STK 1.0 64-bit when I pointed left stick to right. I am using OS Windows 10 64-bit and a controller Xbox One S.

Call stack:

<no symbol available>
gamepad_device.cpp:GamePadDevice::resetAxisDirection:131
gamepad_device.cpp:GamePadDevice::processAndMapInput:214
device_manager.cpp:DeviceManager::mapGamepadInput:424
device_manager.cpp:DeviceManager::translateInput:504
input_manager.cpp:InputManager::dispatchInput:666
input_manager.cpp:InputManager::input:963
event_handler.cpp:GUIEngine::EventHandler::OnEvent:248
cirrdevicestub.cpp:irr::CIrrDeviceStub::postEventFromUser:226
cirrdevicewin32.cpp:irr::SJoystickWin32Control::pollJoysticks:357
cirrdevicewin32.cpp:irr::CIrrDeviceWin32::run:1569
main_loop.cpp:MainLoop::run:550
main.cpp:main:2252
exe_common.inl:__scrt_common_main_seh:288
BaseThreadInitThunk
RtlUserThreadStart

[Auria]

Ok thanks for the report, I have added this info to the ticket, we'll see what we can find.
Everything works fine with gamepads on my end so it's not easy to understand what's going on