Crouch not behaving?

[Similar]

Often I have to press C many times before my V crouches. It's not that the action is delayed, like from lag, the key presses just don't seem to register at all. Doesn't matter if I'm walking, or standing still when I press it either.
Tried binding crouch to a mouse button, but that didn't work any better, so it doesn't seem to be a problem with my keyboard.
C to uncrouch has the same problems, but at least there are more ways to stop crouching.

Pressing 1, 2, 3 to switch weapons also sometimes doesn't seem to register, but it happens more rarely than with C (but always at bad times, of course). Some of it could maybe be due to the game wanting to finish animations before it switches (the Overwatch, for example, has very long animations)? I can't really tell.
Using the scroll wheel is generally more reliable, but rather awkward to use when things get hectic.

All other keys seem to work fine. Space Bar, Alt, Shift, F, WASD, etc. all seem to register presses without problems.
I can drive for hours without problems, for example, and if the C issues were due to lag, I think I should notice something when driving, what with all the rapidly changing stuff that has to be rendered (I tried turning raytracing off anyway and it made no difference for C either).
Lag would affect more things than just crouch.

I've seen another post mention problems with C, and it appears there were plenty of people having problems with crouch after 2.0 was released (had the game installed then, but only started playing it about a week ago), but they don't seem to be quite the same issues as mine.
Aside from when I bound crouch to a mouse button as a test, all my keybinds are default (binding it back to C made no difference either).

Edit: Perhaps worth mentioning that I don't have Phantom Liberty.

[Death Approaches]

shouldn't matter over re: PL; the base code is the same and prepares for this whether or not you have it installed, if you do go out there, the entrance to dogtown is there, and lots of barghest mercs are there too; open fire on them for a fun fight.

I have a basic question - do you have your keyboard plugged into a USB hub and not directly to it's own port? Especially if it's a backlit LED keyboard? Passive games that wait for input this can be fine, active polling on the other hand can exceed an unpowered hub's ability and it usually takes 3 activations to register. When you said it does it on the weapon swap keys as well, a lightbulb went off.

If you're on an nvidia card you can try enabling reflex in the menu, this steals a couple fps but not much, and the control latency (assuming that's the issue) should vastly improve.

[Similar]

Originally posted by Death Approaches:

shouldn't matter over re: PL; the base code is the same and prepares for this whether or not you have it installed, if you do go out there, the entrance to dogtown is there, and lots of barghest mercs are there too; open fire on them for a fun fight.

heh. yeah, before I knew Dogtown was a Phantom Liberty thing, I set a waypoint in there and the GPS took me right to the entrance (which was kind of confusing because it really looked like I could get in there. Maybe there would have been a message if I'd dared to go closer, but those Barghest looked mean).

Originally posted by Death Approaches:

I have a basic question - do you have your keyboard plugged into a USB hub and not directly to it's own port? Especially if it's a backlit LED keyboard? Passive games that wait for input this can be fine, active polling on the other hand can exceed an unpowered hub's ability and it usually takes 3 activations to register. When you said it does it on the weapon swap keys as well, a lightbulb went off.

Both mouse and keyboard are plugged directly into the USB ports on the PC. Good guess, though. It does seem like something like that, except it'd be odd if it only affected two keys (my keyboard is very old, cheap and battered and has never heard of backlight or LEDs or anything like it).
Something like Dash seems to work properly (although it's very sensitive; you really have to tap the key, not press it), for example.

I played about a hundred hours of The Division 2 before I started playing Cyberpunk and didn't notice problems there, nor in other faster games in the past either, so it does seem to be pretty specific to Cyberpunk.
But I could try another port for the keyboard, just in case.

I did read that the game has problems with Razer Chroma (some RGB thing, I imagine) and I recently (about five weeks ago), got a Razer Deathadder mouse, but the software for that is called Synapse. Don't know if it could still cause problems. But again, it'd be weirdly specific if it only affected a couple of keys.

Originally posted by Death Approaches:

If you're on an nvidia card you can try enabling reflex in the menu, this steals a couple fps but not much, and the control latency (assuming that's the issue) should vastly improve.

ah, that's apparently turned on by default.

Thanks for trying. It's a very weird problem.