We have a big and important, but simple request. We’ve reworked the handling of the joysticks and gamepads in Castle Game Engine, with a lot of new features that include serious improvement of joysticks API, access to a huge joysticks database by SDL2 with almost 800 of joysticks definitions, autodetection of joysticks, detection of connection/disconnection of joysticks, etc.
However, because we have very limited access to hardware, we are unable to test how well those new features work. And therefore we need your help to test if everything is working as expected on different hardware joysticks/gamepads. Many thanks to the people who already contributed their tests results!
You can download and build “joystick” project from “examples” in this fork:
https://github.com/eugeneloza-clean/castle-engine. If it's more convenient for you, there are precompiled binaries for Windows 64 bit and Linux 64 bit here:
https://drive.google.com/drive/u/1/folders/1PtBzsrCCE3UsrluY0brmLRSWUWlHZj3v.
If you have access to a hardware joystick or gamepad, please use this tool and tell us (here or in any other convenient way):
* Your joystick name and operation system (Linux or Windows)
* Name your joystick was detected in Castle Game Engine
* If your joystick was correctly autodetected (the joystick name as reported by the OS is shown above, the detected joystick layout is shown below)? If not, can you find your joystick in the list of joysticks and try using it?
* Did the axes and buttons on your joystick corresponded to the axes and buttons displayed in the tool?
Note, that the joystick image, names of the buttons and exact joystick layout may be different, but right stick must be right and upper button must be the upper one.
Thanks a lot!
Recent
