ThinkIntegral wrote...
Pheonix52gx wrote...
Ragke wrote...
That post by Chris is so subtly haughty. I have a feeling he is a machine; he has no people-skills. "Hey look dumb-people. Patches are hard. It takes a million steps to make a patch. I will bullet-point them for you since you're so stupid kthx." That's how I felt when I was reading that post.
I don't think he was going for that impression but I understand where you're coming from. It does provide a reason as to why these things are taking so long for those unaware.
Unfortunately, when you've worked QA for a first party console developer, that information doesn't provide any answers. But on the other hand, much more information (such as an ETA) would mean they'd have to be accountable for that information (such as sticking to that ETA) and that could backfire on them. I don't like Bioware's "we'll let you know when it's ready" approach, but I can understand their reasoning. Also it was nice to know they're still active and not just ignoring the forums altogether.
I'm gonna have to disagree with your last statement. Giving an ETA wouldn't backfire on them if they premised it with a simple, "well we make no guarantees but we can reasonbly see it being done in X amount of time." It's the same argument an employee would give his employer. Plus, they know their teams, the speed at which they work, the nature of difficulty in the type of bugs they face currently/have in the past.
I mean really the whole point is to just give some kind of frame of reference in terms of time so that the person expecting completion has some sense of assurance rather than no assurance.
Maybe I didn't phrase myself correctly. I totally agree with you. Assuming they made an accurate ETA, based on the circumstances you describe and with the premise you point out, you and I would most likely deal with it if that ETA wasn't met. But I'll bet you, like me, know that not everyone perceives an ETA as flexible and that there will always be a group raging about how it was missed. That's what I think Bioware try to avoid by shipping things as they are rather than throwing ideas and maybes out for feedback as some other developers do.
As I said, I don't like it; I want more information myself. Thank you for calling me out on this though.
Alchera7 wrote...
ThinkIntegral wrote...
Alchera7 wrote...
I'll make another post soon including before and after pictures, as soon as I can figure out how to take screenshots while in-game.
Print Screen button?
I've tried that but when I look in the screenshots folder nothing is there. And when I paste into Paint, all I get is a black screen.
You need to set the screen to "Windowed (No Border)" in graphics options in order to use the Print Screen key for screenshots. At least, I had to. It is possible to bind it without doing this, but I am unware as to how without changing the Coelesced file.
Modifié par Pheonix52gx, 15 mars 2012 - 08:03 .