Logo

.ini [portable] | Fifa Button Data Setup

buttonDataSetup.ini buttonData.ini ) file is a configuration script used by the FIFA/FC series on PC to map physical controller inputs to standard in-game actions. It is primarily used to fix issues where third-party or older controllers have swapped buttons (like X/A being flipped) or non-functioning right analog sticks. File Structure & Core Syntax Each entry in the

file follows a specific hierarchical structure to define how a controller is recognized and mapped: AddController "[ID]" : Defines a new controller profile block. The ID (e.g., Controller_025 ) is an internal reference used by the game. AddAlias "[Device Name]"

: Lists the exact hardware names the game should match to this profile. Multiple aliases can be added for the same profile (e.g., "Generic USB Joystick" "Logitech Dual Action" AddMap [Physical_Input] [Game_Action]

: The core mapping command that links a hardware button or axis to a game function. Common Mapping Identifiers

The file uses specific naming conventions for both physical inputs and virtual game actions: PC_CONTROL_BUTTON Physical Button Analog Stick/Trigger (Left Stick), (Right Stick) POV_0_LEFT In-Game Action VB_AI_RS_UP (Skill Move) Menu/UI Action VB_FE_SELECT (Confirm), VB_FE_CANCEL Common Use Cases & Fixes Locating the File

: On modern Windows systems, the active setup file is typically found in Documents > FIFA [Year] Fixing Right Analog Stick

: Issues where the right stick doesn't register usually require re-mapping the values to the correct (Right Stick) directions. Swapped Buttons

: If your "A" button acts like "B", locate your controller's alias in the file and swap the mappings for the corresponding PC_CONTROL_BUTTON Porting Settings : You can often copy a working buttonDataSetup.ini

from an older FIFA version to a newer one to maintain custom mappings across game releases.

The buttonDataSetup.ini file is a core configuration file used by the PC versions of FIFA (now EA Sports FC) to map hardware inputs from generic controllers to the game's standardized "Virtual Buttons". 📂 File Location

The exact path depends on your game version, but it is typically found in one of these two locations:

Documents Folder: %USERPROFILE%\Documents\FIFA XX\buttonDataSetup.ini

Game Directory: Navigate to your installation folder (e.g., Local Disk (C:) > Program Files > EA Games > EA Sports FC 26) 🛠️ Configuration Structure

The file is divided into AddController blocks for specific hardware IDs. Each block uses three primary commands to define how your gamepad behaves: 1. Controller Identification

AddController "[Controller_Name]": Starts the definition for a specific device based on its system-reported name.

AddAlias "[Alias_Name]": Allows the game to apply these settings to multiple gamepads that use different names but the same hardware layout. 2. Mapping Commands

Every line within a controller block follows a specific mapping syntax: AddMap [Hardware_Input] [Virtual_Button] Hardware Input Example Virtual Button (VB) Equivalent PC_CONTROL_BUTTON02 VB_AI_A Pass / Select PC_CONTROL_BUTTON03 VB_AI_B Shoot / Cancel PC_AXIS_0_UP VB_AI_LS_UP Left Stick Up PC_POV_0_UP VB_AI_LDPAD_UP 🔧 Common Fixes & Customization

If your controller is acting "weird" (e.g., the right analog stick performs passes instead of skill moves), editing this file is often the only permanent fix.

Fixing Swapped Buttons: Locate your controller's block and swap the VB values. For example, if A and B are swapped, change PC_CONTROL_BUTTON02 to VB_AI_B and PC_CONTROL_BUTTON03 to VB_AI_A.

The "Default" Block: If your specific controller isn't listed, the game uses the AddController "Default" block at the bottom of the file. You can paste a working configuration from another device into this block to force compatibility.

Permission Issues: If changes don't save, right-click the file, go to Properties, and ensure Read-only is unchecked before editing. Check it again after saving if you want to prevent the game from resetting your custom mapping. 💡 Modern Alternatives

Since FIFA 23 and EA FC 24, manual .ini editing has become less common due to advanced software:

Steam Input: You can disable or enable "Steam Input" in the game's Steam properties to let Steam handle the mapping instead of the game's .ini file.

x360ce: This emulator creates a virtual Xbox controller, which the game recognizes natively, bypassing the need for manual .ini tweaks.

Help you identify your controller's specific name as recognized by Windows?

Walk through advanced analog stick calibration for the .ini file? Controller Console On pc have wrong Input In game - 7773089

The buttonDataSetup.ini file is a core configuration file used by the fifa button data setup .ini

and EA Sports FC series on PC to map physical controller inputs (buttons, axes, and d-pads) to in-game actions.

It is primarily used as a fix for unsupported generic controllers or to resolve issues like the right analog stick not working. 📂 File Location

Depending on your version of the game, the file is typically found in:

Documents Folder: \Documents\FIFA [Year]\buttonDataSetup.ini

Game Directory: Some older or modded versions may place it directly in the main installation folder. 🛠️ Common Usage & Fixes

The file allows the game to recognize "DirectInput" controllers by providing a specific mapping for each device's unique internal ID.

Right Analog Stick Fix: If your right stick doesn't perform skill moves, you often need a custom .ini file that correctly maps the RS (Right Stick) axes (e.g., PC_AXIS_2_UP VB_AI_RS_UP).

Generic Controller Fix: Many players download pre-configured buttonDataSetup.ini files to make cheap or generic USB gamepads behave like an Xbox controller.

Trigger Swapping: If L2/R2 are swapped with L1/R1, specific entries in this file can be edited to reassign the VB_AI_LT and VB_AI_RT values to the correct physical buttons. 📝 Structure of the .ini File

Each entry in the file follows a standardized block format for a specific controller model: Description AddController

Defines the controller's internal name (e.g., "Controller_025"). AddAlias

Lists the names the PC sees for that device (e.g., "Generic USB Joystick"). AddMap

Links a physical button (e.g., BUTTON01) to an in-game action (VB_AI_A). Example Mapping Entry:

AddMap PC_CONTROL_BUTTON01 VB_AI_A AddMap PC_CONTROL_BUTTON01 VB_FE_SELECT Use code with caution. Copied to clipboard

This maps the physical Button 1 to the "A" action in-game and "Select" in the menus. ⚠️ Alternative Modern Solutions

As of EA Sports FC 26, many players have moved away from manual .ini editing in favor of:

The buttonData.ini and buttonDataSetup.ini files are critical configuration components for legacy and modern PC versions of

(now EA Sports FC). These files serve as a translation layer between the raw input data of a hardware controller (DirectInput) and the virtual buttons recognized by the game engine. Core Function and File Location

Purpose: These files standardize input from various generic controllers (like Logitech, Saitek, or Hama) into a layout recognized by the game, which is primarily designed for XInput (Xbox) controllers. Common Locations:

Documents Folder: Often found in Documents\FIFA [Year] (e.g., Documents\FIFA 22).

Game Directory: In older titles, it may reside in the main installation folder or under a FIFASetup subfolder.

Specific File Names: Depending on the version, the file may be named buttonData.ini or buttonDataSetup.ini. Typical File Structure

The file is structured into blocks for different controller models. Each block contains:

AddController: A unique identifier for the device (e.g., "Controller_025").

AddAlias: Common names Windows uses to identify the hardware (e.g., "Logitech Dual Action").

AddMap: Specific lines that map a physical button code to a game action. VB_AI_: Mapping for in-match gameplay. VB_FE_: Mapping for menu navigation ("Front End"). Common Mapping Identifiers Action Code Virtual Button (Game) VB_AI_A Pass / Direct Action VB_AI_B Shoot / Cancel VB_AI_X Cross / Tackle VB_AI_Y Through Ball / Rush GK VB_AI_LB/RB Player Switch / Sprint VB_AI_LS_UP Left Stick Movement Up VB_AI_RS_UP Right Stick (Skill Moves) Up Common Troubleshooting & Fixes buttonDataSetup

Introduction

The .ini file is a configuration file used by FIFA to store button data for various controllers. By editing this file, you can customize the button layout, assign new functions to specific buttons, and even create custom controller profiles.

Prerequisites

Location of the .ini file

The location of the .ini file varies depending on your FIFA version and platform:

Structure of the .ini file

The .ini file consists of sections, each representing a controller profile. The profile sections are denoted by a header in square brackets [ ]. Each section contains key-value pairs that define the button mappings.

Basic syntax

Common sections and keys

Values

Example

[Default]
LStickX = 0.2
LStickY = 0.2
RStickX = 0.2
RStickY = 0.2
DPadUp = button_12
DPadDown = button_13
DPadLeft = button_14
DPadRight = button_15
FaceButton1 = button_0
FaceButton2 = button_1
FaceButton3 = button_2
FaceButton4 = button_3
LShoulder = button_4
RShoulder = button_5
LTrigger = button_6
RTrigger = button_7
View = button_8
Menu = button_9

Tips and best practices

Common use cases

buttonDataSetup.ini file is the architectural backbone of controller recognition in legacy FIFA titles (such as FIFA 11 through FIFA 17). It serves as a translation layer between raw hardware inputs and the game's internal command system. The Core Structure

The file is divided into specific controller profiles, each beginning with an AddController

declaration. A typical entry contains three critical components: Identifiers (

: This lists the various names the OS might assign to your hardware (e.g., "Logitech Dual Action" or "Generic USB Joystick"). Virtual Buttons (

: Maps buttons for "Artificial Intelligence" (actual gameplay like shooting or passing). : Maps buttons for the "Front End" (navigating menus). Physical Maps ( PC_CONTROL_BUTTON

: These link the virtual actions to physical hardware IDs. For example, AddMap PC_CONTROL_BUTTON01 VB_AI_A

tells the game that Button 1 on your controller is the "A" button for gameplay. Anatomy of a Controller Profile A common setup for a generic pad looks like this:

AddController "Generic USB Joystick" AddAlias "Generic USB" AddMap PC_CONTROL_BUTTON03 VB_AI_A ; Button 3 = Pass AddMap PC_CONTROL_BUTTON02 VB_AI_B ; Button 2 = Shoot AddMap PC_CONTROL_BUTTON04 VB_AI_Y ; Button 4 = Through Ball AddMap PC_CONTROL_BUTTON01 VB_AI_X ; Button 1 = Lob/Cross Use code with caution. Copied to clipboard Common Use Cases & Hacks Right Analog Stick Fix

: Many generic controllers fail to register skill moves. This is often solved by remapping (usually the right stick) to the correct VB_AI_RS_UP/DOWN/LEFT/RIGHT parameters in this file.

: You can often fix controller issues in newer demos or repacks by copying a working buttonDataSetup.ini

from an older version (like FIFA 16) directly into the new game's directory. Standardization

: The file allows the game to treat over 30 different legacy controllers from brands like Saitek, Thrustmaster, and Logitech as a standard input device. fifaConfig/buttonData.ini at master - GitHub

The buttonData.ini file is a configuration script used in older PC versions of A text editor (e

(such as FIFA 11 through FIFA 13) to manually map controller inputs. This is particularly useful for generic USB gamepads that the game doesn't natively recognize or that have swapped button layouts. Core Functionality

The file functions by creating a "profile" for your specific hardware. It uses several key commands to link physical controller buttons to in-game actions:

AddController: Defines the unique ID for a controller setup.

AddAlias: Lists the names of devices that should use this mapping.

AddMap: The actual logic that binds a hardware input (like PC_CONTROL_BUTTON01) to a virtual game action (like VB_AI_A). Basic Mapping Structure A typical entry in a buttonData.ini file looks like this:

AddController "Controller_Name" AddAlias "Your Gamepad Name" AddMap PC_CONTROL_BUTTON01 VB_AI_X // Mappings for face buttons AddMap PC_CONTROL_BUTTON02 VB_AI_A AddMap PC_AXIS_0_UP VB_AI_LS_UP // Left stick movement AddMap PC_POV_0_UP VB_AI_LDPAD_UP // D-Pad navigation Use code with caution. Copied to clipboard Useful Resources for Setup

If you are struggling with a generic controller, you can use pre-configured templates or tools to simplify the process:

Pre-made Configurations: You can find complete button mapping lists for dozens of different controllers on GitHub.

FIFA 13 Specific Setup: For users specifically on older versions, a dedicated setup file is available on GitHub-Gist.

Manual Downloads: You can view and download standard .ini templates from Google Docs.

XInput Emulation: If you prefer not to edit .ini files manually, many users recommend using the Linus Tech Tips Forum Guide for setting up x360ce, which tricks the game into seeing your controller as an Xbox 360 pad. Common Fixes

Swapped Triggers: If your RT and RB buttons are reversed, find the AddMap line for VB_AI_RT and swap its corresponding PC_CONTROL_BUTTON number with the one assigned to VB_AI_RB.

Right Stick Not Working: Ensure your right stick axes (e.g., PC_AXIS_2) are correctly mapped to VB_AI_RS actions in the file.

Do you need a specific mapping for a particular brand of controller, like Logitech or a generic PlayStation adapter? Button data setup file for FIFA 13 - Github-Gist

Select an option. Embed Embed this gist in your website. No results found. Learn more about clone URLs. Clone this repository at <

buttonDataSetup.ini file is a configuration file used by PC versions of FIFA (now EA Sports FC) to map physical controller buttons and axes to specific in-game actions. It is primarily used to troubleshoot issues with generic or older controllers that are not natively recognized by the game. File Location

The file is typically located in the game's user data folder in your Documents:

C:\Users\[YourUsername]\Documents\FIFA [Version]\buttonDataSetup.ini

: If the file is missing, you can create it manually by opening Notepad, pasting a configuration, and saving it with the extension. Structure and Content

The file consists of multiple controller profiles. Each profile follows a specific syntax to define the device and its mapping: AddController "[DeviceName]"

: Defines the start of a configuration for a specific device. AddAlias "[AlternativeName]"

: Lists other names the same device might be identified as by Windows. AddMap [PhysicalInput] [GameAction] : Links a physical button or axis to a game function. Common Mapping Codes Game Action (AI) Game Action (Menu) Description VB_FE_SELECT Pass / Confirm VB_FE_CANCEL Shoot / Back Lob / Crossing Through Ball VB_AI_LS_UP VB_FE_LS_UP Left Analog Movement VB_AI_RS_UP VB_FE_RS_UP Right Analog (Skill Moves) Common Fixes using buttonDataSetup.ini

Mistake #1: The Silent Mod Loader

Frostbite games do not automatically reload the INI file mid-game. You must completely restart the game (from Desktop) for changes to take effect.

The Syntax: Decoding the .ini Structure

Opening buttonDataSetup.ini in Notepad++ (avoid standard Notepad to prevent formatting errors) reveals a series of command lines. Here is a typical entry:

AddController "Controller_001"
AddMap PC_XBOX_ONE_ALT USB\VID_045E&PID_02D1&IG_00
AddAlias "GenericUSB"

Followed by button mappings:

AddButton PC_POV_0_LEFT , ALTERNATE , 1 , L2 , 4
AddAxis PC_AXIS_0_X , ALTERNATE , 1 , L_LEFT_ANALOG_X , 1.0 , 0.0 , 0.5 , 1.0 , 1.0

Step 2: Identify Your Controller’s RAW Input

Open the game and navigate to Controller Settings > Calibration. Note the button numbers when pressed. Alternatively, use free tools like XInput Test or DS4Windows to map your controller’s IDs.