Aller au contenu

Photo

Issue importing faces into Mass Effect 3 Updated March 21


8899 réponses à ce sujet

#6901
vI Demon Iv

vI Demon Iv
  • Members
  • 66 messages

sixthnewkid wrote...

cApAc aMaRu wrote...

The solution: don't ship garbage in the first place.


Now this is a great post.  And your being civil.  You paid 60 or 80 bucks for a game and when it doesn't work then there at least should be an apology and some explanations.  We got nothing but two small lousy posts.  Unacceptable.  I just hope that if this thing is ever fixed I have some interest in even playing the game.  Lesson learned, I will never buy a bioware product again on week 1.  Will have to wait to see how broken their product is before i hand them my cash.


The lesson we all need to learn is: Never buy another BioWare product again... at least while EA owns their souls. If they leave EA, then give them another chance, but until then, do not give them a dime.

#6902
Dragon_Nexus

Dragon_Nexus
  • Members
  • 43 messages
The bugs in DA2 hurt a lot as well, I recall.
Wondering why my Rogue seemed a little sluggish suddenly when I later found out one of my preferred characters - Isabella - was essentially poisoning my rogue with her talents. It got to the point where I was attacking so slowly it wasn't worth continuing. I restarted and made sure to keep her the hell away from my party at all times. I'd finished the game before the patch came out.

From that point I was just disillusioned with Bioware. I had a lot of hype for ME2, but I had pretty much none for ME3. The face import bug on day one just killed whatever I had left, and waiting this long for a fix has gradually sapped any desire to play the game. I just hope actually playing it will be a good enough experience to rekindle my love of the series as I go along.

Edit:

vI Demon Iv wrote...

sixthnewkid wrote...

cApAc aMaRu wrote...

The solution: don't ship garbage in the first place.


Now
this is a great post.  And your being civil.  You paid 60 or 80 bucks
for a game and when it doesn't work then there at least should be an
apology and some explanations.  We got nothing but two small lousy
posts.  Unacceptable.  I just hope that if this thing is ever fixed
I have some interest in even playing the game.  Lesson learned, I will
never buy a bioware product again on week 1.  Will have to wait to see
how broken their product is before i hand them my cash.


The
lesson we all need to learn is: Never buy another BioWare product
again... at least while EA owns their souls. If they leave EA, then give
them another chance, but until then, do not give them a dime.


They can't leave EA. Bioware can't, anyway. EA owns the company, the brand and any IPs associated with them. The only thing they could do is gather all the staff and quit to form a new company, and in these days of economic turbulance that would be career suicide.

So yeah, regrettable though it is, it's not going to change.

Modifié par Dragon_Nexus, 02 avril 2012 - 11:37 .


#6903
SpiritWolf448

SpiritWolf448
  • Members
  • 99 messages
Well, their silence in regards to how exactly they are going to adress the problem is a bit unsettling, to be honest. If the problem has been fixed and the patch is supposed to be in the certification stage now, would it really kill them to make a post on how exactly they tackled the problem?

Them choosing not to say anything about how the fix will work makes me fear they took the cheapest/fastest way out... :-(

#6904
woodbyte

woodbyte
  • Members
  • 266 messages

SpiritWolf448 wrote...

Well, their silence in regards to how exactly they are going to adress the problem is a bit unsettling, to be honest. If the problem has been fixed and the patch is supposed to be in the certification stage now, would it really kill them to make a post on how exactly they tackled the problem?

Them choosing not to say anything about how the fix will work makes me fear they took the cheapest/fastest way out... :-(


I share your fears. Not looking good at all.
At this point I'm actually wishing their PR department is just inept. It gives me hope.

Modifié par woodbyte, 03 avril 2012 - 12:01 .


#6905
JBauer24Tactics

JBauer24Tactics
  • Members
  • 119 messages
One month...too much..too much.

#6906
Zmidponk

Zmidponk
  • Members
  • 68 messages

TempShark wrote...

Chris did say they fixed the issue, not just suppress the error message.  If all they did was suppress the error message , then I doubt Chris would put in writing that the error has been fixed.  I'm just saying from his message, he's saying that those of us facing this issue (pun intended) will be able to successfully import our faces from ME1 into ME3.  If they accomplished that, I really don't see a further issue.  That's how this whole thing started, We could not import our face from ME1 to ME3, and Chris is saying that has been fixed. And from what I've been reading, the face was the only import issue, all your story choices make it through just fine.  

Problem:  Face could not import porperly
Resolution According to Bioware:  Faces can now import properly pending the next patch.


The problem is the only issue that has actually been unequivocally acknowledged by Bioware as being an issue is the face refusing to import at all, and an error message popping up saying this.  This means that when Chris Priestly says that the issue is fixed, that could be all he's referring to.  The other part of the face import problem is the faces looking different when they do import, and it being impossible for some to recreate their Shepard's face, and all requests to clarify whether or not this latter part is also part of what's been fixed seem to be falling on completely deaf ears.

Modifié par Zmidponk, 03 avril 2012 - 12:23 .


#6907
Turtlemoht

Turtlemoht
  • Members
  • 5 messages
I've given up on ME3 and picked up a copy of Portal 2 yesterday.

Its a complete game that's highly polished, the DLC is a a wonderful bonus (and it's completely free).

This all creates an awesome user experience. Bioware has so much to learn, and they may not have enough fans left to learn from.

#6908
batman22

batman22
  • Members
  • 157 messages
Can u belive it, the game came out on MARCH 6 2012 and its now APRIL 2 2012 and still no fix, all i have to say is.... WTF.

#6909
JBauer24Tactics

JBauer24Tactics
  • Members
  • 119 messages
Update Chris?

#6910
vI Demon Iv

vI Demon Iv
  • Members
  • 66 messages

Dragon_Nexus wrote...

The bugs in DA2 hurt a lot as well, I recall.
Wondering why my Rogue seemed a little sluggish suddenly when I later found out one of my preferred characters - Isabella - was essentially poisoning my rogue with her talents. It got to the point where I was attacking so slowly it wasn't worth continuing. I restarted and made sure to keep her the hell away from my party at all times. I'd finished the game before the patch came out.

From that point I was just disillusioned with Bioware. I had a lot of hype for ME2, but I had pretty much none for ME3. The face import bug on day one just killed whatever I had left, and waiting this long for a fix has gradually sapped any desire to play the game. I just hope actually playing it will be a good enough experience to rekindle my love of the series as I go along.

Edit:

vI Demon Iv wrote...

sixthnewkid wrote...

cApAc aMaRu wrote...

The solution: don't ship garbage in the first place.


Now
this is a great post.  And your being civil.  You paid 60 or 80 bucks
for a game and when it doesn't work then there at least should be an
apology and some explanations.  We got nothing but two small lousy
posts.  Unacceptable.  I just hope that if this thing is ever fixed
I have some interest in even playing the game.  Lesson learned, I will
never buy a bioware product again on week 1.  Will have to wait to see
how broken their product is before i hand them my cash.


The
lesson we all need to learn is: Never buy another BioWare product
again... at least while EA owns their souls. If they leave EA, then give
them another chance, but until then, do not give them a dime.


They can't leave EA. Bioware can't, anyway. EA owns the company, the brand and any IPs associated with them. The only thing they could do is gather all the staff and quit to form a new company, and in these days of economic turbulance that would be career suicide.

So yeah, regrettable though it is, it's not going to change.


That's funny... Bungie left MS and kept their name and empolyees. They did not get to keep Halo though, so I can see your point. BioWare can leave, but they have to leave ME behind.

#6911
Silicon Drifter 82

Silicon Drifter 82
  • Members
  • 108 messages
can i get a hot tub?!!

#6912
Esquin

Esquin
  • Members
  • 709 messages

TullyAckland wrote...

Just want to echo what Lion has been saying, we have no update right now but we're absolutely working on this as priority. As has been stated before we've fixed the issue and as soon as it's passed QA tests by our own BioWare team, Microsoft and Sony it will be released to you. This is called "certification time" and isn't 100% under our control on how fast it can be deployed.

Now, if I were you I wouldn't care for the reasoning behind the delay, I would just want to know that people are working on it and that it is coming. It is. When? Unknown at this time. Not the best answer, believe me I know.

I'm sure Chris will blast out the announcement as soon as we know more.

Once again we understand what a pain this is, and are doing our upmost on getting the patch to you as soon as possible.


How did this problem even happen in the first place?

Did your bug testers fail to test on of the key and fundamental parts of the Mass Effect experience? I mean really how do you fail to fully test the character import function?

#6913
Liaras

Liaras
  • Members
  • 20 messages
Posted Image

#6914
Bunzmaster

Bunzmaster
  • Members
  • 87 messages
Still not fixed yet?

lame

#6915
woodbyte

woodbyte
  • Members
  • 266 messages

Liaras wrote...

Posted Image


http://cloud.steampo...655D7D8F712D06/

#6916
AGoodGeek

AGoodGeek
  • Members
  • 47 messages

Zmidponk wrote...

TempShark wrote...

Chris did say they fixed the issue, not just suppress the error message.  If all they did was suppress the error message , then I doubt Chris would put in writing that the error has been fixed.  I'm just saying from his message, he's saying that those of us facing this issue (pun intended) will be able to successfully import our faces from ME1 into ME3.  If they accomplished that, I really don't see a further issue.  That's how this whole thing started, We could not import our face from ME1 to ME3, and Chris is saying that has been fixed. And from what I've been reading, the face was the only import issue, all your story choices make it through just fine.  

Problem:  Face could not import porperly
Resolution According to Bioware:  Faces can now import properly pending the next patch.


The problem is the only issue that has actually been unequivocally acknowledged by Bioware as being an issue is the face refusing to import at all, and an error message popping up saying this.  This means that when Chris Priestly says that the issue is fixed, that could be all he's referring to.  The other part of the face import problem is the faces looking different when they do import, and it being impossible for some to recreate their Shepard's face, and all requests to clarify whether or not this latter part is also part of what's been fixed seem to be falling on completely deaf ears.



This is a follow up to my other post btw:

The entire issue which includes the following: faces from ME1 OR ME2 not importing at all OR properly, was summarized by Chris' statement that the issue of faces not importing properly has been fixed.  I really believe Chris means that ALL face import issues, whether or not it's a face that can't be imported or a face that imported incorrectly has been fixed.  He made a general statement addressing a general issue.  You wouldn't have to recreate your face if the import issue is fixed.  Whether or not they added facial assets, or any other kind of coding etc, the issue according to Bioware has been fixed and will be included in the next patch.

I find it really hard to believe that Chris would make an announcement in writing unless he had all his bases covered.  A company like Bioware, any company as a matter of fact, needs to be extremely careful with what they say and how they say it.  Chris' statement in my opinion and understanding, addresses all face import issues.  If it doesn't, and after the patch there still resides some sort of face import issue, Chris will have a lot more problems on his hands.  

It's why he's not saying anything concrete because Community members like those of you on this thread are frustarted to the point where we're actively disecting a Bioware employee's statements down to the last letter when it's meaning is most likely just face value (another pun intended.)  It's why the other two Bioware reps did not say anything concrete at all.  And honestly, I can't blame them for doing that.

Many of you are asking for answers and explanations as to why this happened.  I doubt that they'll give a direct answer before the patch arrives.  My theory is that they'll wait until after the patch is delivered to everyone, then let someone higher up the corporate chain address the issue.

Simply put, those moderators and even Chris are probably not even authorized to directly answer the questions we are asking.  All they can say is what has already been said. Trust me I understand in FULL that the lack of answers to our questions can be infuriating.  I'm right there with each one of you asking "How did this slip testing?"  Stop and think about it for a second.  If you were in their shoes, wouldn't you want to answer a question like that with caution?  With preparation?  With the support of Bioware and EA upper management? I'd be scared  to answer one of the Bioware Community Members when they ask me a question like that. 

Look everyone, we're here voicing our frustrations.  To everyone who owns the game and has been affected by this issue, you have the right to voice your complaint.  I stand with you, and so do many others on this forum.  Let's just be civil, reasonable, and realistic when we contribute. 

I've decided for myself that I'm going to wait for this patch and maybe even start another thread when it does get released asking the simple question of "How did this happen?"  If enough of us ask this question in a civil manner, I sincerely believe that we'll get a civil answer in response.  For now, let them do what they have to do on their part so we can get back to doing ours....playing a videogame.

Modifié par TempShark, 03 avril 2012 - 01:58 .


#6917
Clarian

Clarian
  • Members
  • 376 messages

TempShark wrote...
The entire issue which includes the following: faces from ME1 OR ME2 not importing at all OR properly, was summarized by Chris' statement that the issue of faces not importing properly has been fixed.  I really believe Chris means that ALL face import issues, whether or not it's a face that can't be imported or a face that imported incorrectly has been fixed.


I don't.  Look at what he said:

Chris Priestly wrote...
We have determined that faces importing incorrectly is an error with how codes were detected when transferred from Mass Effect 1 into Mass Effect 2 and then on into Mass Effect 3 or importing a Mass Effect 2 saved game with New Game +.


That excludes ME2 non-NG+ faces. 

#6918
AGoodGeek

AGoodGeek
  • Members
  • 47 messages
Clarian

I think the following statement from Chris encompasses all face import issues including yours:

"We have fixed the issue of faces not correctly importing into Mass Effect 3."

It goes back to why I said Chris needs to be careful in what he says. To me, that statement speaks to all face import issues.

I do hope your fix is included in this patch.

#6919
Clarian

Clarian
  • Members
  • 376 messages

TempShark wrote...
I think the following statement from Chris encompasses all face import issues including yours:

"We have fixed the issue of faces not correctly importing into Mass Effect 3."


I don't.  When the says "the issue," he means the issue he stated earlier.  Which excludes ME2 non-NG+.

#6920
AGoodGeek

AGoodGeek
  • Members
  • 47 messages
Hopefully they'll address this in some way, shape, or form at the PAX convention this Friday. Keep your fingers crossed.

I'd be very upset along with you if this patch didn't fix every face import issue. This entire ordeal has been a tremendous disservice to all the fans affected.

#6921
Zmidponk

Zmidponk
  • Members
  • 68 messages

TempShark wrote...

This is a follow up to my other post btw:

The entire issue which includes the following: faces from ME1 OR ME2 not importing at all OR properly, was summarized by Chris' statement that the issue of faces not importing properly has been fixed.  I really believe Chris means that ALL face import issues, whether or not it's a face that can't be imported or a face that imported incorrectly has been fixed.


The problem is that your belief that this is the case does not make it so.  It is not clear whether he does mean all face import issues or not, which is precisely why people are asking for him, or someone else from Bioware, to clarify this point.  So far, however, these questions have been met with deafening silence.

#6922
JBauer24Tactics

JBauer24Tactics
  • Members
  • 119 messages
I want my facial.

#6923
ThinkIntegral

ThinkIntegral
  • Members
  • 471 messages

TempShark wrote...
Whether or not they added facial assets, or any other kind of coding etc, the issue according to Bioware has been fixed and will be included in the next patch.


That's the heart of this problem really.  I have no doubt Chris meant they addressed the importing issue.  What they don't seem to be understanding, assuming they're even really listening, is that we want very little changes in the aesthetics of the ME3 face, similar to how it was treated between ME1 and ME2.   Nothing in Chris' post or posts from Tully or Lion address this at all. 

Plus they very damn well knew about it a month before the game officially launched when people using the demo where pretty much saying the same thing.


TempShark wrote...
Stop and think about it for a second.  If you were in their shoes, wouldn't you want to answer a question like that with caution?  With preparation?  With the support of Bioware and EA upper management? I'd be scared  to answer one of the Bioware Community Members when they ask me a question like that. 


Not me. I'd freaking man up and talk straight with the community members.  Depending on what it was I'd obviously add disclaimers to my statements, maybe even stating that what I'm saying is purely opinion, but at least I wouldn't just shut the hell up for days on end, and I'd attempt to try to get some info.  If I couldn't disclose I'd at least tell members that.

Modifié par ThinkIntegral, 03 avril 2012 - 02:59 .


#6924
Dragon_Nexus

Dragon_Nexus
  • Members
  • 43 messages

vI Demon Iv wrote...

Dragon_Nexus wrote...

The bugs in DA2 hurt a lot as well, I recall.
Wondering why my Rogue seemed a little sluggish suddenly when I later found out one of my preferred characters - Isabella - was essentially poisoning my rogue with her talents. It got to the point where I was attacking so slowly it wasn't worth continuing. I restarted and made sure to keep her the hell away from my party at all times. I'd finished the game before the patch came out.

From that point I was just disillusioned with Bioware. I had a lot of hype for ME2, but I had pretty much none for ME3. The face import bug on day one just killed whatever I had left, and waiting this long for a fix has gradually sapped any desire to play the game. I just hope actually playing it will be a good enough experience to rekindle my love of the series as I go along.

Edit:

vI Demon Iv wrote...

sixthnewkid wrote...

cApAc aMaRu wrote...

The solution: don't ship garbage in the first place.


Now
this is a great post.  And your being civil.  You paid 60 or 80 bucks
for a game and when it doesn't work then there at least should be an
apology and some explanations.  We got nothing but two small lousy
posts.  Unacceptable.  I just hope that if this thing is ever fixed
I have some interest in even playing the game.  Lesson learned, I will
never buy a bioware product again on week 1.  Will have to wait to see
how broken their product is before i hand them my cash.


The
lesson we all need to learn is: Never buy another BioWare product
again... at least while EA owns their souls. If they leave EA, then give
them another chance, but until then, do not give them a dime.


They can't leave EA. Bioware can't, anyway. EA owns the company, the brand and any IPs associated with them. The only thing they could do is gather all the staff and quit to form a new company, and in these days of economic turbulance that would be career suicide.

So yeah, regrettable though it is, it's not going to change.


That's funny... Bungie left MS and kept their name and empolyees. They did not get to keep Halo though, so I can see your point. BioWare can leave, but they have to leave ME behind.


Difference being, Microsoft didn't own Bungie. They financed them and gave them a lot of support, but they never actually owned them. Bungie the company decided to go and be seperate from MS for a time, if not perminantly. However a lot of the staff stayed behind to for 343 Studios. Not sure if Ms owns them.

This is a different situation. EA bought the holding company that owned Bioware and Pandemic Studios, the latter of which was shut down when it failed to perform (probably in the plan all along. Like buying a box of assorted goods at a car boot sale, you chuck out the junk but you keep the silver cutlery).
So no, Bioware can't leave, EA owns the Bioware brand now.

#6925
AGoodGeek

AGoodGeek
  • Members
  • 47 messages

ThinkIntegral wrote...

TempShark wrote...
Whether or not they added facial assets, or any other kind of coding etc, the issue according to Bioware has been fixed and will be included in the next patch.


That's the heart of this problem really.  I have no doubt Chris meant they addressed the importing issue.  What they don't seem to be understanding, assuming they're even really listening, is that we want very little changes in the aesthetics of the ME3 face, similar to how it was treated between ME1 and ME2.   Nothing in Chris' post or posts from Tully or Lion address this at all. 

Plus they very damn well knew about it a month before the game officially launched when people using the demo where pretty much saying the same thing.


TempShark wrote...
Stop and think about it for a second.  If you were in their shoes, wouldn't you want to answer a question like that with caution?  With preparation?  With the support of Bioware and EA upper management? I'd be scared  to answer one of the Bioware Community Members when they ask me a question like that. 


Not me. I'd freaking man up and talk straight with the community members.  Depending on what it was I'd obviously add disclaimers to my statements, maybe even stating that what I'm saying is purely opinion, but at least I wouldn't just shut the hell up for days on end, and I'd attempt to try to get some info.  If I couldn't disclose I'd at least tell members that.



That's the problem, they CAN'T talk straight with us even if they wanted to.  Well if they did I'm sure legal repercussions would hit them harder then a charging Brute.

Lion said it himself, even if he knew more he wouln't be able to disclose it.