This is clearly a TS problem, I was a long time trying to understand what is wrong with the code of my Arduino firmware and essentially it’s all right, I guess the key release event that TS is waiting for depends on the driver or interface the device is using, but this should be clearly supported since it is for any other game or application, or may be not anymore in windows 11. Kind of funny this is here for so long!
ANSWER: Press the button and while the gray funny box is there unplug the usb cable, this does the job to me and sends to TS the information that the key is released. In the case this is the way to assign keys I suggest to put this in the manual.
According to the description, the “gamepad and joystick hotkey support” official plugin is supposed to work with virtual HID device.
I have a software that when I press a physical joystick button allows to send a vjoy button press.
But it seems teamspeak never sees the vjoy button but always catch the physical one instead.
The developers don’t seem to be interested in this topic anymore.
Workaround - Plug the controller directly into a USB port on the PC and not into a USB hub. That worked for me.
When I try to map speak button on my accuforce wheel, I recognized the putting I press, but then it sits there and requires me to press a second button, requiring me to use both buttons to talk.
If I just choose a key on my keyboard, it accepts one key just fine.
Any suggestions? I would really love to be able to use a button on my Accuforce wheel to talk while driving.
Just installed TS3 on a new build (TS3 has worked fine on my old build).
When I try to set the PTT hotkey from my HOTAS, it recognizes it but when I hit Enter (or left mouse) to save it it always adds +enter (or +left mouse button) to the selection.
Any suggestions? Can hotkeys be manually edited in one of the files? If so, where and which file.
I had similar issue back in 2017 when “Gamepad and Joystick Hotkey Support” was new.
It was solved by module developer. Now I upgraded HW (using ASUS ProArt x670e motherboard) and problem reappeared.
Original issue was with parsing USB device names, especially with virtual functions as far as I remember, here is original thread: https://forum.teamspeak.com/threads/129801-3-1-x-Can-t-set-hotkey-with-my-Joystick-Gamepad/
I, am getting an issue which cropped it’s head up a few days ago. when I goto Program my Joystick PTT key on Comm switch on the joystick, I see the button press but the OK is either greyed out or when I press it “Mouse Button1” gets selected along with my comms key button press from my stick…
I have another friend who is having the issue but none of our other frineds have this issue…
Currently, I am using Win 11 22H2 (OSBuild 22621.1702) TeamSpeake version: 3.5.6 (11/25/2020 08:53:42)
QT Version: 5.12.3
I, was using this same version a few days ago and I was able to program my PTT key no problem. I did reinstall Windows but I regularly do that and never had an issue the past few years with this happening…
It did happen some years ago and I solved it somehow but it remains a mystery as to how to get this solved…
I tried Google searches and just similar issues but not my exact issue… so if you know how to fix this I am all ears…
Problem is that “Gamepad and Joystick Hotkey Support” freezes after first input.
To verify this:
When you first time try to map PTT it will detect button down event and freezes, never detecting button up and waiting for some other key to add to combo.
If you retry, it will never detect any button/event until addon is restarted (disable/enable).
If it happens to you with PTT already mapped somehow, TS will just continuously transmit after first button down.
I’ve been havign this isssue for so long, i have done a workaround with third party program.
But, why i turned here is because I want to get the attention of the devs, so what happens is that when a button is pressed it does not register the release que. Because, (and i dont know if this is the reason to 100% but feels like it could.) on my joystick there are other buttons that are (ON)-(ON) which means they are always being depressed, maybe the TS PTT option thing does not recognise it and dont want to exit that menu because of that?
So here i am, i have no idea how to get the devs attention because they dont have a support page.
Tried it, even bought USB 2.0 header for this, no avail. I think reason is USB 2.0 on my motherboard is hooked under USB 3/USB 4 anyway.
As I’m 99% certain it has something to do with USB device addressing it is still no go
I wanted to ask for help with Teamspeak. I have been on and had everything working perfectly, but I recently got a new computer and when I reinstalled Teamspeak, i am having issues with push to talk. I use push to talk because i use speakers for my engine sound and don’t want to annoy everyone. Before, I had no problem assigning my ptt button but now it wants me to do a button combination. In other words, I assign my ptt button and then have to also hit another button, either mouse or keyboard. I have Googled and spoke to several people for a fix and can’t find one. Has anyone, by any chance, heard of this happening?
I am on Windows 11 and using a dedicated ptt button. It is for iRacing. It recognizes the button and assigns it but wants a second button pushed as well.
Yes I have an idea. I’m confident it has something to do with USB device name reported to TS. There was EXACTLY same issue few years back with virtual functions on USB controllers (see above) and now it seems to be related to more complex USB architecture and most likely to USB4.
As written above, you may try to use USB 2.0 ports and it MAY get better because of more old school USB device name/path.
Unfortunately, there is deafening silence from devs for looong time
In the past I have used the add on for joysticks/game pad to use my racing wheel for push to talk, but now it is insisting on a combo of wheel and keyboard which is near impossible when racing in VR. Any ideas why it wont let me use only one button like in previous versions? Or know of a work around. both the new TS and old ver 3 have the same issue now!
