Victor Wachter wrote...
Setting previous dates (holiday season, Jan. 5, etc.) was a mistake, since we didn't hit any of them. We were optimistic enough to set those dates, but things did not go as planned. Now, we are dropping back a bit and trying to realign expectations so we don't get a community all up in anticipation again.
See, the problem is that this is a bit of backwards thinking.
The problem isn't that you set release dates, the problem is that you didn't meet the release dates that you set.
This doesn't make stating release dates "bad", expecially in the light of the bioware points system.
I'm sure you can understand that encouraging the customer to support your company by purchasing a product beforehand, but giving no information on when they will receive that product isn't exactly the best way of doing business I can think of.
So, simply enough, set dates that you can meet, and if you don't meet them, just be communicative and tell people how the roadmap changed and what is the next set date. Crap happens, but as long as there's communication, you did what you could.
On the other hand, while not giving any release date at all may seem the easy way out, it's actually a worse solution customer-satisfaction-wise, and doesn't encourage trust in buying the bioware points..
But it's not fair to say that the note contained no information. First, you know that new code is in testing. We're not just looking into the issue or working on the fix. We've begun the testing process, which is the first phase of getting it released.
Second, we wanted to make it clear that there were lessons learned from the release. We're adjusting testing methodologies to better find these types of issues in future updates. This will be a benefit for all of our releases in the future.
yeah, well, I understand what you mean, but the fact that you're working on it, and that you learned from the past mistakes, seem a tad obvious. I doubt anyone doubted that.
While you might have felt the need to state it clearly, it doesn't tell us much that we didn't know. What it doesn't tell us, is when we'll get our money's worth.
Which is the whole problem.
Finally, we really are trying to improve communication and information flow around here. Notes like these are an indication of that. I have some meetings this week, where we'll work further toward getting updates on the questions floating about the forum, so we can help you feel better informed.
I'm glad to hear that. Still, i cannot stress enough on how much i feel that taking the easy way out and washing your hands of release dates is the wrong solution.
Also, I'd encourage you, if you want to make us feel better informed, to finally let us know if we can really expect bioware to keep their promise on the fact that consoles won't influence the PC version of the game, because at the moment I, and many others, are feeling that this problem isn't being kept.
Is there any kind of agreement that forces you to release both the PC and the xbox 360 version at the same time? if not, can we expect to see the PC version released ASAP, whatever the status of the xbox 360 version is?
I'm not holding my breath for you to respond on this, to be honest, but one never know, might we witness a bit of honesty for once in the gaming market

I hope you understand that many PC users that decided to support you (yes, even with criticism) by NOT downloading that pirated version that shouldn't be named, at the moment are feeling "rewarded" with more waiting and no real idea on where we'll get to enjoy what the ones that took the shortcut are already enjoying. Many of us already paid for the content, and feel entitled to a bit more information on the "when", not just on the "if" (which I hope it's obvious). Also, we're starting to feel like the redhead stepchildren compared to console users, given that the 360 fix seemed to get priority over the PC release.