Voice is broken again.

[SilkenKidden]

<p>Mine got fixed last week but now it is broken again.  Can't see me in channels.  Can't hear anyone in channels.  Others are having the problem that didn't have it last week.  The system is deteriorating.</p>

[Mikkahl]

<p>Well, for many of us, it's "Voice is still broken".  Not much different from last week, with intermittent connectivity, except I have not seen a single client or EQ2VoiceService crash as of yet (knocking on wooden head).</p><p>I had voice this morning, with some issues.  But I had to give up my invite to a VS raid tonight because I could not get voice working. <img src="/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" alt="SMILEY" /></p>

[bigsigh]

<p>..or possibly the thread could be called, 'voice is still broken,' or maybe, 'yet another attempt at fixing voice fails'.</p><p>SOE made a choice, release a faulty product, or delay and wait until it was ready for release. They chose the former.</p><p>Then they made another choice, fix this joke by rolling back, or allow it to continue and screw those who can't use voice. They chose the latter.</p><p>SOE wonder why people won't play on Test. Helloooo, it is because you don't LISTEN to what the people on test are telling you! If they did, we wouldn't be where we are now, which is living in silentville.</p><p>What we NEED to see now is a response from a dev telling us where this is going now. We waited for this 'fix', we have dealt with the nonsensical TSR responses, and now we just want an answer. Telling us that rollling back is hard is NOT an answer, it is an excuse. If SOE wanted to fix this laughable sitution, they could do so and the fact that they have gone this long without doing so tells me that they have no intention of taking the smart option, which would be to roll back to a pre-GU 52 state.</p><p>We know that the devs are reading these threads, yet, they say nothing. They get away with saying nothing because we let them. I am just about fed up with their bumbling incompetence and there is only one thing that they will understand. Maybe when they are all unemployed, because the great game that used to pay their wages is dead, maybe then they will understand.</p><p>It is not affecting JUST those who have no voice, it has a flow on effect to those who have voice but can't interact with those who don't. Even those who have no voice issues are seeing this drama and are just adding yet another straw to the camel's back, and given the standards lately, that back is very close to breaking.</p>

[Thunderthyze]

<p>The problem arose when SOE attempted to integrate the voice client with the Station Launcher which they have marketed as the great saviour of communication. Maybe the time has come to admit Station Launcher still isn't ready or that it was wrong to attempt this integration. Go back to the Vivox files being within EQ2 and not outwith and maybe we can have our communication back.....or maybe we should just go back to Teamspeak?</p>

[bigsigh]

<p><cite>Holymoly@Runnyeye wrote:</cite></p><blockquote><p>The problem arose when SOE attempted to integrate the voice client with the Station Launcher which they have marketed as the great saviour of communication. Maybe the time has come to admit Station Launcher still isn't ready or that it was wrong to attempt this integration. Go back to the Vivox files being within EQ2 and not outwith and maybe we can have our communication back.....or maybe we should just go back to Teamspeak?</p></blockquote><p>Going back to Teamspeak or Vent is not really an option when 90% of the guild have working voice and see no need to do so. This is the divisive nature of the problem. As I said, this is causing issues for people that have no issues and this is what SOE don't seem to realise.</p><p>The time to admit failure is long past, it is now time to actually DO SOMETHING about it.</p>