« Read all Developer Blogs
||Development Updates & First Screenshots
by Peter Kirk on Feb 13, 2006
First we'd like to apologize for being a little behind "schedule" here on our developer blog posts, as we wanted to get at least one post into the developer blog per month. On the development side we have been working busily, and have even convinced ourselves to allow the first screenshots ever to be released to public.
Of course, these alpha shots are NOT indicative of the final product - the interface and the features will continue to change, as TeamSpeak 3 is still a work in progress. The screenshots above indicate connection info which is opened on a remote client. You might also notice (if you look closely) that there are three individual, connected clients called "*_IntelMac", "*_linux64" and "_win32". These are not mere names, we have a TeamSpeak 3 client and server running on:
Support for additional operating systems and platforms will be added after we launch TeamSpeak 3.
- Mac OS X (both Intel based and PPC)
- Windows (32Bit and 64Bit)
- Linux (32Bit and 64Bit)
The windows screenshot was taken on Windows XP with classic design (no flashy icons for us hardcore developers :D)
As you may have noticed, with pings of 0, the three clients and server are all on the same LAN, and yet we have packet loss of approximately 2%. "How can that be?", the clever reader may ask himself. The answer is simple - we are currently using "fake" packet loss for testing and debugging purposes. This packet loss is generated by the client/server software (we just drop random packets), and will not occur in the final version, and is strictly for testing purposes :D.
Although you cannot see it on the screenshots (because they aren't animated gifs), the connection info is designed to refresh itself automatically, so you don't need to reopen the darn thing all the time just to see if anything is changing.
On a different topic, the most important feature of TeamSpeak 3 (the "talking" part) is already implemented. There is still some work to be done, but we are able to talk with each other using TeamSpeak 3, using a much higher audio codec resulting in much clearer voice quality (and of course utilizing lots of bandwidth :P) than is possible in TeamSpeak 2. Even though there is still an outstanding TODO list negatively affecting the latency of voice transmission, we have already significantly lowered the latency of speech compared with TeamSpeak 2.