Apologies for the slow reply. This one slipped through the cracks.
There are a number of issues with these generators, which obviously need some time investment to bring up to date:
They are using an older, xsl-based form of the attribute-based ORM mapping. The relational generators use an in-memory form that is several generations beyond this now.
They aren't normalizing names. Spaces in value type names cause lots of problems, including the trailing space in the Talent.EyeColor object type name.
Duplicate uses of a value type in one table aren't handled
Some data types are not mapped
I think most of the data type errors are coming from schema validation at the plix level because the names are bogus. The transforms here generate a PLiX xml file and set the NUPlixLoader custom tool property, which then generates the correct code for the project type (VB or C#). This generator does schema validation, so one error in the plix file will stymie the whole process. You can see the errors in context by opening the .plix.xml file and using the standard Error List tool window to see the schema validation errors.
Having said that, the PLiX generation transforms are much more forgiving than the schema validation, and PLiX installs a helper window called the PLiX Snippet Preview Window under the View/Other Windows menu. If you open this preview window and the .plix.xml file, and select the plx:root node in the document, then you'll see the majority of the code. It won't compile, but you can copy it and and fill in the blanks. The preview window also lets you choose output language, which is determine by the project type for the custom tool based generator.
In VS2008 and VS2010 you also have the 'LinqToSql Attribute Mapping', which is an alternate (and much newer) plix-based code generator. I saw significantly fewer PLiX errors here (dataTypeName="Byte[" should be dataTypeName=".i1" dataTypeIsSimpleArray="true"). You might try running this generator instead of one against your model in VS2010.
Sorry these aren't in better shape. They were student projects from several years ago and I haven't had the bandwidth to keep them up to date.