FoxHound109 wrote...
Link Ashland 614 wrote...
IMPORTANT: If your Shepard doesn't have a face code, it will work importing. If it has a face code that isn't that Shepard's code, you'll have to do it from scratch.
Meaning? Sorry I use the 360 so I know nothing about face codes and whatnot.
Basically, when they made ME2, they changed the way the face was generated slightly so that creating a face also generated a code, allowing you to recreate that face by simply inputting that code. However, this caused a slight problem with characters imported from ME1, as they had no face code. Unlike with ME3, this was spotted and sorted during development by making the game import the raw data of what the face looked like, although this still caused some very minor differences to occur (usually along the lines of some scars disappearing, or being different, which most people weren't too bothered about, probably because it made sense with the whole Project Lazarus thing). This also meant that your ME2 character did not have a face code.
However, there is an unnoticable (at the time) bug where, if you import an ME1 character into ME2, then start making a new customised face, but change your mind, and go back and accept the imported face, the face code for the customised face is attached to the save files for that Shepard, even though, ingame, it's the imported face that shows up. This is now causing problems when it comes time to import your ME2 Shepard into ME3, as ME3 might take the facecode for the wrong face, and try importing that. There is a workaround where you use the Gibbed save editor for ME2 to delete the face code from your ME2 save before importing, but, contrary to what Link Ashland 614 seems to believe, having no face code still does not guarantee the face imports accurately, even after the supposed 'fix'.