b_client_force_push_to_talk not working the way I think it should

[Screech]

When I get this permission enforced on my by a server while I have my Voice Activate capture profile selected it notifies me that I was switched to Push-To-Talk (PTT) due to the b_client_force_push_to_talk rule. But when I push my PTT key (CTRL) it does not activate my mic. I have looked in my hot key settings and CTRL is set a my PTT key for all capture profiles, even the voice activate ones.

If I switch to a profile that is configured as PTT my PTT key works fine.

I think the PTT hot key configured on a VAC profile should be respected and the client be able to talk while in a channel with b_client_force_push_to_talk set without having to switch to a PTT profile.

Server (3.0.1 on Linux x64)
Client (3.0.3 on Windows 7 x64)

[SightUp]

+1

I have this problem too!

[dante696]

We have read this thread, but can't see the bug here.

I can use my PTT key, that has been set in my current VAD profile (i never use PTT).

I set the permission in my client permissions.
+ Current profile has VAD active and an deactivated PTT hotkey
+ The Correct hoktey profile is marked under Hotkeys
+ The same hotkey profiel is active
= I can talk

[MuhChy]

Yep, same here.
I can use my PTT hotkey while using a VAD capture profile and active force PTT.

dunno, maybe check your clientsetup again ^^

[Jordi]

Maybe Screech's user, has this permission skipped.

[Screech]

Disregard. I was looking at the wrong hotkey profile, looking at my public server hotkey profile, but when I joined his server my client defaulted to the default hotkey profile. I have to much going on to think straight and overlooking simple things all this week.

[dante696]

Ok, i mark it as no bug then.
It's always good to check this out

I can't remember anymore, when we have tested this feature.