8899 réponses à ce sujet

[chainsawgutsfuck]

FlyingWalrus wrote...

Glitch, bug, they're the same thing aren't they? When a program does not respond or act as it is intended to due to unknown or unforeseen variables?

Be reasonable. QA is a very demanding job and the debugging process is often a horrifying laundry list of hilariously obscure and inexplicable things. It is more often than not impossible to clear the list completely—bugs are prioritized. Like I said, I bet this one is just one that happened to go awry at just the wrong place in the process where it was overlooked or missed. Unfortunate indeed that it had to be such a prominent feature.

...except the community could probably sort it out in under a week if BioWare said "Sorry guys we can't be arsed to do our job, cya". And that *is* their job.

Car manufacturers don't release a car with a half-working gearbox and go "Well it's just too long and arduous a process to sort it out now, we'll ship out replacements in the next few months - enjoy driving in the meantime". BioWare don't release the final game of a trilogy with a faulty, half-working character importer to continue and complete the legacy of your customised (face, story, whatever) Shepard.

Except they do.

[mybudgee]

One thing sums it up. The most epic fail in the history of failures. Period.

Modifié par mybudgee, 08 mars 2012 - 09:58 .

[Abe-kun]

Damn. I finally got the CE for xbox 360 today and found this suprise. I could't import my first 2 Shepards but got my newest Infiltrator Shepard to ME3... listening codex and hoping quick fix...

[Kertsang]

FlyingWalrus wrote...

Glitch, bug, they're the same thing aren't they? When a program does not respond or act as it is intended to due to unknown or unforeseen variables?

Be reasonable. QA is a very demanding job and the debugging process is often a horrifying laundry list of hilariously obscure and inexplicable things. It is more often than not impossible to clear the list completely—bugs are prioritized. Like I said, I bet this one is just one that happened to go awry at just the wrong place in the process where it was overlooked or missed. Unfortunate indeed that it had to be such a prominent feature.

Yes, you are absolutely correct on all counts. But what people are angry about is that a developer of this caliber has missed such a HUGE glitch. This is the kind of thing reserved for games like Big Rigs Over the Road Racing, not Mass Effect, and yes I did just mention Big Rigs and Mass Effect in the same sentence.  And very importantly, this is a glitch that is affecting so many people, and the fact that it is such a crucial aspect of the entire franchise makes it all the more painful.

[FlyingWalrus]

Cootie wrote...

FlyingWalrus wrote...
*snips a bunch, hope you don't mind*

Doesn't that prove my point though? The point of interacting with the community in a transparent manner is to avoid tinfoil-hatting. Ignorance is really just a lack of information, and we're suffering from it lots.
Even if it's just "We're working on it, seriously. I don't have any specifics right now, but I promise I'll try to get back to you," it'd prove to be an efficient way to get rid of the constant frothing.

The rest of your post is just the opposite of tinfoil hatting, because we don't know anything.
Why?
Nothing's been said. And nothing's been said regarding the whole "they must've known about this"-issue, either.
It's just leaning towards renegade, and it's easily fixed. That's what's really frustrating.

And if Chris is just a community guy, and I don't assume his job is easy, taking the time to just repeat the same thing over and over has worked well for other companies, like Activision Blizzard, because it looks like they care and are actively looking into it.
I can't be sure he's working hard to find answers, either, because we haven't heard from him.

I'm just saying, communication is good. I don't want to sound like I'm demanding very much, or constant attention or somesuch. But from where I'm standing, it really doesn't sound so bad to just retype the same statement over and over.
Again, I should stress that I don't know, and I'm not an expert.

I don't think that awfulizing is particularly productive, either. While I don't believe that the issue is one that we should let go considering what it is in this case, I don't think that getting "updates" for the sake of updates is a good thing either. If there is an update, let it be one of substance with an actual explanation. This can take time to get.

After all, you're not the only one with a horse in this race. I have a Shepard that I purpose built to NOT change throughout all of Mass Effect, from beginning to end. Learning that his story will be on pause for that much longer is somewhat deflating but I will deal with it in the meantime. I have said my peace to Bioware and now I simply watch and wait. And hope. HOPE, that is, that the disparity in the code isn't so great that it isn't unfixable.

[Drumcorps_Ageout]

Had to recreate my face manually. This is the best I could do.

ME2


ME3


Note: The lighting in ME2 doesn't show that his eyes were actually light blue/purple in color.

Modifié par Drumcorps_Ageout, 08 mars 2012 - 10:04 .

[Kastigar]

FlyingWalrus wrote...

Glitch, bug, they're the same thing aren't they? When a program does not respond or act as it is intended to due to unknown or unforeseen variables?

Be reasonable. QA is a very demanding job and the debugging process is often a horrifying laundry list of hilariously obscure and inexplicable things. It is more often than not impossible to clear the list completely—bugs are prioritized. Like I said, I bet this one is just one that happened to go awry at just the wrong place in the process where it was overlooked or missed. Unfortunate indeed that it had to be such a prominent feature.

So bugs are prioritized, and a core feature of the game....wasn't on the top of that list. A bug with the importer, part of the system that brings your Shepard from one game to the next, a pillar of what this series is built on, isn't functioning properly...and it fell through the cracks. What if Shepard didn't lip synch right, or just stould completely rigid during cut scenes, or had no run animation if he was being hit by enemy fire? The whole damn forum would be up in arms.

You are basically arguing that Bioware, for all their efforts and all they've accomplished, is also either A) grossly incompetent or incredibly stupid. Core features should be at the absolute top of the "get it right and get it working" list.

I'm not trying to be a jerk or anything. But this issue is effecting a fair amount of players, and it is an issue with a core aspect of the game. How can Bioware honestly be defended over this issue?

[GODzilla]

avmf8 wrote...

GODzilla_GSPB wrote...

All in all I spend a good three to four hours to recreate my Shepard. I think the outcome is pretty good, but I also think this should not have been necessary!

For myself I believe that, if I'd ever play Mass Effect from the beginning with another character then it's going to be the standard male Shepard, since I've actually never done this (only MY custom FemShep *g*).

But there are people, some with an almost crazy amount of different custom Sheps. I've read a guys post who claims he has 15. 15!!! ^^ Must be a pain trying to recreate them all. -.-

Bottom line: I'm almost certain, I don't expect this to ever get fixed. But go ahead Bioware, surprise me!

I am not sure but you may be talking about me I do have 15 Sheppards. None of them sucesfully imported into ME3. I did 15 because I wanted to see every consiquence and decission pan out. Varriations like I save Wrex or kill him or tell ash to stay with the bomb or tell kaiden. to stay with the bomb. I made saren kill himself but another time did not every major choice youcan make I did to see them all.

That is why I am very pissed off at this. I think I am the most pissed off person here. 

Certainly. ^^ And I can understand why you played it this way, though it's 100% contradictionary to my own playstile. I usually play only one "personal canon" Shepard, making it my story, chosing like I would if it was really me and then living with the consequences. It's more personal this way.

Taking the game apart like this, decision by decision, like it's a table of content or a chart, feels wrong. But that's just my opinion.

[Cootie]

FlyingWalrus wrote...
*snip(I'm really sorry for constantly removing your text, but quote towers are bad)snip*

I'm not the one making them look bad. They hardly need help in that department, ho ho ho.
Okay, no, I'll stop villainising them, or I'm trivialising the problem.

I don't really see how "updates for updating's sake" is a bad thing, unless it's very excessive, so much that it becomes repetitive. I think most of all we just want confirmation that this is being handled, how and when we might see it. Should we get our hopes up? Should we calm down and just wait patiently?

I can see the advantage of waiting for a while, trying to sense when the conversation stops being all about angry complaints and nasty hyperbole so that the chances of the fans actually absorbing what's being said are relatively high.
But!
A simple "We hear you. Just hang in there and we'll see what we can do" doesn't really open up for a lot of counter-arguments, does it?
If so, I'd love to be enlightened.

Ooooor I might just be super-tired. Yes, that's it.
Forget everything I just said.

[FlyingWalrus]

Kastigar wrote...

FlyingWalrus wrote...

Glitch, bug, they're the same thing aren't they? When a program does not respond or act as it is intended to due to unknown or unforeseen variables?

Be reasonable. QA is a very demanding job and the debugging process is often a horrifying laundry list of hilariously obscure and inexplicable things. It is more often than not impossible to clear the list completely—bugs are prioritized. Like I said, I bet this one is just one that happened to go awry at just the wrong place in the process where it was overlooked or missed. Unfortunate indeed that it had to be such a prominent feature.

So bugs are prioritized, and a core feature of the game....wasn't on the top of that list. A bug with the importer, part of the system that brings your Shepard from one game to the next, a pillar of what this series is built on, isn't functioning properly...and it fell through the cracks. What if Shepard didn't lip synch right, or just stould completely rigid during cut scenes, or had no run animation if he was being hit by enemy fire? The whole damn forum would be up in arms.

You are basically arguing that Bioware, for all their efforts and all they've accomplished, is also either A) grossly incompetent or incredibly stupid. Core features should be at the absolute top of the "get it right and get it working" list.

I'm not trying to be a jerk or anything. But this issue is effecting a fair amount of players, and it is an issue with a core aspect of the game. How can Bioware honestly be defended over this issue?

Actually, it probably was one of their top priorities. The thing is it must have broke AFTER they thought they sorted it. It was probably one of the very first things they tried and tested. One of the chief frustrations in debugging is that sometimes fixing one bug creates several more. The character import is a one-time process that you do at the beginning of a new game and forget about as soon as you begin; it's not something as ubiquitous as animation or gameplay, things which are almost immediately observable. To thest the importing, they would have had to start a whole new game each time, which is well beyond time consuming.

And like I said, I am affected as well. I am defending Bioware no more than I would defend any other well-meaning -- but very human -- human being.

[Ajirasan]

My male Shepard gonna look like a hobo. :/

Modifié par Ajirasan, 08 mars 2012 - 10:22 .

[TheRealJayDee]

Terror_K wrote...

The fact is simply this: this should never have got past QA. Not in a million years. Not with what the Mass Effect trilogy was supposed to be. It's either carelessness, laziness or incompetence (or all three).

This. It's just unbelievable. I also can't fathom why they decide to make it worse by this lack of communication. What they did achieve though is to completely kill any and all anticipation I had for this game, which I'll get in few hours. And that is really something, cause ME3 was my most anticipated game of the last years, by far. Now I'm extremely close to just sending it back instantly, and waiting for a playable budget version.

Damn.

Modifié par TheRealJayDee, 08 mars 2012 - 10:23 .

[avmf8]

FlyingWalrus wrote...

Kastigar wrote...

FlyingWalrus wrote...

Glitch, bug, they're the same thing aren't they? When a program does not respond or act as it is intended to due to unknown or unforeseen variables?

Be reasonable. QA is a very demanding job and the debugging process is often a horrifying laundry list of hilariously obscure and inexplicable things. It is more often than not impossible to clear the list completely—bugs are prioritized. Like I said, I bet this one is just one that happened to go awry at just the wrong place in the process where it was overlooked or missed. Unfortunate indeed that it had to be such a prominent feature.

So bugs are prioritized, and a core feature of the game....wasn't on the top of that list. A bug with the importer, part of the system that brings your Shepard from one game to the next, a pillar of what this series is built on, isn't functioning properly...and it fell through the cracks. What if Shepard didn't lip synch right, or just stould completely rigid during cut scenes, or had no run animation if he was being hit by enemy fire? The whole damn forum would be up in arms.

You are basically arguing that Bioware, for all their efforts and all they've accomplished, is also either A) grossly incompetent or incredibly stupid. Core features should be at the absolute top of the "get it right and get it working" list.

I'm not trying to be a jerk or anything. But this issue is effecting a fair amount of players, and it is an issue with a core aspect of the game. How can Bioware honestly be defended over this issue?

Actually, it probably was one of their top priorities. The thing is it must have broke AFTER they thought they sorted it. It was probably one of the very first things they tried and tested. One of the chief frustrations in debugging is that sometimes fixing one bug creates several more. The character import is a one-time process that you do at the beginning of a new game and forget about as soon as you begin; it's not something as ubiquitous as animation or gameplay, things which are almost immediately observable. To thest the importing, they would have had to start a whole new game each time, which is well beyond time consuming.

And like I said, I am affected as well. I am defending Bioware no more than I would defend any other well-meaning -- but very human -- human being.

This was an easy problem to test and they did not do it. Common I had issues the second I tried to import a character. The as far as I am concerned most important core feature of the game broken fromthe start.

In which case they will most likeley not fix.

[lakdav]

We expect some kind of an update on the problem. This is either a quick-to-fix bug, and they will only say something when its done in a few days, or it will take a long time and they want to give us periodic updates maybe once a week. Assuming of course that 1) they know how much time it might take to fix it and 2) they care to keep us informed. Given that Bioware is an experienced developer, i 'dare' to hope that they know what they are doing both on the programming side and the community management side. They would not have survived this long if the werent. They wont survive long if they no longer do.

Anyway, guess we are just in a bad time right now. The next word is either "We're done with the patch, have fun with it" or "We found the main issue, and trying to find a way around it, gonna take some more time". Either would be welcome.

[Heratos]

I hope this flaw will be fixed soon as I am sadly to say, not touching ME3 untill i can play with my own character. Don't really see the reasoning behind removing/changing the appearence customization this much in the 3rd game of a trilogy. Looking forward to a patch to fix it hopefully as quick as possible. Keep up the work Bioware and give us ME3 back;)

[gavccu]

I think some of the folks on this forum should calm down a wee bit - some of the moans and groans are a wee bit undignified and a bit over the score. Yes it's a glitch but BioChris says it's being worked on by the Dev teams who were probably planning to be on holiday after ensuring and building an epic finale to all of our adventures over the last year or so - lets give them a bit of time people.

Me? Here in the UK i will have to make do watching the trailers (again) until tomorrow; i would chew my right arm off to have ME3 in my Xbox right now and trying to get a close a copy of My ME1 ME2 Shep as possible and spending a bit of time getting it right. I've taken a screengrab in preperation, so it hopefully shouldn't be too difficult to reproduce.

Chin up America/Canada!

[gavccu]

P.S. Jim Shepard - looking good bro! It can be done

[Dougremer]

 Hi,

Nagging a little bit here. But from what I can tell it's only the eyes that needs to be fixed. Been checkin other peoples shepards out and it's the same, the eyes look off. And I see more male shepards turning out better.
So, if something needs to be fixed it's the eyes, the rest looks great IMO.

Yes, that JIM looks great and a few pages back I saw a female that wasn't bad at all. Have a look HERE first and you'll see my charachter in the demo looks pretty spot on (except lightning, hairstyle and lipstick).
Then you look HERE and you'll really see the big difference. It's the eyes that screw things up. And compared I think the ME3 looks more like the ME1 than ME2.

But this won't stop me from playing, if they fix it I'll just play it again

/Dougremer

[bazzag]

Although its a tad annoying, i don't mind much. Went on to the demo last night to see how close i can get my shep to look like him and i was very pleased with the results.

[Katana Gamer]

FlyingWalrus wrote...

Cootie wrote...

FlyingWalrus wrote...

Guys, Bioware is not your ****. You aren't ENTITLED to an update every 24 hours or whatnot. You do not need to know every detail of the process they are going through right now, if there is one at all.

I can understand why people are upset, but the audacity of some of you, sheesh.

I'm sorry?
Did you pay the exact same amount of money as the rest of us? Because if you got your game for free, I'd love to know how. Please enlighten us.

I don't even know what the hell you're trying to say. But yes, I did drop for a CE same as many people on this forum. US$79.99 plus 9.75% tax.

And I'm just going to make a general response since I don't want to bulletpoint a response for everyone.

You're free to go running around screaming your head off about how Bioware knew that this was going to happen, spouting inane conspiracy theories and basically making yourself look like you wear tinfoil hats as a matter of habit nowaday, but that's not going to make either Bioware or your fellow forum-goers take you seriously. The fact is that bugs happen. Anyone who has spent an hour working with code knows that she is a fickle mistress and that it can be straight up gymnastics trying to get a program to behave exactly as you want it.

Were it so easy, do you not think that Bioware would rather avoid the possibility of an enraged and heartbroken fanbase? The fact is that somewhere between three game engines and five years, something is not gonna align. It seems so simple to us standing from the outside and minutely critiquing every design choice, but we weren't the ones laboring under a deadline. Frankly, I can see how it would have been easy to miss if they thought they had it in the early stages. For doing other things, the feature mysteriously breaks or derails or something or the other.

I'm not here to be Bioware's defense attorney. Like I said, I can't be mad at people for being mad. I'm just trying to be a voice of reason and rationality here.

Oh yeah, and isn't Chris just a community guy? That means he actually has to try and get info from other people, which as anyone who has ever worked as part of a company knows isn't always an immediate possibility.

You sir, as a customer have bought a PRODUCT. 
- Example: Imagine having 10 original DVD movies you love and cherish, and you go out and buy a BluRay player ADVERTISING that it can play all original DVDs. So you fire it up and try, out of 10 DVDs 6 do not play at all, 3 play some part of the movie (about 60%, but missing key scenes), and 1 plays 90% but not the ending.
This is what would happen - you would take it back (with some yelling included).
So you feel you are entitled to finished product (do not let me discuss how you should not pay additional 16% so that the player activates it's remote controller), specially as it was sold with it's main feature ADVERTISED.

However here you argue that customers are actually NOT entitled to ADVERITSED functionalities of the product. That in industry where workers usually earn much more than workers assembling a BluRay player.
The proof that this is not a bug, or that EA purposely released a flawed product (not working as advertised) is the popup error message - they found out that some of the combinations of charcter parameters will break the import feature totally - so instead of fixing it, they added a popup. (And yes I am a Project manager in software development company, so I know all about bugs, and acceptance, and QA). 
Bottom line EA (BW is their part so yes EA) advertised a feature in the product and did not deliver it to paying customers...If your TV displayed the picture upside down you would not beg for factory to say when it will fix it - you would demand a correctly functioning product

[AlcyoneNoth]

This is disappointing. I've been so excited to play, and finally picked up my pre-ordered Collector's Edition this afternoon, but now I run into this problem. I've had the game for about 7 hours now and I cannot for the life of me bring myself to start playing. I've tried messing with the character creator to recreate my original Shep, but no matter how hard I try it's never the same. The first playthrough is always the most enjoyable, and I refuse to do it without the Shep that I've come to love over these past years.

[Immer Rastrelly]

I tried the game a bit. It's OK. But...

Now I'm totally joining the I AM NOT PLAYING UNTIL I HAVE MY SHEPARD BACK mob.

Because:

Bottom line EA (BW is their part so yes EA) advertised a feature in the product and did not deliver it to paying customers...If your TV displayed the picture upside down you would not beg for factory to say when it will fix it - you would demand a correctly functioning product

[avmf8]

Immer Rastrelly wrote...

I tried the game a bit. It's OK. But...

Now I'm totally joining the I AM NOT PLAYING UNTIL I HAVE MY SHEPARD BACK mob.

Because:

Bottom line EA (BW is their part so yes EA) advertised a feature in the product and did not deliver it to paying customers...If your TV displayed the picture upside down you would not beg for factory to say when it will fix it - you would demand a correctly functioning product

I hear you I have played to about where you get free roam but the experience seems hollow without any of my sheps.

[archisb]

When can we expect the patch to be released? Cause till the patch is released I'm not going to play my Mass Effect 3 which I have already purchased from Origin store.

[cheezbaalz]

Damn thee Bioware!