Phantom controller when playing Ghost of Tsushima DIRECTOR'S cut

Hey all,

I am running Ghost of Tsushima DIRECTOR’S cut through steam with proton experimental and all is well except one thing. The game thinks I have a controller connected. I have nothing of that sort. The only I have connected are my headphones and a mouse. Because it assumes I have a controller, It does not allow me to change keyboard bindings. I really want to remap Dodge and Parry.

I have tried disabling/enabling steam input with 0 luck. Could someone help?

The only reference I could find was a post from 2012 on the arch forums.

garuda-inxi

System:
Kernel: 6.14.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=e1e5baab-defb-43b8-bf16-26d8e7f494cc rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A info: frameworks v: 6.14.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Laptop System: LENOVO product: 83DN v: Yoga Pro 9 16IMH9
serial: <superuser required> Chassis: type: 10 v: Yoga Pro 9 16IMH9
serial: <superuser required>
Mobo: LENOVO model: LNVNB161216 v: SDK0T76461 WIN
serial: <superuser required> part-nu: LENOVO_MT_83DN_BU_idea_FM_Yoga Pro 9
16IMH9 uuid: <superuser required> UEFI: LENOVO v: NKCN28WW
date: 06/28/2024
Battery:
ID-1: BAT0 charge: 46.1 Wh (55.3%) condition: 83.4/84.0 Wh (99.2%)
power: 17.4 W volts: 15.4 min: 15.6 model: BYD L23B4PF1 type: Li-poly
serial: <filter> status: discharging cycles: 11
CPU:
Info: model: Intel Core Ultra 9 185H bits: 64 type: MST AMCP
arch: Meteor Lake level: v3 note: check built: 2023+ process: Intel 4 (7nm)
family: 6 model-id: 0xAA (170) stepping: 4 microcode: 0x24
Topology: cpus: 1x dies: 1 clusters: 9 cores: 16 threads: 22 mt: 6 tpc: 2
st: 10 smt: enabled cache: L1: 1.6 MiB desc: d-10x32 KiB, 6x48 KiB; i-16x64
KiB L2: 18 MiB desc: 9x2 MiB L3: 24 MiB desc: 1x24 MiB
Speed (MHz): avg: 400 min/max: 400/4800:5100:3800:2500 scaling:
driver: intel_pstate governor: powersave cores: 1: 400 2: 400 3: 400 4: 400
5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400 14: 400
15: 400 16: 400 17: 400 18: 400 19: 400 20: 400 21: 400 22: 400
bogomips: 135168
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Meteor Lake-P [Intel Arc Graphics] vendor: Lenovo
driver: i915 v: kernel alternate: xe arch: Xe-LPG process: Intel 4 (7nm+)
built: 2023+ ports: active: eDP-2 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:7d55 class-ID: 0300
Device-2: NVIDIA AD107M [GeForce RTX 4050 Max-Q / Mobile] vendor: Lenovo
driver: nvidia v: 570.144 alternate: nouveau,nvidia_drm
non-free: 550-570.xx+ status: current (as of 2025-04) arch: Lovelace
code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4
speed: 16 GT/s lanes: 8 ports: active: none empty: eDP-1 bus-ID: 01:00.0
chip-ID: 10de:28e1 class-ID: 0300
Device-3: Syntek Integrated Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-8:3 chip-ID: 174f:11ad
class-ID: fe01 serial: <filter>
Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
unloaded: nouveau alternate: fbdev,intel,nv,vesa dri: iris gpu: i915
display-ID: 0
Monitor-1: eDP-2 model: Lenovo 0x8ba1 serial: <filter> built: 2022 res:
mode: 3200x2000 hz: 165 scale: 200% (2) to: 1600x1000 dpi: 236 gamma: 1.2
size: 344x215mm (13.54x8.46") diag: 406mm (16") ratio: 16:10
modes: 3200x2000
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia nouveau drv: nvidia
platforms: device: 0 drv: nvidia device: 1 drv: iris device: 2 drv: nouveau
device: 3 drv: swrast gbm: drv: iris surfaceless: drv: nvidia wayland:
drv: iris x11: drv: iris
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 25.0.5-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel Arc Graphics (MTL)
device-ID: 8086:7d55 memory: 15.11 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.4.313 layers: 10 device: 0 type: integrated-gpu
name: Intel Arc Graphics (MTL) driver: mesa intel v: 25.0.5-arch1.1
device-ID: 8086:7d55 surfaces: N/A device: 1 type: discrete-gpu
name: NVIDIA GeForce RTX 4050 Laptop GPU driver: nvidia v: 570.144
device-ID: 10de:28e1 surfaces: N/A device: 2 type: cpu name: llvmpipe
(LLVM 19.1.7 256 bits) driver: mesa llvmpipe v: 25.0.5-arch1.1 (LLVM
19.1.7) device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Meteor Lake-P HD Audio vendor: Lenovo
driver: sof-audio-pci-intel-mtl
alternate: snd_hda_intel,snd_sof_pci_intel_mtl bus-ID: 00:1f.3
chip-ID: 8086:7e28 class-ID: 0401
API: ALSA v: k6.14.6-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.4.2 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Meteor Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:7e40 class-ID: 0280
IF: wlp0s20f3 state: up mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:4 chip-ID: 8087:0033
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
Local Storage: total: 953.87 GiB used: 333.56 GiB (35.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: MZVL21T0HCLR-00BL2 size: 953.87 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: EL1QGXA7 temp: 39.9 C scheme: GPT
Partition:
ID-1: / raw-size: 951.65 GiB size: 951.65 GiB (100.00%)
used: 333.51 GiB (35.0%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%)
used: 46.5 MiB (18.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 951.65 GiB size: 951.65 GiB (100.00%)
used: 333.51 GiB (35.0%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
ID-4: /var/log raw-size: 951.65 GiB size: 951.65 GiB (100.00%)
used: 333.51 GiB (35.0%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
ID-5: /var/tmp raw-size: 951.65 GiB size: 951.65 GiB (100.00%)
used: 333.51 GiB (35.0%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.95 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 22
dev: /dev/zram0
Sensors:
Src: /sys System Temperatures: cpu: 40.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 30.95 GiB used: 5.9 GiB (19.1%)
Processes: 453 Power: uptime: 1h 27m states: freeze,mem,disk
suspend: s2idle wakeups: 3 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.3 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1560 libs: 484 tools: octopi,paru Compilers:
gcc: 15.1.1 Shell: garuda-inxi default: fish v: 4.0.2 running-in: konsole
inxi: 3.3.38
Garuda (2.7.2-1):
System install date:     2025-05-09
Last full system update: 2025-05-14
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:

EDIT:

I have also run the game without steam and the same thing happens. I highly doubt its a steam input issue. If I remember correctly the game (GOT) implements its own system for managing controls.

hey,

ive seen now you edited the post . But did you try if you run it with Steam the Controller Setting to disable Steaminput ? Did you looked on protondb website? I dont have this Game.

right click properties

I dont know where you get the Game may its configured for Controllers idk. Otherwise may try antimicrox or other input remapper for that Game idk jutst some thinkings…

1 Like

I don’t know if the cause is the game itself, but some touchpads, gaming mice and Bluetooth dongles can cause this behavior. Try disabling the touchpad, either in the KDE system settings or, if available on this laptop, in the BIOS or via keyboard shortcut (Fn+F?). If that doesn’t help, try disconnecting the mouse before you start the game and see if you can change the keyboard bindings (or try a different mouse).

2 Likes

Unfortuntely this does not help. Thank you for time though.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.