# Input Device Issues and Suggestions

**URL:** <https://forums.fatsharkgames.com/t/input-device-issues-and-suggestions/85433>\
**Category:** Gameplay Feedback\
**Created:** [October 27, 2023, 1:03am UTC](https://forums.fatsharkgames.com/t/input-device-issues-and-suggestions/85433 "2023-10-27T01:03:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeff.from.above](https://avatars.discourse-cdn.com/v4/letter/j/bb73d2/32.png) [@jeff.from.above](https://forums.fatsharkgames.com/u/jeff.from.above)\
**Post date:** [October 27, 2023, 1:03am UTC](https://forums.fatsharkgames.com/t/input-device-issues-and-suggestions/85433/1 "2023-10-27T01:03:40Z")

</div>

**Issues**

- The game forces a switch of input devices if it detects any input from the other device. This is cumbersome, especially when we’re forced to use a keyboard shortcut for push-to-talk.

- The game seems to have trouble with gamepads in general.

- Other times, if I’m trying to use the push to talk keybind or the in-game chat while using a gamepad, it won’t work until I grab my mouse and click somewhere in the game window.

**Suggestions**

- Combine gamepad and m&kb inputs into one control scheme instead of switching between them.
- On gamepads, let us use the up button on the d-pad (currently unused) for push-to-talk.
- Let us kiss Hadron

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/fatshark/original/3X/3/1/319a2f41b73f03a4d9360defbe43058888a33c8c.png) [@system](https://forums.fatsharkgames.com/u/system)\
**Post date:** [November 3, 2023, 1:03am UTC](https://forums.fatsharkgames.com/t/input-device-issues-and-suggestions/85433/2 "2023-11-03T01:03:40Z")

</div>

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