Forum

Page 3 of 4 FirstFirst 1234 LastLast
Results 31 to 45 of 56
  1. #31
    Join Date
    June 2018
    Posts
    21
    Quote Originally Posted by dante696 View Post
    And which server and client version is this?
    What is in your server logs?

    edit
    Have you changed your myTeamSpeak e-mail or password with client 3.2?
    Since I made myteamspeak account, I did not change the e-mail and password. I use 3.3.0 server version 3.2.0 client version. I have just started running.

  2. #32
    Join Date
    June 2008
    Posts
    18,151
    Could you please show your client log and server log?
    Please enable logging for clients and reconnect at least once before you show the server log.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  3. #33
    Join Date
    June 2018
    Posts
    21
    Quote Originally Posted by dante696 View Post
    Could you please show your client log and server log?
    Please enable logging for clients and reconnect at least once before you show the server log.
    Client Log

    Code:
    3.7.2018. 09:53:52		Info	TeamSpeak 3 Client 3.2.0 (2018-06-29 13:47:51)	
    3.7.2018. 09:53:52		Info	SystemInformation: Windows 7 SP1 (7601) x64 (AMD or Intel) Binary: 64bit	
    3.7.2018. 09:53:53	Direct Sound	Debug	setting timer resolution to 1ms - 	
    3.7.2018. 09:53:55	SoundBckndIntf	Error	C:/Program Files/TeamSpeak 3 Client/soundbackends/directsound_win64.dll error: NO_DEFAULT_FOUND	
    3.7.2018. 09:53:55	SoundBckndIntf	Error	C:/Program Files/TeamSpeak 3 Client/soundbackends/directsound_win64.dll error: NO_DEFAULT_FOUND	
    3.7.2018. 09:53:55	Windows Audio Session	Error	GETTING_DEFAULTAUDIOENDPOINT: Element not found. - 	
    3.7.2018. 09:53:55	SoundBckndIntf	Error	C:/Program Files/TeamSpeak 3 Client/soundbackends/windowsaudiosession_win64.dll error: GETTING_DEFAULTAUDIOENDPOINT	
    3.7.2018. 09:53:56		Info	*** Time [SPAWN_EVENTCONVERTER]: 4052	
    3.7.2018. 09:53:56	ClientUI	Info	OpenGL Info: LibGLES, Vendor: Google Inc., Renderer: ANGLE (NVIDIA GeForce 9200 Direct3D11 vs_4_0 ps_4_0), Version: OpenGL ES 2.0 (ANGLE 2.1.99f075dade7c)	
    3.7.2018. 09:53:59		Info	successfully downloaded revocation list for myteamspeak id	
    3.7.2018. 09:53:59		Info	successfully downloaded revocation list for accounting	
    3.7.2018. 09:54:03		Info	*** Time [ICONMANGER]: 6939	
    3.7.2018. 09:54:03	Addons	Info	Checking for addon updates...	
    3.7.2018. 09:54:04	Addon	Info	Addon up to date.	
    3.7.2018. 09:54:04	Addon	Info	Addon up to date.	
    3.7.2018. 09:54:04	Addon	Info	Addon up to date.	
    3.7.2018. 09:54:08	Plugins	Info	Loading plugin: clientquery_plugin_win64.dll	
    3.7.2018. 09:54:10	Query	Info	listening on 127.0.0.1:25639	
    3.7.2018. 09:54:10	Plugins	Info	Loading plugin: gamepad_joystick_win64.dll	
    3.7.2018. 09:54:10	Gamepad Plugin	Info	Found client raw input wnd proc	
    3.7.2018. 09:54:10	Gamepad Plugin	Info	Cleared device list	
    3.7.2018. 09:54:11	Plugins	Info	Loading plugin: teamspeak_control_plugin_win64.dll	
    3.7.2018. 09:54:11	ControlPlugin	Warning	Failed to initialize Control Plugin	
    3.7.2018. 09:54:11		Info	*** Time [PLUGINS]: 3174	
    3.7.2018. 09:54:18		Info	*** Time [CHAT_WIDGETS]: 2908	
    3.7.2018. 09:54:19		Info	*** Time [MAINWINDOW_ACTIONS]: 373	
    3.7.2018. 09:54:19		Info	*** Time [CONTACTS]: 139	
    3.7.2018. 09:54:19		Info	*** Time [REMOTEIMAGEFETCHER]: 251	
    3.7.2018. 09:54:21		Info	*** Time [EVENTCONVERTER]: 196	
    3.7.2018. 09:54:21	Windows Audio Session	Devel	DeviceDeleteList::wait_for_deletes - enter - DeviceDeleteList	
    3.7.2018. 09:54:21	Windows Audio Session	Devel	DeviceDeleteList::wait_for_deletes - leave - DeviceDeleteList	
    3.7.2018. 09:54:22		Info	*** Time [TREE]: 600	
    3.7.2018. 09:54:22		Info	*** Time [INFOFRAME]: 162	
    3.7.2018. 09:54:24		Info	*** Time [BUILD_GUI]: 2271	
    3.7.2018. 09:54:25		Info	*** Time [SERVERVIEW_ACTIONS]: 310	
    3.7.2018. 09:54:25		Info	*** Time [FINAL]: 270	
    3.7.2018. 09:54:25		Info	*** Time [SERVERVIEW]: 3894	
    3.7.2018. 09:54:25		Info	*** Time [SERVERVIEWMANAGER]: 6048	
    3.7.2018. 09:54:26		Info	*** Time [MAINWINDOW_MENU_AND_TOOLBAR]: 195	
    3.7.2018. 09:54:29		Info	*** Time [MAINWINDOW]: 38539	
    3.7.2018. 09:54:29		Info	*** Time [INIT]: 38633	
    3.7.2018. 09:54:29	ClientUI	Devel	Notifications init: Soundpack path: C:/Program Files/TeamSpeak 3 Client/sound\default	
    3.7.2018. 09:54:29		Info	current mytsid data is invalid - request new	
    3.7.2018. 09:54:29		Info	requested new mytsid data	
    3.7.2018. 09:54:30		Info	set_new_myteamspeak_id returned internal error	
    3.7.2018. 09:54:31		Info	*** Time [NOTIFICATIONS]: 2474	
    3.7.2018. 09:54:31	ClientUI	Info	Qt version: 5.6.2	
    3.7.2018. 09:54:31	ClientUI	Info	Using configuration location: C:\Users\Sanel\AppData\Roaming\TS3Client\settings.db	
    3.7.2018. 09:54:33	Bookmarks	Info	Collecting autoconnect bookmarks	
    3.7.2018. 09:54:33	ClientUI	Info	Last update check was: pon srp 2 10:40:37 2018	
    3.7.2018. 09:54:33	ClientUI	Info	Checking for update	
    3.7.2018. 09:54:34	Update	Info	Checking for updates...	
    3.7.2018. 09:54:39	Newsticker	Info	Newsticker next check: pon srp 2 19:55:43 2018	
    3.7.2018. 09:54:42	Update	Info	Check license: version=3, min_version=3, my_license_version=3, my_license_min_version=3	
    3.7.2018. 09:54:42	Update	Info	Check client version: 3.2.0 1530280071	
    3.7.2018. 09:54:42	Update	Info	Update check, my version: 1530280071, latest version: 1530280071	
    3.7.2018. 09:54:42		Info	Statistics report: Not yet, next report on sub srp 7 10:41:41 2018	
    3.7.2018. 09:54:42	Newsticker	Info	Newsticker not found for language hr	
    3.7.2018. 09:54:43	Newsticker	Info	Newsticker received for language hr, expires on uto srp 3 12:24:42 2018, next check in 1800 seconds	
    3.7.2018. 09:56:06	ClientUI	Info	Connect to server: localhost	
    3.7.2018. 09:56:06	ClientUI	Info	Trying to resolve localhost	
    3.7.2018. 09:56:06	TSDNS	Info	A/AAAA DNS resolve successful, "localhost" =(h: 127.0.0.1 p:0)	
    3.7.2018. 09:56:06	ClientUI	Info	Lookup finished: ip=127.0.0.1 port=9987 query=localhost error=0	
    3.7.2018. 09:56:06	ClientUI	Info	Resolve successful: 127.0.0.1:9987	
    3.7.2018. 09:56:06	ClientUI	Info	Initiating connection: 127.0.0.1:9987	
    3.7.2018. 09:56:07	Windows Audio Session	Devel	DeviceDeleteList::wait_for_deletes - enter - DeviceDeleteList	
    3.7.2018. 09:56:07	Windows Audio Session	Devel	DeviceDeleteList::wait_for_deletes - leave - DeviceDeleteList	
    3.7.2018. 09:56:07	Windows Audio Session	Debug	WAS::openDevice-enter - {0.0.0.00000000}.{e24e58c1-2776-424c-bfbb-a58442f27dfd}	
    3.7.2018. 09:56:07	Windows Audio Session	Devel	Mix Format: SRate:44100 Bitrate: 32 Channels: 2 - Speakers (2- High Definition Audio Device)	
    3.7.2018. 09:56:07	Windows Audio Session	Devel	Initializing with mix format. - Speakers (2- High Definition Audio Device)	
    3.7.2018. 09:56:07	Windows Audio Session	Info	Initialized with 2 channels in 32bit, 44.1kHz. - Speakers (2- High Definition Audio Device)	
    3.7.2018. 09:56:07	Windows Audio Session	Devel	WAS Buffer size: 896 - Speakers (2- High Definition Audio Device)	
    3.7.2018. 09:56:07	Windows Audio Session	Debug	WAS::openDevice-leave - {0.0.0.00000000}.{e24e58c1-2776-424c-bfbb-a58442f27dfd}	
    3.7.2018. 09:56:07	Windows Audio Session	Debug	WAS::startDevice-enter - {0.0.0.00000000}.{e24e58c1-2776-424c-bfbb-a58442f27dfd}	
    3.7.2018. 09:56:07	Windows Audio Session	Debug	WAS::startDevice-leave - {0.0.0.00000000}.{e24e58c1-2776-424c-bfbb-a58442f27dfd}	
    3.7.2018. 09:56:07	ClientUI	Info	LIMSTOPWATCH onEditMixedPlaybackVoiceDataEvent (recorder): 77 ms 10	
    3.7.2018. 09:56:07	Windows Audio Session	Debug	[Playback] RenderDeviceContext inner loop lasted > 20 ms 78 - Speakers (2- High Definition Audio Device)	
    3.7.2018. 09:56:08	Windows Audio Session	Devel	DeviceDeleteList::wait_for_deletes - enter - DeviceDeleteList	
    3.7.2018. 09:56:08	Windows Audio Session	Devel	DeviceDeleteList::wait_for_deletes - leave - DeviceDeleteList	
    3.7.2018. 09:56:09	SyncImpl	Error	Error getting myteamspeak id: invalid_data	
    3.7.2018. 09:56:09	ClientUI	Info	Connect status: Connecting	
    3.7.2018. 09:56:09	PktHandler	Devel	Puzzle solve time: 16	
    3.7.2018. 09:56:10	ClientUI	Info	Connect status: Connected	
    3.7.2018. 09:56:10	ClientUI	Info	Connect status: Establishing connection	
    3.7.2018. 09:56:10	ClientUI	Info	Connect status: Connection established	
    3.7.2018. 09:56:10	PermManager	Info	Loading permissions from cache	
    3.7.2018. 09:56:21	Windows Audio Session	Debug	[Playback] RenderDeviceContext inner loop lasted > 20 ms 74 - Speakers (2- High Definition Audio Device)	
    3.7.2018. 09:56:23		Info	requested new mytsid data	
    3.7.2018. 09:56:23		Info	set_new_myteamspeak_id returned internal error
    Server Log
    3.7.2018. 09:52:38 VirtualServer Info listening on 0.0.0.0:9987, [::]:9987
    3.7.2018. 09:56:10 VirtualServerBase Info client connected 'Sanel_Pandzic'(id:2) from ??????:64833
    Last edited by dante696; July 3rd, 2018 at 01:06 PM. Reason: bbcode added

  4. #34
    Join Date
    June 2008
    Posts
    18,151
    Code:
    3.7.2018. 09:56:23 Info requested new mytsid data
    3.7.2018. 09:56:23 Info set_new_myteamspeak_id returned internal error
    That's the cause. Will talk to developers.

    Update
    It could be that you did trigger a bug that was inside the first beta version. The bug was fixed in beta 2 already, but you need to manually trigger a re-creation of the myTS ID.

    Possible soloution
    - Logout from myTeamSpeak and then login back into your account. Then reconnect to server.
    - When above did not solve the problem, try to change your account password. You can change it back afterwards.

    will move our conversation to client thread https://forum.teamspeak.com/threads/136236
    Last edited by dante696; July 3rd, 2018 at 01:06 PM. Reason: removed old stuff
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  5. #35
    Join Date
    May 2010
    Location
    Germany
    Posts
    12
    You can not connect to an older server than version 3.2.0 !

    === Client Release 3.2.0 27 Jun 2018
    ! Dropped support for pre 3.1.0 TeamSpeak servers.


    I also misunderstood it because there is "support"!
    Support is for me Lifetime/Helpdesk for this version

    I think that better in a clear statement how:
    You can not connect to an older server than version 3.2.0 !

    Because i think a lot of server running on 3.1.10

    How can I downgrade, or do I have to reinstall?

  6. #36
    Join Date
    June 2011
    Location
    Germany
    Posts
    4,350
    Quote Originally Posted by SoundY View Post
    === Client Release 3.2.0 27 Jun 2018
    ! Dropped support for pre 3.1.0 TeamSpeak servers.


    I also misunderstood it because there is "support"!
    Support is for me Lifetime/Helpdesk for this version
    TeamSpeak not giving support for a certain server software version is nothing client users care about at all, so why would it be in the client changelog?
    Note that beta is not for everyone but merely experienced users and developers. In software development, "dropping support" is a very common expression.
    Let's see when 3.2.0 sees its official release, but I assume many will deem it too early.

    Quote Originally Posted by SoundY View Post
    I think that better in a clear statement how:
    You can not connect to an older server than version 3.2.0 !

    Because i think a lot of server running on 3.1.10
    There is no server version 3.1.10. They skipped from 3.1.3 to 3.2.0. The 3.2.0 TeamSpeak client is supposed to be able to connect to servers newer than (not including) 3.0.13.8. There was absolutely no relevant change in 3.2.0.

    Quote Originally Posted by SoundY View Post
    How can I downgrade, or do I have to reinstall?
    There is no supported way.

  7. #37
    Join Date
    June 2018
    Posts
    21
    Quote Originally Posted by dante696 View Post
    Code:
    3.7.2018. 09:56:23 Info requested new mytsid data
    3.7.2018. 09:56:23 Info set_new_myteamspeak_id returned internal error
    That's the cause. Will talk to developers.

    Update
    It could be that you did trigger a bug that was inside the first beta version. The bug was fixed in beta 2 already, but you need to manually trigger a re-creation of the myTS ID.

    Possible soloution
    - Logout from myTeamSpeak and then login back into your account. Then reconnect to server.
    - When above did not solve the problem, try to change your account password. You can change it back afterwards.

    will move our conversation to client thread https://forum.teamspeak.com/threads/136236
    Thank you, I solved the problem

  8. #38
    Join Date
    July 2018
    Posts
    1

    Username changes after losing connection and reconnecting

    After I updated to Teamspeak version 3.2.0 Beta every time I lose connection to a Server it changes my Username to my myTeamspeak Username.

    As you can see in the screenshot I set my Username as "Test123" but it gets changed to my myTeamspeak Username after I reconnect.
    Attached Images Attached Images  
    Last edited by dante696; July 6th, 2018 at 02:49 PM. Reason: merged

  9. #39
    Join Date
    June 2008
    Posts
    18,151
    Good catch. We can reproduce this and you are right client 3.1.10 did not has this problem.
    On reconnect the nickname set in identity is used instead of using the name you had before. I will forward this to our developers.

    Next beta client will fix this.

    Thread merged from bug section to existing beta thread
    Last edited by dante696; July 6th, 2018 at 02:48 PM.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  10. #40
    Join Date
    January 2016
    Posts
    12

    Exclamation

    I'm having many problems of Teamspeak 3 3.2.0 Beta crashing all time (No responding window, and audio not working neither). I have to kill the process with Task Manager. Is any having the same issue?

    It's excessive, during a day (8 hours) it crashes 4-5 times. No specific reason and seems to be quite aleatory.

    I'm a really long user of TS, and never ever crashed, but with the latest BETA something is going on

  11. #41
    Join Date
    June 2008
    Posts
    18,151
    Can you offer as client log or a crash dump where your crash/freeze happened?
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  12. #42
    Join Date
    January 2016
    Posts
    12
    Indeed there's no crash dump as did not crash just stopped working (white window, and no way of recovering it), I have to manually close it with task manager.


    EDIT: corrected the log file
    Attached Files Attached Files
    Last edited by By-Jokese; July 11th, 2018 at 05:39 PM.

  13. #43
    Join Date
    June 2008
    Posts
    18,151
    You showed the wrong log file.
    This log is from outdated client 3.1.8 and not 3.2.0

    ------------------------------------------------------------------


    Can you try to run the client a without plugins being loaded?
    Way one use start parameter -safemode when you start the client.
    Way two is to turn off the plugins manually under Tools -> Options -> Addons.
    Last edited by dante696; July 11th, 2018 at 04:13 PM. Reason: removed some stuff because wrong log offered
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  14. #44
    Join Date
    November 2006
    Location
    Kent - UK
    Posts
    64
    anymore information on this?
    - Made styling for server integration management dialog possible.
    Last edited by Martyn; July 13th, 2018 at 04:32 PM.

  15. #45
    Join Date
    June 2008
    Posts
    18,151
    Old beta did not allow to change the color for background in integration dialog.
    The background is now invisible instead of being white and it can be changed in the qss file.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. [Discussion] TeamSpeak 3 Client 3.1.8 Beta
    By Chris in forum Suggestions and Feedback
    Replies: 18
    Last Post: January 21st, 2018, 12:19 PM
  2. [Discussion] TeamSpeak 3 Client 3.1.7 Beta
    By Chris in forum Suggestions and Feedback
    Replies: 20
    Last Post: December 13th, 2017, 08:00 PM
  3. [Discussion] TeamSpeak 3 Client 3.1.6 Beta
    By Chris in forum Suggestions and Feedback
    Replies: 10
    Last Post: August 16th, 2017, 12:43 PM
  4. [Discussion] TeamSpeak 3.1.1 Beta Discussion
    By Chris in forum Suggestions and Feedback
    Replies: 15
    Last Post: February 10th, 2017, 05:02 PM
  5. [Discussion] TeamSpeak 3 Client 3.1 [BETA]
    By KIDINK^ in forum Suggestions and Feedback
    Replies: 249
    Last Post: January 10th, 2017, 03:12 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
  •