I believe it happens only to users who have a bad ping to the server. When it reaches a certain threshold, the user will drop.Well I already noticed this issue as well.
Sometimes TeaSpeak disconnects client earlier then Tea*Speak.
Im already investigating this issue, but haven't really a clue because of the randomness.
Yes I have done this.I don't have any issues with connection from (3.2.0 beta) to TeaSpeak Server. anything works fine here
Just be sure. you has enabled the 31exp on config.yml and updated protocol_key ^^
I have not experienced it.Yes I have done this.
The problem is with users randomly disconnecting with the message No ping response. This is unrelated to the 3.2b client but is a problem with the TeaSpeak server.
Ok regarding this issue (needing to connect twice with 3.2b client):
Well I already noticed this issue as well.
Sometimes TeaSpeak disconnects client earlier then Tea*Speak.
Im already investigating this issue, but haven't really a clue because of the randomness.
Has this been fixed on the latest version?
- Improved connection handling
What notification? I meant if the time out problem has been fixedYes the notification is fixed with the newest version
@FSKiller
- You will find it under "Bookmarks > Manage Bookmarks > Click: Go Advanced > And you need to untick: "Send myTeamSpeak ID"
or you can like this: Ctrl+S > click More > untick: Send myTeamSpeak ID