Forum


Notice to all users

We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020

Results 1 to 13 of 13
  1. #1
    Join Date
    June 2002
    Location
    Krün / Germany
    Posts
    1,638

    TeamSpeak 3 Client 3.0.0-beta13 Available

    We've just finished uploading version 3.0.0-beta13 of the client. Here's a list of changes:

    Code:
    === Client Release 3.0.0-beta13 - 02 Feb 2010
    * Added automatic scroll to tree when dragging items to the top or lower margin
    - Fixed context menu for a downloaded directory.
    - Fixed a download bug where the actual channel folder wasn't respected.
    - When adding integer permissions and grant permissions, first let the user
      input the value and then send it to the server to avoid sending double data.
    - Added button to options to reset all "Are you sure...?" confirmations.
    - Added confirmation when setting grant permission to zero.
    - Don't ask "You are still connected to..." when closing server tab if you
      actually are not connected
    + Added option "Always stay on top" in application settings (Windows only).
    - Fixed "Channel maxclient reached" pop up menu doesn't save answer 
    - Refilter permissions tree when "show granted only" is enabled and a
      permission is removed.
    * No longer check for "config" directory in installation directory when
      deciding the configuration location
    * Added server address and port to last-seen information in contacts
    - "User requested talk power" sound only played if user is in own channel
    - Fixed wrong TTS channelname with connected sound
    + Added customizable toolbar buttons (most icons are still too small. They will
      be updated with a later release.)
    * Updated German translation
    - Automatically unmute users when they are removed from contacts list
    * Added Edit virtualserver menuitem to Self menu
    - Closing edit virtualserver dialog with Escape will also trigger the discard/
      apply dialog
    - Fixed possible marking the edit virtual server dialog modified after opening
    - Fixed typo in hotkey setup, so "Status change - Deactivate" works again. 
    * Individually handle permissions to view server/channel group tabs and display
      notification in the permission and client widget if they cannot be viewed.
    * Initialize only those permission tabs for which permission was granted to
      avoid invalid permission error spam.
    - Removed -enableallactions commandline option.
    - Fixed restoring server and channel groups on reconnect when keeping the
      permissions window open.
    - Fixed strange behaviour of toggle microphone hotkey in combination with auto-
      activate microphone when switching server tabs.
    * Reload chatlog when connecting to a new server in the same tab
    * Tweaked autoscrolling after reloading logs
    - Fixed creating hotkeys (no keys were accepted / gray box stayed always open)
    * Play talk-power-requested sound only if user has permission to grant it
    * Changed serverquery clear highlight button shortcut to Backspace, so Escape
      key is available for closing the window again.
    + Escape always closes hotkey dialog, even if hotkey input doesn't work.
    * Allow multiple whitespaces in channel description.
    + Added use of server-, channel- and client info templates. Look into
      the folder styles\default for premade templates, which can be modified
      for different styles and languages.
    + Added server address:port in server info.
    - Fixed pasting a text into hotkey rename field.
    Windows users that lost their settings after update:
    If after the update your settings are gone this is due to the client not finding the configuration files any more, nothing is lost, don't panic . This should only occur when during the install you asked teamspeak to place the config files into the %appdata% folder ("Each user has his own configuration"), but somehow managed to create a "config" folder in the installation folder. The solution is simple: Stop the Client and copy the contents of the config folder in your TS3 Client installation into %appdata%/TeamSpeak 3 Client/. After restarting the client again your settings should be back.

    Have fun downloading (or using the auto-updater )

  2. #2
    Join Date
    December 2009
    Location
    Tunisia
    Posts
    37

    Attention:
    From now, all Linux version must start with an startscript, this is included in the main folder of the teamspeak3 client installations

  3. #3
    Join Date
    January 2010
    Location
    Germany
    Posts
    26
    Auto-updater:
    Today, times have used the auto updater. 've Found here that my favorite entries, styles and other settings were gone. Weird.
    Is it so intended? Should I create any backup before?
    (translated with google ^ ^)

  4. #4
    Join Date
    December 2009
    Location
    Netherlands
    Posts
    18
    @JackCimberly:

    Windows users that lost their settings after update:
    If after the update your settings are gone this is due to the client not finding the configuration files any more, nothing is lost, don't panic . This should only occur when during the install you asked teamspeak to place the config files into the %appdata% folder ("Each user has his own configuration"), but somehow managed to create a "config" folder in the installation folder. The solution is simple: Stop the Client and copy the contents of the config folder in your TS3 Client installation into %appdata%/TeamSpeak 3 Client/. After restarting the client again your settings should be back.

  5. #5
    Join Date
    August 2009
    Location
    Österreich
    Posts
    18
    Mini Bug:
    In the german translation:

    Codec Qualität: 8 estimated bitrate: 5.71 KiB/s

    estimated bitrate is here in english and not in german!
    I had an Win 32 + 64 Bit System!

  6. #6
    Join Date
    December 2009
    Location
    Germany, Cologne
    Posts
    1,364
    Updated and: Works fine!

  7. #7
    Join Date
    January 2010
    Location
    Germany
    Posts
    26
    Quote Originally Posted by rolfie View Post
    @JackCimberly:
    Thank you

  8. #8
    Join Date
    December 2009
    Location
    Stuttgart
    Posts
    29
    Quote Originally Posted by stegmuellerm View Post

    Attention:
    From now, all Linux version must start with an startscript, this is included in the main folder of the teamspeak3 client installations
    If you open the script with a text editor and understand what it's doing, you can still start it the old way.
    Simply export that var and start the server the old way. Works fine for me.
    Had to do it the old way 'cause the script only checks for the user who started the script, but as i set the setuid bit to another user the server starts using another user even if started as root. http://de.wikipedia.org/wiki/Setuid

  9. #9
    Join Date
    June 2006
    Location
    England, Hertfordshire
    Posts
    249
    Apparently, clients in servergroups is not shown with beta13, only beta12. I hope the server update to 17 will fix this...

  10. #10
    Join Date
    December 2009
    Posts
    244
    Clients are shown fine for me in Client Beta13 w/ Beta17 Server

  11. #11
    Join Date
    July 2002
    Location
    Germany
    Posts
    2,191
    Quote Originally Posted by karimali831 View Post
    Apparently, clients in servergroups is not shown with beta13, only beta12. I hope the server update to 17 will fix this...
    Yes indeed. Did you notice that big Pop-Up box that came up when you connected? The one saying server is outdated? The one saying members of permission groups would not be displayed correctly because of it? I hope you clicked ok and didn't read it, because that is ALWAYS the best thing to do.

  12. #12
    Join Date
    June 2006
    Location
    England, Hertfordshire
    Posts
    249
    Quote Originally Posted by Peter View Post
    Yes indeed. Did you notice that big Pop-Up box that came up when you connected? The one saying server is outdated? The one saying members of permission groups would not be displayed correctly because of it? I hope you clicked ok and didn't read it, because that is ALWAYS the best thing to do.
    Stating not complaining and update fixed, thanks

  13. #13
    Join Date
    January 2009
    Location
    Germany
    Posts
    29
    Last edited by dextar; February 4th, 2010 at 05:42 PM.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. [Resolved] [Teamspeak Client] Client list search (CTRL+F)
    By bbqeater in forum Bug Reports [EN/DE]
    Replies: 3
    Last Post: February 24th, 2015, 10:35 AM
  2. Replies: 3
    Last Post: August 2nd, 2010, 07:47 AM
  3. IMPORTANT - BETA13 Server!
    By LostSoulBS in forum Suggestions and Feedback
    Replies: 4
    Last Post: January 18th, 2010, 01:09 PM
  4. Upcoming Changes... client beta10, server beta13
    By R. Ludwig in forum Archive
    Replies: 3
    Last Post: January 14th, 2010, 03:58 PM
  5. insufficient permission modify power Beta13 fix?
    By mavmike in forum Permission System
    Replies: 4
    Last Post: January 12th, 2010, 10:40 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •