Quote Originally Posted by Nommers View Post
I don't know why I feel compelled to defend them after a month of near-total radio silence, but I'm seeing this sentiment a lot and they did walk it back a bit.

I'm giving them the benefit of the doubt and assuming that they blamed old hardware because using an old CPU was the most reliable way they could trigger the bug in their test environment. Still not the best look to go with that excuse right after the bulk of the 2002 problem turned out to be on their end as well, but considering the majority of bug reports seem to have been sent in AFTER that post, they may genuinely not have known any better.

No matter how they go about it, though, intermittent posts by one community manager in one forum thread are not enough to make this right.

Like ClaraKitty said, I'd like to believe that they're staying quiet until they have a guaranteed fix ready to go - after all, the last time they said they fixed it they just made it worse. But at this point, outside of this thread and Soken's twitter, we've received no official assurances that this bug is being looked into at all, and I for one would feel a heck of a lot better if they said anything at all on Lodestone. I know the EN Community Team is away but even their twitter post said they had people still on board watching for problems. This seems like a problem to me. EDIT: I avoid social media like the plague myself, but is anyone making noise about this?

Quote Originally Posted by miragedive View Post
As someone who’s been dealing with this issue for nearly a month, I feel strange coming here to defend Square but here we are. To everyone saying that we’ve had no feedback, you’re wrong. Mr. Soken has made it very clear on his Twitter that the sound team wants to investigate the issue but cannot do so without proper bug reports and system information in the relevant forum. Those who did post on the bug reports forum can see that the first post reporting the issue has been moved to Accepted Bugs and is currently being investigated before it gets confirmed and we (hopefully) get an official timeline for the fix. It’s a holiday season, and the team deserve a break after the gruelling process of releasing 6.0 and 6.01, plus preparing 6.05. No one is ignoring the issue, or belittling it just because it’s not widespread. It’s just the first time they’ve come across something like this so naturally the process will take some time.
I get what you guys are saying and I'd say I'm a very patient person. I don't want any problems with SE or anyone involved.
I don't want to feel this resentment bubbling up when I even boot the game up to check for new/updates/anything.
All I'm asking for currently (besides a fix) is an official response. Not a Twitter post. Not some Forum acknowledgement about it being investigated.
The very first time we "made it" onto the 'Known Issues' List was on the 7th. That was already very late IMO to give us an official response when it started on the 3rd. And since 6.01 the "public" only knows that it's been 'fixed'.
No one in my personal circle has the sound issues. No one in my FC has the sound issues. They have no clue anyone is having major Problems with the Release STILL. (Besides me venting once, but they're to busy chatting about the raids anyway..)

We all agree that usually SE is VERY good with customer service and direct connection to the community, it pains me to feel so left alone.

If they really are investigating it gives us something to feel seen. None of this 'search the forums, search the Twitter', because even when I went directly to Soken's Twitter and looked through his posts/responses/likes I could not see a recent acknowledgement. (I'm not saying there isn't one. I'm just saying its not easily found.)

This game is for many people, and I'm sure there are a good handful that aren't as involved in PC's and the Internet as we believe we all are. Old and Young play this game. There is a Recent Info Panel on the Launcher for a reason.