ah yes, we are busy updating/merge for the next release. More info will follow. But basically, it's just an import/naming issue.
as about the pref drop, that's a huge diff, dunno what can possibly cause it. Fabrice On Apr 14, 2010, at 1:49 AM, dapdap wrote: > Hi again, > > Just an update and a question. > > I couldn't get the program working with trunk\fp10 ...(no > AnimationSequence) > But did get it working with tags\3.4.2 > > In doing so, however, I've found that my maximum fps has dropped down > from 48 (with branches 3.0.0) to 30. > > Anyone know why this would be? > It's exactly the same code ... > > Cheers > > D > > > On Apr 14, 10:50 am, dapdap <[email protected]> wrote: >> Thanks as always for your help Fabrice. >> >> Unfortunately it is indeed an animated md2 I want to facelink. >> >> When I switched to the trunk I got a whole raft of errors that I >> didn't really want to look at last night. >> But today is another day and scanning the error list I can see they >> are based around two issues - AnimationSequence and >> DirectionalLight3D. >> >> I'll look into these and see if I can work out what I'm doing wrong. >> I'll get back to the forum if I get stuck :) >> >> D >> >> On Apr 14, 2:28 am, Fabrice3D <[email protected]> wrote: >> >>> 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.
