Introduction

The ButtonMap on the Xbox360GamePad allows for the Keyboard to simulate input for an Xbox360GamePad. By default this value is null, therefore the Keyboard will not simulate any input. Setting this value to a non-null value will enable keyboard simulation.

Code Example

The following example sets up a button map for the keyboard:

Microsoft.Xna.Framework.Input.KeyboardButtonMap buttonMap = new Microsfot.Xna.Framework.KeyboardButtonMap();

buttonMap.LeftAnalogLeft = Keys.Left;
buttonMap.LeftAnalogRight = Keys.Right;
buttonMap.LeftAnalogUp = Keys.Up;
buttonMap.LeftAnalogDown = Keys.Down;

buttonMap.A = Keys.A;
buttonMap.B = Keys.S;
buttonMap.X = Keys.Q;
buttonMap.Y = Keys.W;

InputManager.Xbox360GamePads[0].ButtonMap = buttonMap;

Introduction

The ButtonDown method returns whether a button is currently being held down. This will be false if the player is not pushing the button, and it will return true every frame that the button is pressed.

Code Example - Checking Buttons

The following code shows how to perform logic if the player is holding the A or B buttons on the Xbox360GamePad:

Add the following using statements:

using FlatRedBall.Input;

Later, perform the checks:

 var gamepad = InputManager.Xbox360GamePads[0];
 if (gamepad.ButtonDown(Button.A))
 {
     // do something when the A button is down
 }
 if (gamepad.ButtonDown(Button.B))
 {
     // do something when the B button is down
 }
 if(gamePad.ButtonDown(ButtonPosition.FaceLeft))
 {
     // do somethign when the left button is down, which could be X or Y
 }
 

Code Example - Checking DPad

The DPad on the Xbox360GamePad acts as four separate buttons. Therefore, each direction can be independently checked just like buttons. For example, the following code moves a character according to the left and right DPad.

var gamePad = InputManager.Xbox360GamePads[0];
if(gamePad.ButtonDown(Xbox360GamePad.Button.DPadRight))
{
    PlayerInstance.XVelocity = 100;
}
else if(gamePad.ButtonDown(Xbox360GamePad.Button.DPadLeft))
{
    PlayerInstance.XVelocity = -100;
}
else
{
    PlayerInstance.XVelocity = 0;
}

Code Example - Checking All Buttons

Buttons are represented by enumerations which can be looped through to check. The first enumeration value is 0, and the last value in the enumeration is Button.LeftStickAsDPadRight. Therefore, the following loop will check all buttons:

for(int i = 0; i < (int)Xbox360GamePad.Button.LeftStickAsDPadRight + 1; i++)
{
  if(gamePad.ButtonDown( (Xbox360GamePad.Button)i))
  {
    // This button is down, do something
  }
}

Introduction

ButtonPosition can be used to reference a button based in its physical position rather than by letter. Referencing a button by position can be useful if players are playing your game with gamepads which do not necessarily position their buttons identically.

For example, consider the A, B, X, and Y button positions on the Xbox and Switch controllers.

You may want your game to use the button positions rather than specific button letters when assigning input to your player.

Code Example - Getting Button by ButtonPosition

Entities typically use IPressableInput instances to control actions like jumping. Rather than inspecting the gamepad type, games cna use the ButtonPosition to assign input. For example, the following code might be used to assign the JumpInput:

// The following code assumes JumpInput is a property of type IpressableInput:
this.JumpInput = gamepad.GetButton(ButtonPosition.FaceDown);

Introduction

The ButtonPushed method returns whether a particular button was pushed. A "push" is defined as occurring when a button is not down the previous frame, but is down the current frame.

Code Example - Checking ButtonPushed

The following code might be used to cause an Entity to jump when the A button is pushed:

if(InputManager.Xbox360GamePads[0].ButtonPushed(Button.A))
{
   this.Jump();
}

Alternatively check the ButtonPosition.

if(InputManager.Xbox360GamePads[0].ButtonPushed(ButtonPosition.FaceDown))
{
   this.Jump();
}

Introduction

The Deadzone property can be used to address drift which can occur due to analog stick hardware reporting near-zero values, or due to the user unintentionally pushing the analog slightly in an undesired direction. By default, Xbox360GamePads use a 0.1f Deadzone value. The details of how the Deadzone property is applied can be found in the DeadzoneType page.

Introduction

The ControlPositionedObject method is a shortcut method which can be used to quickly add control logic for PositionedObjects using a Xbox360GamePad. The ControlPositionedObject method modifies the Velocity values of a PositionedObject. Therefore, consider the following:

• Acceleration will not have any impact on a PositionedObject that is being controlled by ControlPositionedObject

• ControlPositionedObject sets Velocity even if the left analog stick is not being touched (it will set it to 0).

• ControlPositionedObject on Entities which contain shapes will break CollideAgainstBounce calls since CollideAgainstBounce modifies velocity, but the modified velocity will be overridden by ControlPositionedObject. If using CollideAgainstBounce, consider using ControlPositionedObjectAcceleration.

• ControlPositionedObject provides control for X, Y, and Z (using the shoulder buttons).

Note: ControlPositionedObject is a method which can be very useful for new programmers, for prototypes, and for simple games. However, most games require more custom controls over their objects. Therefore, you may find that you will need to replace ControlPositionedObject with custom movement code as your project expands. If so, don't worry - you're not doing anything wrong.

Code Example

Assuming MyEntity is a valid PositionedObject instance:

const float magnitude = 10;
InputManager.Xbox360GamePads[0].ControlPositionedObject(MyEntity, magnitude);

Implementation Details

The following code is the code used in the engine to implement ControlPositionedObject. You can use and modify this code if you'd like to customize how the logic is applied:

       public void ControlPositionedObject(PositionedObject positionedObject, float velocity)
       {
           positionedObject.XVelocity = this.LeftStick.Position.X * velocity;
           positionedObject.YVelocity = this.LeftStick.Position.Y * velocity;

           if (ButtonDown(Button.LeftShoulder))
               positionedObject.ZVelocity = velocity;
           else if (ButtonDown(Button.RightShoulder))
               positionedObject.ZVelocity = -velocity;
           else
               positionedObject.ZVelocity = 0;
       }

Introduction

The CreateDefaultButtonMap method is a method which creates a button map for the calling Xbox360GamePad. This is a quick way to bind Keyboard keys to the Xbox360Controller - especially as a fallback during development if an Xbox360 game pad is not connected. For more information on creating custom button maps, see the Xbox360GamePad ButtonMap page.

Button map keys

The CreateDefaultButtonMap method performs the following logic internally:

  this.ButtonMap = new KeyboardButtonMap();
  
  ButtonMap.LeftAnalogLeft = Keys.Left;
  ButtonMap.LeftAnalogRight = Keys.Right;
  ButtonMap.LeftAnalogUp = Keys.Up;
  ButtonMap.LeftAnalogDown = Keys.Down;
  
  ButtonMap.A = Keys.A;
  ButtonMap.B = Keys.S;
  ButtonMap.X = Keys.Q;
  ButtonMap.Y = Keys.W;
  
  ButtonMap.LeftTrigger = Keys.E;
  ButtonMap.RightTrigger = Keys.R;
  ButtonMap.LeftShoulder = Keys.D;
  ButtonMap.RightShoulder = Keys.F;
  
  ButtonMap.Back = Keys.Back;
  ButtonMap.Start = Keys.Enter;

Modifying the default ButtonMap

You can modify the ButtonMap after it's been created:

Xbox3630GamePad gamePad = FlatRedBall.Input.InputManager.Xbox360GamePads[0];
gamePad.CreateDefaultButtonMap();
// now reassign the A button
gamePad.A = Keys.Q;

For more information, see the ButtonMap page.

Introduction

Xbox360GamePad and Gamepad Hardware

The name Xbox360GamePad exists for historical reasons - XNA originally only exposed support for Xbox36 controllers. Modern versions of FlatRedBall provide support for a variety of hardware including:

• Xbox360 and Xbox One controllers

• Switch Pro controllers

• USB Gamecube controllers

• Playstation DualShock

• General PC controllers

Detecting Button Presses

Detecting Connected Gamepads

The following code reports the number of game pads connected at a given time:

Using the Analog Sticks

The Xbox360GamePad provides two analog sticks:

• LeftStick

• RightStick

Using a Keyboard as a Game Pad

Vibrations

The following code sets the vibration on the game pad:

Frequency of Updates

Platform Support

The Xbox360GamePad name orignally comes from the fact that XNA supported Xbox 360 controllers. Despite its name, the Xbo360GamePad class can be used on most FlatRedBall platforms. As of the time of this writing, the following platforms and hardware are supported.

• Desktop GL: Xbox 360 controllers, Xbox One controllers, Switch Pro controllers, USB Gamecube controllers, PlayStation DualShock, Generic PC controllers

• Desktop XNA: Xbox 360 controllers, Xbox One controllers

• Android: Bluetooth and wired controllers

• iOS: Untested

Introduction

The FakeIsConnected property can force a Xbox360GamePad's IsConnected property to true whether a physical controller is actually connected or not.

Common Usage

Some game logic may depend on the number of connected Xbox360GamePads. For example, a game which supports a local versus mode may enable one character-selection cursor for each connected Xbox360GamePad. You may not have access to four Xbox controllers, but you may want to still test this functionality. The FakeIsConnected enables this.

Introduction

The DeadzoneType property controls how the Deadzone value is applied on an Xbox360GamePad. By default Radial DeadzoneType is used.

Code Example

The following code sets the first Xbox360GamePad to use a Cross deadzone with a 0.15 value:

InputManager.Xbox360GamePads[0].Deadzone = .15f;
InputManager.Xbox360GamePads[0].DeadzoneType = DeadzoneType.Cross;

Deadzone Types

Radial

The Radial deadzone type treats the position of the analog stick as (0,0) if the position reported by the hardware is within a circle centered at (0,0) with the Deadzone value used as the radius. Visually, this means that any value within the red area would be reduced to (0,0).

Radial deadzones are recommended for top-down (four-way directional) movement games.

Cross

The Cross deadzone type treats each axis independently regardless of the value of the other axis. In other words, if the absolute value of X as reported by the hardware is smaller than the Deadzone value, then X will be reported as 0. Visually, this creates a cross deadzone area as shown in the following diagram:

Cross deadzones are recommended for platformer games and games where players may want to move perfectly along a particular axis.

Introduction

The GamepadLayout property returns the type of layout that the Xbox360GamePad returns. This property is set according to the ID and Name reported by the gamepad. Note that this is not always accurate as some manufacturers reuse IDs and Names for different gamepads. If you have a gamepad which is incorrectly reported, please report this in the FlatRedBall chat or create a pull request in the Xbox360GamePad.cs file. Note that the InputManager includes an array of Xbox360GamePad objects for historical and convenience reasons - even controllers which are not Xbox360 (or Xbox One) controllers will appear in this list, such as PlayStation Dual Shock controllers.

Code Example - Selecting a GamePad Icon According to GamepadLayout

The following code could be used to select an icon for a gamepad based on the gamepad layout.

var gamepad = InputManager.Xbox360GamePads[0]
switch(gamepad.GamepadLayout)
{
    case GamepadLayout.Xbox360:
        SetIcon(Xbox360GamepadIcon);
        break;
    case GamepadLayout.SwitchPro:
        SetIcon(SwitchProIcon);
        break;
    case GamepadLayout.PlayStationDualShock:
        SetIcon(PlayStationDualShockIcon);

        break;
        // etc...
}

Introduction

The IgnoreButtonForOneFrame method can be used if multiple objects are watching for a particular button to be pushed, but the first one that reacts to it should "consume" it so that no other objects get the button push. This method is very convenient because it does not require any additional logic aside from simply calling this method when consuming the button event.

Code Example

In this example we have some if statements which increment a number according to button pushes. The first check for the A button will call IgnoreButtonForOneFrame on the A button. The first check for the B button will not. The result is that A will increment the call count by 1, while B will increment the call by 2.

Add the following using statement:

using FlatRedBall.Input;

Add the following at class scope:

int mCount = 0;

Add the following in Update:

Xbox360GamePad gamePad = InputManager.Xbox360GamePads[0];

// Do our first checks.  
if (gamePad.ButtonPushed(Xbox360GamePad.Button.A))
{
    mCount++;
    gamePad.IgnoreButtonForOneFrame(Xbox360GamePad.Button.A);
}

if (gamePad.ButtonPushed(Xbox360GamePad.Button.A))
{
    mCount++;
}

if (gamePad.ButtonPushed(Xbox360GamePad.Button.B))
{
    mCount++;
}

if (gamePad.ButtonPushed(Xbox360GamePad.Button.B))
{
    mCount++;
}

FlatRedBall.Debugging.Debugger.Write(mCount);