Nope. The next update will primarily focus on performance improvements and bug fixes (it's still a big update tho). We are aware that permissions are a thing and we'll add the functionality asap....

Yes... dark mode support would be awesome! :cool:

18446

We've identified another issue with our CDN and fixed it. The update should work fine now.

My apologies for any inconvenience!

This should be fixed now... please let us know if you experience any other issue.

I admit the last sentence is a bit confusing. The global chat is not related to a specific TeamSpeak Server so you can use it regardless of where your server host hosted. Basically, what it means...

There's something in the air...

https://www.youtube.com/watch?v=yYQjw6NJBjo

Every TeamSpeak Server is shipped with a free default license for 32 slots. These licenses have expiration dates (in this case July 1st, 2020). We're updating these licenses on a regular basis... so...

Looking into the client logs you've provided I'd say your PC is very slow in general... is that correct?

Well... why should I confirm something that was allegedly spilled by someone at our booth? That somehow questions the authenticity of the information.

:confused:

We didn't do any changes regarding font sizes in the latest client releases. Have you been using 3.3.0 before?

Version 3.3.2 is available on all update channels now. Thank you for your report!

Das Update auf Version 3.3.1 sollte den Fehler beheben.

Please send me a PM with the IP of the server where this is happening and we'll take a look. I have a slight idea what it could be, but like dante, I'm unable to reproduce it on my end.

Did not follow the thread for a while tbh... what's the question?

Working as intended... for now we're just prevent being crashed remotely.

;)

This thread is supposed to collect feedback and bug reports for the TeamSpeak Client release 3.3.x series.

Please refer to the release announcement to get a list of changes.

:)

We've just published new version of the TeamSpeak Client. This hotfix release provides a number of bug fixes and improvements. Please refer to the changelog for a full list of changes:


===...

A new client build was just put in the oven... version 3.3.1 should resolve this issue (and a few others). It will be available on the beta channel later today.

This will be fixed with version 3.3.1. Thank you for reporting this!

:o

Yes, he did. I've merged the posts into this thread now...

:)

The original thread creator deleted it... I have restored it now.

Makes sense.

Ok. Thanks for the clarification.

First and last visit in YaTQA are basically first connected and last connected. That's why I was asking...

So... what you're asking for is basically a "last disconnected" thing right?

Finally some questions!

:D

I can neither confirm nor deny... blah blah... seriously... if you look at the images we've published, the answer should be quite obvious, right?

We have a release...

Sorry guys... but this „discussion“ is over now. Feel free to provide constructive feedback or ask meaningful questions about TS5 in new threads.

Well... that's Qt. But hey... at least emojis are colored now on Windows.

:p

Unfortunately, those are outdated. Please re-send your current crashdumps and logs so we can investigate the issue.

We're getting closer every day. Just a little more patience please.

:)

Yes, we have thought about changing our hashing algorithm, but there's no need to change this immediately. Also, it would cause a lot of trouble for our users.

Indeed, you could exploit this......

Zwei Fragen:


Sind ALLE Nutzer in ALLEN Channels betroffen sobald der Fehler auftritt?
Löst das Wechseln des Channels das Problem für einzelne Nutzer?

Please send me a PM with your client log when this happens so we can further investigate this.

Any plugins running?

Glad to hear! Apologies for the inconvenience.

;)