PLAYSTATION CONTROLLER FLICKERING PROMPT FIX

PLAYSTATION CONTROLLER FLICKERING PROMPT FIX

What This Mod Does

Since patch 1. 7 introduced native DualSense controller support on PC, players using PlayStation controllers — DualSense, DualSense Edge, and DualShock 4 — have experienced a persistent bug where the game's button prompts constantly flip between PS5 and Xbox layouts while using the analog sticks.

Specifically, moving the left stick horizontally or the right stick vertically would cause the prompts to cycle to Xbox, and upon re-entering the dead-zone they would snap back to PS5.

This was very apparent and extremely annoying on the map, which would constantly recenter and make a sound.

This made the UI unreliable and broke the immersion of native PS5 prompt support that patch 1. 7 was supposed to deliver.

No amount of disabling Steam Input, using third-party tools like DualSenseX, DS4Windows, HIDHide, or ValvePlug (a SpecialK tool) resolved the issue because the bug exists entirely within the game's own input configuration files, not in the Windows driver or Steam layer.

Root Cause

STALKER 2 uses Unreal Engine 5's RawInput plugin to handle PlayStation controllers on PC, configured in the file Stalker2/Config/DefaultInput.ini.

Within the section of this file, each supported controller has a DeviceConfiguration entry identified by its USB Vendor ID and Product ID.

For all DualSense and DualShock 4 devices, one of the axis entries in AxisProperties read as follows:

(Key=GenericUSBController_Axis5,bIsDpad=True,Offset=1. 000000). GenericUSBController_Axis5 is a raw HID axis report that the game uses to handle D-pad input on PlayStation controllers.

The problem is that with bIsDpad=True set, this axis is simultaneously reported to the game as both a D-pad signal and a raw generic USB axis event.

The game's internal controller type detection heuristic — the logic that decides whether to show PS5 or Xbox button prompts — watches incoming axis events and uses them to determine which controller is currently active.

When GenericUSBController_Axis5 fires as a generic axis, the detector misidentifies it as activity from an Xbox controller, because that generic axis index overlaps with axis indices the detector associates with Xbox input.

The result is the prompt flip players have been experiencing every time they touch the sticks.

This is entirely a GSC Game World configuration oversight introduced alongside the patch 1. 7 DualSense implementation. 

What Was Changed

In DefaultInput.ini, for the following four device entries in [/Script/RawInput. RawI