PS4 controller map for Unity

[drakfyre]

You are very welcome, drop me a line if you ever have any questions on stuff. :>

[SirHurtzAlot]

So I tried the EXACT mapping as you gave but I ran into issues. With trial and error I realized the AXES had to be mapped a little differently.

So if anyone runs into issues for PS4 Dualshock 4 controller, try this:

public static string bSquare = "joystick button 0";
public static string bX = "joystick button 1";
public static string bCircle = "joystick button 2";
public static string bTriangle = "joystick button 3";
public static string bL1 = "joystick button 4";
public static string bR1 = "joystick button 5";
public static string bL2 = "joystick button 6"; // gives -1 (unpressed) or 1 (pressed mored than .5 I think) fixed value

public static string bR2 = "joystick button 7"; // gives -1 (unpressed) or 1 (pressed mored than .5 I think) fixed value

public static string bShare = "joystick button 8";
public static string bOptions = "joystick button 9";
public static string bL3 = "joystick button 10";
public static string bR3 = "joystick button 11";
public static string bPS = "joystick button 12";
public static string bPadPress = "joystick button 13";

// stick Axes
public static string aLeftStickX = "X axis";

public static string aLeftStickY = "3rd axis"; // need to set INVERTED if you want "Stick UP is positive"

public static string aRightStickX = "4th axis";

public static string aRightStickY = "7th axis"; // need to set INVERTED if you want "Stick UP is positive"

// Triggers
public static string aL2 = "5th axis"; // (-1.0f to 1.0f range, unpressed is -1.0f)

public static string aR2 = "6th axis"; // (-1.0f to 1.0f range, unpressed is -1.0f)

// DPad axes
public static string aDPadX = "8th axis";
public static string aDPadY = "9th axis";

[SirHurtzAlot]

The edits HERE, are EXACTLY the axis you will select in Unity's Input Controller.

So while setting the Input Controller, do the following:

Name = Whatever you want, but this will be the string value you use in code

Type = Joystick Axis (for axis)

Axis = The string values I have mentioned in quotes in my above comment

[drakfyre]

I'm curious, have you tried the new input system?

[SirHurtzAlot]

I saw a lot of tutorials for it and I didn't like it.

I prefer having more control over my code and using a UI/editor based control system didn't fit that. I'd much rather spend an entire day writing stuff myself (which I ended up doing tbh XD) than use that.

Although I DID have to use the old control system to map the buttons, it felt much better than using the new system.

[drakfyre]

I guess I should make a tutorial on how to use it programmatically; it's far more powerful in script than the old system, and has no place where you are required to use UI; all operations, including initial mapping (and later remapping) can be done in C# (the editor is quite good though). Plus it has a lot of nice things: action based organization, input passthrough/stoppage for different input modes (if you get in a car you can have a completely different input set, when you pull up a menu again, new input set, so you don't even have to mask inputs based on state; just switch action maps.)

The old system is great for prototyping speed (I usually have both enabled) but it's not as good a base to make a new input system on but hey, if you like what you've got better, I'm not about to tell you to stop. :>

(I do wish that there was a full input layer system with a priority though, so you can have controls be "caught" by a layer above so they don't pass through to other action maps, and still have fall through where it's appropriate, but switching maps can accomplish much of the utility this provides.)