Title: Third-party XInput controller incorrectly triggers PlayStation button glyphs

Game version: Arma Reforger 1.8.0.13
Platform: Windows / Steam

Controller: GameSir G7 Pro 8K
Windows device: Xbox 360 Controller for Windows
USB hardware ID: VID_3537&PID_1CC5

Issue

Arma Reforger displays PlayStation-style controller glyphs when using a GameSir G7 Pro 8K, even though Windows recognizes the device as an Xbox/XInput controller and the controller functions normally.

The issue affects the visual button prompts only. Input behavior itself appears correct.

A genuine Microsoft Xbox controller on the same PC displays the expected Xbox A/B/X/Y glyphs.

Steps to reproduce

1. Connect a GameSir G7 Pro 8K to a Windows PC.

2. Confirm in joy.cpl that Windows identifies it as Controller (XBOX 360 For Windows) and status is OK.

3. Disable Steam Input for Arma Reforger.

4. Launch Arma Reforger.

5. Navigate the main menu or enter a session.

6. Observe that the UI displays PlayStation-style button prompts instead of Xbox A/B/X/Y prompts.

Troubleshooting already performed

• Steam Input enabled and disabled — no change.

• Controller disconnected during game launch and connected afterward — no change.

• Controller polling rates tested at 250 Hz, 1000 Hz, 4000 Hz, and 8000 Hz — no change.

• Windows consistently identifies the controller as an Xbox/XInput device.

• Genuine Microsoft Xbox controller tested on the same system — Xbox glyphs display correctly.

Log evidence

When the GameSir controller is connected directly, the Reforger log shows PlayStation-specific UI resources being loaded:

UI/Textures/Icons/icons_gamepad/icons_gamepad_playstation-glow-200_atlas.edds

UI/Textures/Icons/icons_gamepad/icons_gamepad_playstation-200_atlas.edds

along with the generic gamepad resources. console

When using a genuine Xbox controller, the PlayStation resources are not loaded. The log instead shows only the generic gamepad resources:

icons_gamepad-200_atlas.edds

icons_gamepad-glow-200_atlas.edds

This indicates that Reforger is selecting a different glyph/resource family depending on the physical controller being presented.

Additional isolation test

As a diagnostic test, the GameSir controller was hidden from the game and presented through a virtual Xbox controller.

With the virtual Xbox controller exposed to Reforger, the PlayStation-specific resources disappeared and the game loaded only the normal gamepad resources:

icons_gamepad-200_atlas.edds

icons_gamepad-glow-200_atlas.edds console

The same configuration successfully connected to an official BattlEye-protected Reforger server, with BattlEye initializing normally. console

Expected behavior

An XInput-compatible controller that Windows identifies as an Xbox controller should display Xbox-style A/B/X/Y, LB/RB, LT/RT, View/Menu glyphs.

Actual behavior

The GameSir G7 Pro 8K functions as an Xbox/XInput controller but Reforger selects the PlayStation glyph set.

Likely area to investigate

The issue appears to be in controller presentation/glyph classification rather than actual input handling. Reforger may be using controller identity, HID metadata, VID/PID, or another device-classification property in addition to XInput capability when selecting the glyph atlas.

The physical controller in this case reports:

VID_3537

PID_1CC5

It may be worth checking how third-party XInput devices are classified by the gamepad glyph-selection logic.

Suggested improvement

In addition to fixing automatic detection, a user-selectable setting such as:

Controller Glyph Style: Auto / Xbox / PlayStation

would provide a fallback for unsupported or incorrectly classified third-party controllers.