So, in an effort to drop in something at the last minute for the holidays, Ray has been trying to fix the leaky Voice Chat stuff tonight.

He's pushed a "release" into production, using some code modifications.. we think we may have tracked down the problem, but we aren't sure that it's actually "fixed".

Unfortunately, it's very time consuming to try and test; so for the moment, the best we can do (for tonight) is just push this out, and ask people to let us know how it works.

(Ray may also try testing it at home later, but feedback is still appreciated).

Thanks all, have fun.

Deja vu.

Pffttttbahahahha

Hey, we had a support ticket about the voice chat stuff earlier, so we tried to burn a few hours to definitely fix it.

We didn't write the voice chat system, so Ray is debugging unfamiliar code written in an unfamiliar language, which plugs into someone else's binary.. and it apparently the code enough bugs that he keeps genuinely fixing things, but it still doesn't work right. That, and it can be quite challenging to test all the different states and conditions of people joining and leaving channels (but it only requires one rare edge case to create a recurring problem).

We didn't leave the office until after midnight tonight, trying to resolve this. I'm just asking for feedback and reports if you experience issues.

Or you could just laugh at us, and be an asshat.

Is both an option? ;)

When you try five times to fix it and it still doesn't work, its time to throw it in the bin. I have told you this SO MANY times all I can do is laugh now, its just insanity.

Mumble is the perfect solution to this issue and I've seen it work beautifully to integrate with other applications and do channel switching the best example being FAF which is the community lobby for supreme commander.

I've tested this for you so many times, ive talked with almost every vet in the playerbase because of the leaking issue and we all can't fathom why you don't make the decision to get rid of teamspeak, its obviously junk. I empathise that youve worked hard on this, but I can't be supportive when you don't work smart.

We do not use the voice chat because it leaks and we have all become dissillusioned with using it and the VO voice chat is now so badly reputed amongst guild leaders that even if you say its fixed they will still only use external voice chat programs at this point. It will take a significant change to the underlying protocol to actually get us to believe that it will never leak again.

So understand that I would much rather be a complete and utter asshat but tell you the honest truth about it than let you labour under delusions.

We will test your patch to voice chat, but if it leaks again honestly, give up on teamspeak - its a piece of crap.

(Facepalm)

I already responded to the idea of using mumble some time ago. Please read that entire thread.

The problem has never, ever been teamspeak. The problem is a bunch of convoluted spaghetti code that one of our people wrote, was told to "fix" at various times, never documented, and then they left the company. Ray could probably re-write it from scratch in about a week two, but that's a long (and expensive) time in our world.

A connection between our server mechanics, and the voice chat system, would be necessary no matter what system we used. The particular codec wrapper (ts, mumble, whatever) is irrelevant.

So, I have Ray try and debug it when he gets a chance. Ray is great at debugging, but this is unfamiliar and convoluted stuff. Considering the major server outages and other challenges we've had to deal with in the past year, I think my placing a low priority on voice chat is understandable.

If people find they "don't trust me", that's fine. You're all welcome to use whatever external solution you want.

Anyway, Ray says there's still an issue, albeit one that causes voice chat to not work entirely, versus having a leak. There's an ordering problem in people joining/leaving channels that get auto-created and not destroyed properly, which has been the challenge all along, and is pretty.. obscure.

Yes I read the thread, I'm the 5th post. I read it then and I just read it again and all you really said was that it was going to take time to implement and it might have some challenges. How many more patches to teamspeak before you decide to throw in the towel and do it from scratch anyway? Nobody cares if its not mumble, but this is the most repetitive bug you've had.

We trust that you can build a good voice chat system, we don't trust teamspeak.

TRS, could you give it a rest? Some of us appreciate that they're trying to fix things.

Yea everyone's tired of the "TRS knows how to fix everything" threads

I get where he's coming from. Leaking voice chat has been really frustrating. But no reason to get all panty-twisted really. Devs said its on the radar and they are putting serious time into it. That's all we can ask.

And honestly, it doesn't sound like Teamspeak is the problem. Sounds like Inc just said that it was an in-house employee that wrote the connector between Teamspeak and VO, that fucked it up (no offense).

He put Raybondo (the universal dissolvent....wait...oh shit) on it to get it squashed. That's saying something about how important they think this is.

Yeah, I don't know how much clearer I could get than "The problem has never, ever been teamspeak." I'm not like "defending teamspeak", or advocating one way or the other, I'm just saying it's totally unrelated. TRS has a serious reading-comprehension issue going on here.

Anyway, yes, please post issues with Voice Chat to bugs. Or a ticket, if you really want, but Bugs is probably better.

If you can reproduce exactly what order of events causes a problem, that would be extremely helpful.

We do know of one outstanding problem (Ray found this morning) that causes voice chat to stop working. We are not aware of any cases that cause leakage to occur. If you do post a bug, please post a complete record of what you recently did.. like joining a group while chatting with your guild, etc. The problems we've seen have been related to management of multiple channels, and the creation / destruction of voice-chat channels by the game-server glue (again, not the teamspeak server). So, people moving in and out of group chat, while also in guild chat, that kind of thing.