@Gamer92000 How were you able to debug it and find the exact code causing the issue? I find that really interesting!
You have to start teamspeak using the parameter --remote-debugging-port=<port> and specify a desired port.
Then you can connect to this with any chromium browser like chrome, opera, brave, etc.
localhost:<port>
There you click on TeamSpeak Client UI. This will give you a chrome-like debugging interface - as TeamSpeak 5 is an electron (like) application, afaik.
There you will instantly see the errors printed to the console. When clicking on the location on the right hand side:
the file containing the faulting code will open. This will just be one line of unreadablity.
You will need to press the two brackets at the bottom left to get a nice view of the code:
Then you can click on the link in the console again and will be brought to the section.
2 Likes
Anyway we are gonna get a fix for? Any workaround? Quite some time since last update to the beta.
Everything regarding this error is listed here.
Currently the only workaround is to disable error sound inside client.
