its gonna be ok, till you want to follow an animated mesh like md2 The normalDirty forces Away to calculate the normal of a face that has been updated. for perf reasons this is not done automatically on animated meshes.
why don't you target the trunk instead of 3.0.0 branche? numerous fixes were made. and you eventually need to catch up very soon ;) Fabrice On Apr 13, 2010, at 4:03 PM, dapdap wrote: > Hi guys, > > > I've been working away at a project using \branches\3.0.0\src as my > classpath. > I just went to use FaceLink but then soon discovered that it's not > included in 3.0.0. > > I spent a bit of time changing my classpath to various other libraries > but encountered one or two other issues (not least of which is that my > project runs about 10 fps faster in 3.0.0 compared to any of the > others) > > Anyway, I grabbed a copy of FaceLink from another directory and pasted > it in my source directory and tried to run my app. > > So far it's only come up with one error > C:\FDFull\movieclip\src\FaceLink.as(57): col: 11 Error: Access of > possibly undefined property normalDirty through a reference with > static type away3d.core.base:Face. > > So I commented out the 'offending' line > _face.normalDirty = true; > > And now it seems to be running okay. > > I've no idea what a normalDirty is ... > > I guess my question is - is what I'm doing a good/bad idea? > Am I likely to get myself in a mess or should FaceLink work okay now > that I've omitted that line? > > Cheers > > D > > > -- > To unsubscribe, reply using "remove me" as the subject.
