Skip to content
This repository has been archived by the owner on Aug 17, 2024. It is now read-only.

Block controls occupied by mod's controls #13

Open
ikt32 opened this issue Jun 10, 2017 · 5 comments
Open

Block controls occupied by mod's controls #13

ikt32 opened this issue Jun 10, 2017 · 5 comments

Comments

@ikt32
Copy link
Owner

ikt32 commented Jun 10, 2017

When using a controller, controls can be bound to buttons that the game also uses for existing actions. It'd be nice if this could be blocked properly without losing original functionality.

PR #12, and commits c6cf9a9 and 58b6a2e solved the tapping thing, but blocking things is still lacking.

Any ideas?

@ikt32
Copy link
Owner Author

ikt32 commented Oct 19, 2017

26c3380 enabled executing the original functions after holding the buttons, but I can't get single-tap actions to work. Example:

Shift Up blocks the Duck action. Tapping Shift Up just makes the mod shift up, and the Duck action is blocked properly. Holding Shift Up executes the Duck action and the character can be seen ducking while this button is held. The mod doesn't shift up.

Shift Down blocks the Switch Weapon action. Tapping Shift Down just makes the mod shift down, and the Switch Weapon action is blocked properly. Holding Shift Down does not execute the Switch Weapon action. The mod doesn't shift down.

Help would be nice.

@asm512
Copy link

asm512 commented Dec 24, 2017

Have you found a solution to this? If I understand correctly, holding either shift up or shift down does not call the respective function, but instead in shift up's case, causes the character to duck, and in shift up's case calls nothing?

@ikt32
Copy link
Owner Author

ikt32 commented Dec 27, 2017

Nope. Depending on the original action, holding works as long as the original action also allows holding. This is ducking, aiming, shooting, etc. If the original action was tap-only (switch weapons), it doesn't work.

@ikt32
Copy link
Owner Author

ikt32 commented May 13, 2020

This is still open, by the way.

ikt32 added a commit that referenced this issue Jul 7, 2020
Still no solution for #13
@Luc45
Copy link

Luc45 commented Nov 22, 2020

Howdy!

"X" is mapped to downshiftby default, but it is also mapped to the Next vehicle weapon action natively. Is there a way to prevent "X" from triggering the Next vehicle weapon action?

image

Got it

  1. While in-game, open Manual Transmission menu
  2. Controls -> Controller -> Controller bindings (mine is Native, by the way)
  3. ShiftUp blocks = NextWeapon
  4. ShiftDown blocks = NextWeapon

😁

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants