SDL Joystick Object release

You might need to load the txt at start of frame on the test above as well, forgot to say

Quote from NaitorStudios

Create a new mfa, add a counter, press a button and make notes of what button that is...
The controller mappings is just so it's consistent, so you don't have to worry about other controllers being completely different.

Oh ok thanks.
This is what i did in first place, but for the PS4 pad only, without loading the map.

Thanks again.

Quote from NaitorStudios

You might need to load the txt at start of frame on the test above as well, forgot to say

Yeah sure.

Ok buttons works as expected. Numbers are the same for PS4 and XBOX one controllers.

The d-pad is tricky.
For XBOX is a "Hat value", while for the PS4 is a button value (11-14), the same that i found before loading the map.

I'll try to make some "or" statements...

Nope. Only the first four buttons (0-3) are the same.
Everything else is mixed up. So i think the loaded map isn't working.

I can make the d-pad working with "hat value" (for xbox one) and button pressed (for PS4), but this is a workaround.

Quote from Pika

Nope. Only the first four buttons (0-3) are the same.
Everything else is mixed up. So i think the loaded map isn't working.

I can make the d-pad working with "hat value" (for xbox one) and button pressed (for PS4), but this is a workaround.

Try using the example MFA that comes with SDL Joystick - it should say which buttons are being pressed. Modify it to load the game controller map file first, if you need to.

It registering every input is most of the battle, though.

Quote from Phi

Try using the example MFA that comes with SDL Joystick - it should say which buttons are being pressed. Modify it to load the game controller map file first, if you need to.

It registering every input is most of the battle, though.

I tried it with and without map. Nothing changed. Buttons numbers are always the same.

I found out that the GUID is not in the map.
Is very similar to this:

Quote

030000005e040000ff02000000000000,Wired Xbox One Controller

with the last numbers being different (7200 instead of 0000).
So i tried to add it to the map copying the line, but nothin happens. Still the same button numbers...

Yeah, I have the same issue as Pika with adding mapping files, it doesn't seem to do anything...
The buttons are still mixed up, DS4 doesn't return hat values and instead returns them as buttons from (11-14), analogue joysticks centers are 128/128, instead of 0,0 (though I at least found a workaround with this one: Please login to see this attachment.)
Which means I had to make a manual system that changes a virtual configuration based on the controller connected. and like it works. But doesn't seem like the right thing to do especially with the many controllers available out there

I tried to load the global mapping file, nothing changed, tried to make my own mapping file, same thing, so i'm really confused with this action

Quote from Linky

I tried to load the global mapping file, nothing changed, tried to make my own mapping file, same thing, so i'm really confused with this action

On closer inspection, that's for SDL GameController classes, not SDL Joystick classes. I will see if I can write the A/C/E for interacting with the GameController part, but it may not be for a while.

Quote from Phi

On closer inspection, that's for SDL GameController classes, not SDL Joystick classes. I will see if I can write the A/C/E for interacting with the GameController part, but it may not be for a while.

Wrote 'em. Will be out of testing next week, hopefully - I have an intermittent hard drive I'm trying to duplicate first though.
Please login to see this link. can get it early!

Thanks for the update!

Testing feedback:
The ps4 controller touchpad pressed state is not recognized, cant tell if problem is in sdl itself or the extension but thought I'd let you know. It worked in previous versions.
Also for ps4 controller, hat0 (dpad) is not recognized, the dpad button IDs work, but hat0 does not.

Some questions:
Is loading a game controller database file needed on every frame, or is it enough to do once and it will keep in memory over frames?
Also is loading a game controller database file needed to recognize most common controller types or will they be recognized by sdl framework anyway?

The DarkEdif port of SDL Joystick is now renamed to SDL Object as of build 10.

First build (b10) is publicly released following a lot of testing on Clickteam Discord.
• Updated internal SDL library from v2.0.20 to v3.0.0
• Added Gamepad interface
• Added ports for Android, iOS, HTML5 and Mac
• Added rumble
• Added accelerometer/gyroscope (controller tilt/movement detection)
• Added object properties for changing SDL behaviour
• Added 8/16/32-dir and angle conditions/expressions
• Added 360-movement X/Y intensity calculations
• Added stick/dpad changed direction conditions - ext will trigger when changed, you don't have to constantly check
• Added help file and example file
• Added controller touchpad
• Added controller battery power level reading
• Removed Joystick ball A/C/E (SDL2 only, was removed in SDL3)
• Fixed Fusion built-in keyboard delay/conflict - Control X should not be needed anymore
• Updated to DarkEdif SDK v18 - iOS fixes, Mac compatibility
• Fixed Nintendo Switch Pro conflicting with Steam - this was a Please login to see this link. fixed by SDL folks.

To grab it, y'all just need to be a Please login to see this link. (and testers got it free once testing completed).
$5 per platform you want.

What an impressive list of additions!

Quote from TechVision

What an impressive list of additions!

Thank yew. I had a bunch of CT users help test, and thought about how I would want it designed for x and y games; stuff like 360 movement calculations are built-in, you can get controllers not tied to a player object ignored, D-Pad and sticks can be 32/8-dir/360 angle converted, etc.
Actually started work on it before PkR did his latest update, but figured it was best to rename if we're having two variants being maintained, which is something I tried to prevent. I used the rename to rework the Joystick stuff that PkR had already done.

Quote from Phi

Thank yew. I had a bunch of CT users help test, and thought about how I would want it designed for x and y games; stuff like 360 movement calculations are built-in, you can get controllers not tied to a player object ignored, D-Pad and sticks can be 32/8-dir/360 angle converted, etc.
Actually started work on it before PkR did his latest update, but figured it was best to rename if we're having two variants being maintained, which is something I tried to prevent. I used the rename to rework the Joystick stuff that PkR had already done.

Great that the community can help with these sort of projects!

Will you release it on Clickstore as well?

Quote from TechVision

Will you release it on Clickstore as well?

Probably, but CS is a pain to write a page for. Otherwise, you can just message directly and pay with PayPal or something.

This is great, but one of the (quite many) reasons I jumped ship to Godot (which is 100% free!) was the lack of controller support - why hasn't this been a priority for Clickteam to resolve with a supported built-in solution? Isn't "stable support for a modern controller for video games" deemed important for a game engine?

Mac port?! So with this my fellow Mac gamers can actually play my games with controller support?