Home » News
Mandatory update for TeamSpeak 3
Posted by Administrator | 02 June 2010 - 15:35 | 0 Comments
It has been over 1.5 months since the last stable release of TeamSpeak 3. Many of the prior updates were not mandatory, the current update, however, is. We have updated all of the Clanhost TeamSpeak 3 servers to the latest version. Please read further for an overview of the most important changes.
Additional notes regarding TS3 Client Beta 21:
- It has been ~1.5 months since our last stable client release, which has resulted in a massive amount of updates for the new client (the final changelog will be over 150 lines!). As usual, the final changelog will be published to http://forum.teamspeak.com/forumdisplay.php?f=90 upon release.
- We fixed multiple crashes, and we are very interested in any crashes you might experience with the new client. Please post any new crash-dumps to http://forum.teamspeak.com/showthread.php?t=46880
- We renamed Token" to "Privilege Key". We hope the new name will give new users a better mental image of what exactly this functionality is used for.
- Some users (mostly dial-up or non-broadband) had problems with the bandwidth requirements that TeamSpeak 3 demands (higher than in TeamSpeak 2), for these users we added the new delay parameter in the codec setup. It essentially allows you to reduce the bandwidth demands at the cost of the speed at which your transmissions are received. For example to have the same bandwidth usage as TeamSpeak 2 did you could go with (Speex 8kHz, Quality 7, Delay 100ms). The default value is a delay of 20ms which is the same behavior as in previous TeamSpeak 3 releases.
- "Commander" like whisper functionality is now possible: Simply create a new channel group (e.g. name it "Channel Commander"). Then go into the whisper list setup, and add a hot-key to whisper to this new channel group - that's all it needs.
- From this release forward there will be two "branches" of releases from which you can chose: The default is the "stable" branch which only contains well tested versions. The alternative is the "beta" branch which will give you the newest cutting edge client releases that might not have been tested as much yet. To tell your updater to use releases from the beta branch you need to run the updater once, then edit the configuration file "update.ini" and add the following code into this file:
If there any questions please contact us.