Thank you all for the continuous feedback and reports following the recent updates. Your input has been incredibly helpful in tracking down remaining issues.
This Hotfix focuses on resolving problems related to special characters in file paths, which could prevent the client from starting or disrupt file transfer operations on certain systems. On Windows, this update specifically fixes issues that occurred when running TeamSpeak under user accounts with names containing special characters.
For affected users:
If you’re still experiencing crashes or startup issues since beta3 or beta3.1, please use the link below to perform a fresh installation of beta3.2 by downloading it from our Website.
Before performing a fresh installation, please make sure to uninstall TeamSpeak from your system & delete your installation folder, e.g., C:\Program Files\TeamSpeak, and then install TeamSpeak again using the beta3.2 installer below.
If you’re still experiencing issues after performing a fresh installation of beta3.2 as prompted above, please clear your cache folder located at %localappdata%/TeamSpeak, then try starting the client again.
We’re closely monitoring all incoming feedback and will continue to address reported issues as quickly as possible.
This hotfix addresses several issues with special characters in file paths, which block the client start and affect file transfer operations on some machines. On Windows, it specifically resolves issues when running TeamSpeak under user accounts with names containing special characters.
Bug Fixes
Fix UTF-8 encoded string handling in filepaths for cache/settings creation and file-transfer operations
Please Note:
As always, feedback is welcome here. Please note that issues unrelated to this update should be discussed in their own dedicated threads.
We encourage you to share your suggestions for future releases in the appropriate threads within the suggestions and feedback area, rather than in the release thread. This is because update posts are typically closed after some time, and suggestions or feature requests may get overlooked.
We reserve the right to remove any off-topic posts from this thread.
Since version beta3 the client starts as a wayland window by default if running under a wayland session. To restore the original behavior of a xwayland window you can simply start the client with the --ozone-platform=x11 parameter.
does somehow performance loss count towards this thread?
Im on mid-endish specs
5 3600 - stable 4.2ghz on 1.33v
rtx 2060 - stable and oced
3200 cl16 oced to 3666 cl16 with tighter timings
and im experiencing bigger fps loss then streaming on discord(doesnt matter what settings i use, i tried to change bitrate/fps/changing codec/settings in codec}.
For example in valorant i lost 50 fps while streaming but in apex from consistent 144 fps i was getting drops to 90/100 fps and was averaging 130 with those drops.
here are advanced settings(changing those as i said before didnt improve fps but sometimes they improved stream image)
i didnt change anything in decoding
no i did not try without it - ill test it.
changing game priority doesnt really help on windows, it might cause more issues it is better to let windows handle it - valorant is automatically on high priority and teamspeak on normal
after tests:
same thing happens from 300 fps drops to 250(50 fps drop)
I am really happy with this release overall. Screen sharing performance is significantly better now, and I will argue that it has the ability to look better than Discord at times. Where Discord requires a Turbo subscription for the best quality, the base Community subscription seems to offer even better quality options for the stream. Because we are limited to peer-to-peer, friends in my home state have streams that are much smoother than those farther away. While the quality overall is much better than it was before, the peer-to-peer nature of most connections leads to a lot of “hiccups / hitching / freezing” (not low quality).
I see a separate reply indicating that server-side screen sharing is a significant undertaking, and I completely understand this. I eagerly await future releases. I have two questions though:
1 - Will TeamSpeak Communities have server-side screen sharing as an option? Or just self-hosted servers?
2 - Will there be an additional cost and/or bandwidth limit for server-side screen sharing in a TeamSpeak Community?
I ask these questions because if we aren’t adding server-side screen sharing to Communities, and if we are going to need to pay more or be limited on bandwidth, I may have additional questions about the value proposition for paying for a Community versus self-hosting.
Again, absolutely loving everything so far. And truly appreciate Syox and the remainder of the team’s dedication to answering questions on the forum!