Salty Chat currently uses the un-/mute feature. Every request to un-/mute a player is sent to the server, as it ensures that the client does not receive any more voice data for the respective player.
On servers with high player count (~700+) this leads to issues with the TeamSpeak server since it can't handle that many request/second.
To mitigate these issues, TeamSpeak suggested the use of their whisper feature, which will be used from 3.0.0 onwards.
This issue is used to keep track of issues regarding the switch from un-/mute to whispering.
Current known issues:
Phone/Radio loudspeaker does not work, if target clients aren't already a whisper target by the sending client
Clients which haven't talked to each other before can lose the first ~5 seconds of the first interaction
It seems that there is a higher amount of crashes for certain clients. Callstack of a crashdump doesn't show plugin involvement, maybe a TeamSpeak bug related to whispering?
While whispering it is not possible to send voice samples when the client is not talking without forcing the capture mode to continuous transmission, which impacts the usage of echo effect and a loudspeaker rewrite/redesign
The bubble in front of the client name in TeamSpeak doesn't light up when local client is talking
3D position of another client gets reset when client starts whispering to the local client > workaround implemented in 3.0.2
Talk state reported by the SDK flaps to false and back to true if the client is talking while updating whisper targets > workaround implemented in 3.0.5
Aside from the first one it seems that these issues are all caused by TeamSpeak. We reported these issues to TeamSpeak and they are investigating.
Things that need to be tested:
[X] Proximity
[X] 3D audio
[X] Adjustable ranges / Distance-based flattening of the volume
Salty Chat currently uses the un-/mute feature. Every request to un-/mute a player is sent to the server, as it ensures that the client does not receive any more voice data for the respective player. On servers with high player count (~700+) this leads to issues with the TeamSpeak server since it can't handle that many request/second. To mitigate these issues, TeamSpeak suggested the use of their whisper feature, which will be used from 3.0.0 onwards.
This issue is used to keep track of issues regarding the switch from un-/mute to whispering.
Current known issues:
3D position of another client gets reset when client starts whispering to the local client> workaround implemented in 3.0.2Talk state reported by the SDK flaps to> workaround implemented in 3.0.5false
and back totrue
if the client is talking while updating whisper targetsAside from the first one it seems that these issues are all caused by TeamSpeak. We reported these issues to TeamSpeak and they are investigating.
Things that need to be tested:
Data based on 3.0.5.