Custom Keybind cause conflict in b2060/b2189

FiveM Discussion Bug Reports
1
  1. Generic Informations

Category : Client bug related to the Casino Update (b2060/2189)
Tested on : Canary & Production client
Server : Latest artifact 3247 with

+set sv_enforceGameBuild 2060
or
+set sv_enforceGameBuild 2189

  1. What actually happens

In game build 2060, it’s impossible to change your keybind because of the custom category “FiveM” conflicting with other keybind.
It doesn’t appear as this specific category is the problem in game, but I suppose it is the only change made by FiveM

Note : Clicking the “Restore All Defaults” or deleting fivem.cfg doesn’t correct this bug

  1. Reproducible steps, preferably with example script(s)

No conflict prior to b2060 :
Keybind conflict in b2060 :

As you can see, the message “There are inputs that are currently unbound or conflict.” appear with an exclamation mark, but no other category appear with it.

In normal circumstance, the conflict category & specific key would warn us

Happening constantly with this simple repro command (The specific key doesn’t affect the bug, you could try any other key)

RegisterKeyMapping(‘+test’, ‘Test Keybinding’, ‘keyboard’, ‘F9’)

1 Like
2

I’m also seeing this on build 2189

1 Like
3

Could be related to invalid hook (changed in b2060) to manage the conflict from the keys
See this line : fivem/GameInput.cpp at master · citizenfx/fivem · GitHub

But i’m currently unable to test it…

4

This specified hook looks fine for me, i.e. doesn’t seems to be changed comparing to b1604 and b2189, maybe I miss something? What you’ve noticed?

5

Same issue reported by our players

6

Maybe some old files left in citizen/platform/data/control/ instead of an actual issue with custom key mapping data?

In fact, the underlying issue is a bit weirder:

image
image1386×346 67.2 KB

Seems as if it’s rather the case the international keyboard mapping logic would be broken?

7

OK, other than that layout bug, it seems game code fails on 2 new inputs that were added in 2060/2189, and again not the custom key mappings.

  • INPUT_RESPAWN_FASTER
  • INPUT_HUDMARKER_SELECT

… being unbound yet marked as mandatory binding or so?

(yeah, that does seem to be an outdated control/ directory, and nothing to do with ‘custom keybind cause conflict’. thanks for the misleading report!)

		<!--
			IGNORE:	These inputs are not required to be placed into a specific category.
					They are either unused, not-remappable, duplicate mapped, or deprecated.
		-->

				<Item>INPUT_RESPAWN_FASTER</Item>
				
				<Item>INPUT_HUDMARKER_SELECT</Item>

Apparently using these on 1604 would be even more broken, so we might need a platform-[build] directory, too?

1 Like
8

Should be fixed in latest.

4 Likes
9

It’s not fixed ? i have this problem now

10

Latest. Not whatever is on production.

1 Like
11

B2060: key mappings don’t show in game settings - FiveM Discussion / Bug reports - Cfx.re Community you forgot to mark this issue as resolved