![snakebyte ps3 controller pc driver snakebyte ps3 controller pc driver](https://m.media-amazon.com/images/I/71YALZGF8dL._SL1500_.jpg)
* Thrustmaster Firestorm Wireless controller * Thrustmaster Firestorm Dual Analog Gamepad If not, then I'd be interested in knowing the brand of controller that is natively supported. If so, then it looks as if the PB gamepad command functionality will only support that subset of controllers without remapping.
![snakebyte ps3 controller pc driver snakebyte ps3 controller pc driver](https://bilder.afterbuy.de/images/NLRLNS/_aimg9223599L5vvSZ.png)
I don't have one of those annoyingly perverted form factor XBOX controllers to test,īut I am sure that someone reading this does,Īnd hopefully will let us know if both analogs are detected through the named axis functions. Perhaps the development team mapped the joystick readings XBOX style? If Microsoft gets their way, then the XBOX controller (with the physically offset analogs) will be the new emerging standard.
![snakebyte ps3 controller pc driver snakebyte ps3 controller pc driver](https://www.ewent.com/product/image/medium/pl3331_2.jpg)
It looks like you will have to ask for some user input in order to correctly set and read the axis mappings for any given gamepad. Just like I had to do in my Gamepad Button Trainer for the button mappings, 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)
![snakebyte ps3 controller pc driver snakebyte ps3 controller pc driver](https://cdn.shopify.com/s/files/1/0255/5101/1900/products/SB913471_snakebyte_PS4_GamePad_4_S_bubblegum_camo__03_1200x630.png)
MessageRequester("Information", "This will test the joystick in a window.", 0) MessageRequester("Error", "No joysticks are availables.", 0)