.ini — Fifa Button Data Setup

For the vast majority of FIFA (and now EA Sports FC) players, the controller just works. You plug it in, select "Classic" or "Alternate" from the in-game menu, and you’re off to the races. But for the modding community, the competitive edge-seekers, and those using unsupported or arcade fight sticks, the default settings are a cage. The key that unlocks this cage is a small, powerful, and often intimidating file: buttonDataSetup.ini.

This article is your complete encyclopedia for understanding, editing, and mastering the buttonDataSetup.ini file. We will cover what it is, where to find it, how its syntax works, and advanced techniques to create a truly bespoke controller layout.

Always create a backup copy of the original buttonData.ini or profile.ini before making changes. A single syntax error (like a missing bracket) can cause the game to crash on startup or fail to recognize any controller.

Before editing the .ini, you must know what ID your controller sends when a button is pressed.

The buttonData.ini file is a core configuration file used in older PC versions of

(such as FIFA 11 through FIFA 15) to manually map controller inputs for generic or unsupported gamepads. Because many budget controllers aren't natively recognized as "Xbox 360" controllers, players often have to copy-paste detailed mapping blocks—assigning specific hex codes to actions like VB_AI_A (Pass) or VB_AI_RS_UP (Skill Moves)—into this .ini file to fix non-functional right sticks or swapped buttons. The Ghost in the Gamepad

The blue-and-white plastic of Elias’s "Generic USB Joystick" felt light and cheap, a $5 thrift store find that promised glory but delivered only frustration. He had loaded up the pitch, but his star striker was spinning in endless, nauseating circles. The right analog stick was dead, a silent rebel against his commands.

"Fix the mapping, fix the soul," Elias whispered, cracking his knuckles.

He navigated to the game's dusty corridors: Documents\FIFA\buttonData.ini. Opening the file was like entering a digital tomb. Thousands of lines of code—AddAlias, AddMap, VB_AI_LDPAD_UP—stared back at him in monochromatic defiance.

He found a block of code on an old forum, a "legendary" setup for generic pads. He deleted the old, broken aliases and pasted the new string.

AddMap PC_CONTROL_BUTTON03 VB_AI_AAddMap PC_AXIS_2_UP VB_AI_RS_LEFT

He saved the file, the cursor blinking like a heartbeat. When he alt-tabbed back into the stadium, the spinning stopped. The striker stood still, awaiting orders. Elias flicked the right stick. A perfect step-over. A flick of the heel. The "button data" was no longer just text; it was the bridge between his fingers and the back of the net.

The cheap plastic didn't feel so light anymore. It felt like a trophy. How To Play FIFA 21 With A Generic USB Joystick (No x360ce) fifa button data setup .ini

For many PC gamers, configuring a generic or unsupported controller for the FIFA series (now EA Sports FC) can be a frustrating hurdle. The buttonDataSetup.ini file is the key configuration document used by the game's engine to map hardware inputs to in-game actions. Manually editing or replacing this file is a common fix for issues like non-responsive right analog sticks, swapped buttons, or controllers not being recognized at all. What is buttonDataSetup.ini?

The buttonDataSetup.ini file contains detailed mapping data for various game controllers. It standardizes inputs—such as buttons, triggers, and thumbstick axes—into a format the game understands, regardless of the brand or model of your gamepad. Each controller entry in the file typically includes:

AddController: The internal ID assigned to a specific gamepad model.

AddAlias: Common names or device strings used to identify the hardware.

AddMap: Specific lines that link a physical button (e.g., PC_CONTROL_BUTTON01) to a virtual action (e.g., VB_AI_A for passing or VB_FE_SELECT for menus). Common File Locations

The location of this file can vary slightly depending on the version of FIFA you are playing, but it is typically found in one of two places:

Documents Folder: Look in Documents/FIFA [Version Name] (e.g., Documents/FIFA 22).

Game Installation Directory: In older titles like FIFA 12, it may be located in Program Files/EA Sports/FIFA [Version]/Game. How to Fix Controller Issues Using .ini Data

If your controller isn't working correctly, you can often resolve the issue by using a pre-configured buttonDataSetup.ini file or modifying your existing one. 1. The Right Analog Stick Fix

The most common issue with generic controllers is the right analog stick failing to register, which prevents players from performing skill moves.

Manual Fix: You can open the file in a basic text editor like Notepad and find the entry for your controller (or the "Default" entry).

Coordinate Remapping: Ensure the axes for the right stick are correctly defined. For example, PC_AXIS_2 is often used for right-stick horizontal and vertical movement. 2. Swapped Buttons (Triggers vs. Bumpers) For the vast majority of FIFA (and now

Sometimes L1/R1 are swapped with L2/R2. To fix this, locate your controller's section in the .ini file and swap the mapping for VB_AI_LB/RB with VB_AI_LT/RT. 3. Using Older Configuration Tools

buttonDataSetup.ini file is a configuration file used by older PC versions of FIFA (primarily FIFA 11 through FIFA 17) to manually map controller buttons and fix issues like the "Right Analog Stick" not working. File Location

You can typically find the file in your Windows user documents folder: Documents\FIFA [Year]\buttonDataSetup.ini C:\Users\[Username]\Documents\FIFA 15\buttonDataSetup.ini Common "Proper Piece" Mapping

If your controller is not recognized correctly, users often replace the content of the

file with a "Universal" or "Xbox" style mapping. Below is the standard structure for a generic USB controller to act like a standard Xbox/PS pad:

AddController "Controller_045" AddAlias "Default" AddMap PC_CONTROL_BUTTON01 VB_AI_A AddMap PC_CONTROL_BUTTON02 VB_AI_B AddMap PC_CONTROL_BUTTON03 VB_AI_X AddMap PC_CONTROL_BUTTON04 VB_AI_Y // ... (Additional mapping configurations) Use code with caution. Copied to clipboard

(Based on common configurations found on GitHub, often requiring entries to map actions to PC_CONTROL identifiers) Fixing Specific Issues Right Analog Stick Fix : If the right stick is swapped or not working, ensure the (Right Stick) mappings point to the correct axes (usually Modern Workaround : For newer titles like FIFA 23 or FC 25, the method is largely deprecated. Instead, use tools like the x360ce emulator DS4Windows

to emulate an Xbox 360 controller, which is natively supported by the game engine.

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

You've spent an hour editing. You save the file. You launch FIFA... and nothing changed. Here is the troubleshooting checklist.

[Metadata]
version = 1.0
profile_name = Default
created_by = gamer
created_date = 2026-04-10
platform = Windows
[Device]
vendor_id = 0x045e
product_id = 0x028e
guid = 028e045e-0000-0000-0000-000000000000
device_name = Xbox 360 Controller
connection = USB
[Buttons]
A = button_0
B = button_1
X = button_2
Y = button_3
LB = button_4
RB = button_5
LT = axis_2
RT = axis_5
Start = button_9
Select = button_8
LStick = button_10
RStick = button_11
DPadUp = hat_0_up
DPadDown = hat_0_down
DPadLeft = hat_0_left
DPadRight = hat_0_right
[Axes]
LeftStickX = axis_0
LeftStickY = axis_1
RightStickX = axis_3
RightStickY = axis_4
invert_LeftStickY = false
deadzone_LeftStick = 0.08
sensitivity_RightStick = 1.0
[Advanced]
trigger_threshold = 0.5
rumble_strength = 0.8
analog_mode = linear
turbo_enabled = false
anti_ghosting = true

Physical inputs are usually named:

Example Swap (Make R1 do shooting): AddMap PC_CONTROL_BUTTON_R1 VB_AI_B Location of the

You need the list of VB_ (Virtual Button) commands. Examples: