Fix PS Prompts in Expedition 33

Clair Obscur: Expedition 33 delivers stunning turn-based combat and immersive storytelling, but PC players using PlayStation controllers often encounter Xbox button prompts like A, B, X, Y instead of familiar □, △, ○, × icons. This issue arises from default input handling in Steam or the game’s Unreal Engine 5 setup, which prioritizes Xbox layouts. Fortunately, multiple reliable fixes exist to restore native PlayStation glyphs without compromising performance.

Understanding the Controller Prompt Problem

The core issue stems from how modern games detect controllers on PC. DualSense (PS5) and DualShock 4 (PS4) controllers connect via USB or Bluetooth, but software layers like Steam Input or third-party mappers emulate them as Xbox devices for broad compatibility. In Expedition 33, this results in mismatched prompts, confusing players mid-battle during precise timing-based mechanics like parries and dodges.

Community reports confirm this affects both Steam and non-Steam versions, including Game Pass. Disabling overrides allows the game to recognize the controller natively, displaying correct PS icons. These solutions work across wired and wireless setups, with USB often proving more reliable for detection.

Primary Fix: Disable Steam Input for Native Detection

The simplest and most effective method for Steam users is adjusting game-specific controller settings. Steam Input, while powerful for customization, defaults to Xbox prompts and can override the game’s built-in support for DualSense.

1. Launch Steam and navigate to your Library.
2. Right-click Clair Obscur: Expedition 33 and select Properties.
3. Switch to the Controller tab on the right.
4. From the dropdown, choose Disable Steam Input.
5. Close the window, restart the game, and reconnect your controller.

This tweak forces the game to use its internal input system, which supports PS glyphs out-of-the-box. Test in the menu or a skirmish—prompts should now show PlayStation symbols. If using Bluetooth, ensure your controller is paired directly via Windows Bluetooth settings first.

Config File Editing for Forced PS5 Prompts

For persistent issues or non-Steam launches, directly edit the game’s configuration files. Located in the app data folder, these INI files control input platforms. This method sets DefaultGamepadName=PS5, overriding any detection errors.

Step-by-Step for Steam Version:

• Press Win+R, type %LOCALAPPDATA%, and hit Enter.
• Navigate to Sandfall/Saved/Config/WindowsNoEditor/.
• Locate or create GameUserSettings.ini (show hidden files if needed via View > Hidden items).
• Right-click to edit with Notepad; if none exists, new text file renamed to GameUserSettings.ini.
• Delete contents and paste:

  [CommonInputPlatformSettings_Windows]
  DefaultGamepadName=PS5
  bCanChangeGamepadType=False

• Save, set file to read-only (right-click > Properties), and relaunch.

For Game Pass/Xbox App: Use WinGDK folder instead of WindowsNoEditor. This edit survives restarts and applies globally.

Third-Party Tools: DS4Windows and Beyond

DS4Windows emulates PS controllers as native Xbox for better compatibility but can be tuned for authentic prompts. Download from the official site (ds4-windows.com) and configure:

• Install and run DS4Windows.
• In Settings, set Emulated Controller to DualShock 4.
• Hide DS4 Controller option enabled.
• Connect via USB for stability, disable Steam Input as above.

Alternatives include disabling all mappers: Close Steam Overlay, DS4Windows, or reWASD, then plug in directly. Firmware updates via PlayStation Accessories app ensure optimal detection.

Mods for Permanent PS Icon Replacement

Nexus Mods offers a plug-and-play solution: “Force PS5 Controller Icons.” This pak file swaps Xbox textures with PS5 glyphs seamlessly.

1. Download from Nexus Mods.
2. Extract to Steam/steamapps/common/Expedition 33/Sandfall/Content/Paks/.
3. No launcher needed; game reads it automatically.

Ideal for PS4/PS5 or third-party pads. Compatible with most setups, but back up Paks folder first.

Troubleshooting Common Hurdles

If prompts persist:

• USB vs. Bluetooth: Wire up—many games ignore wireless PS controllers.
• Multiple Tools Conflict: Uninstall extras; test vanilla.
• Firmware/Game Updates: Check PlayStation app and Steam for patches.
• Verify Detection: Windows Devices shows DualSense as “Wireless Controller”? Good sign.

Restart PC post-changes. For Xbox controllers wanting PS prompts, reverse via Steam Input profiles.

Optimizing Controller Setup in Expedition 33

Beyond prompts, tweak Steam global settings: Settings > Controller > Enable PlayStation Configuration Support. This aids detection across libraries. In-game, check options for input swap if available—community notes FF16-style toggles may patch in.

Expedition 33’s combat shines with precise inputs: Practice parry windows (△/Y) and QTEs (○/B) feel natural with matching visuals.

FAQs

Why does Expedition 33 show Xbox prompts on PS5 controller?

Steam Input or game defaults emulate Xbox for compatibility; disable to fix.

Does this work on PS5 console?

Console versions use native PS prompts—no fixes needed.

Will config edits break saves?

No, input settings are separate; read-only protects them.

Best for wireless DualSense?

USB preferred; Bluetooth works after Steam disable.

Mods safe for multiplayer?

Single-player only; no online impact.

Community Tips and Future Patches

Forums buzz with success stories—over 90% fix rate via Steam disable. Developers may add toggle in updates, per Steam discussions. Share your setup in comments!