![]() ![]() However the analog readings are returned to the program by the Joystick functions, I think that PureBasic compiler gamepad support maps the right analog stick values into unexpected registers. Looking at how your code performs Regenduft, I would consider it a bug only if there was no way provided to read both controller analogs for a given dual analog stick configuration. PureBasic's gamepad controller function default mappings should work to read such a controller or be adaptable to work with it. To be the PC standard controller if there ever was one. (and their newer very poor quality hardware F series controllers) ![]() The X-KIM (only after I push its MODE button) is the sole controller where I could get both analogs to properly register using that joystick tester.ĭifferent controller manufacturers have variances in the button and axis mapping positions. If InitJoystick() = 0 : MessageRequester("Fehler!", "InitJoystick() = 0") : End : EndIfĭrawAxisXYZ(i, JoystickAxisX(0,i,#PB_Relative),īananenfreak, I have tested three different gamepads with the above program: ![]() If OpenWindow(0, #PB_Any, #PB_Any, 270, 180, "Joystick-Test", #PB_Window_SystemMenu) = 0 If StartDrawing(WindowOutput(0)) Set the drawing output to our windowįrontColor(RGB(255,0,0)) Use the RED colour MessageRequester("Info", "Button 2 has been pressed", 0) MessageRequester("Info", "Button 1 has been pressed", 0) If Event = #PB_Event_CloseWindow : Quit = 1 : EndIfĭelay(20) a little delay (20 milli seconds -> 50 fps) MessageRequester("Information", "This will test the joystick in a window.", 0) MessageRequester("Error", "No joysticks are availables.", 0) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |