Hey Daevid the problem caused by somewhat over-zelous garbage collection optimisations, but essentially it is this:
the screen method is used for resolving a vertex into screen-space using the > camera transform of the given 3d object like this: > > screenVertex = camera.screen(object3d, vertex); > > when no vertex is given, a dummy vertex is used. however, the instance of > the screenvertex is reused so as not to create a bunch of uneccesary > screenvertex objects > so to fix your problem, just stick a dummy new Vertex() object in there. although this sort of defeats the GC saving theory ;) needless to say, this problem is fixed much more elegantly in the latest sources... cheers! Rob On Fri, Jan 30, 2009 at 4:29 PM, Daevid <[email protected]> wrote: > > Thanks for checking that it should work! > > It seems that my problem comes from me trying to change the position > with obj3D.position.add(x, y), which obviously doesn't actually update > the position correctly. But it's still strange that the function > returns the other object's value, isn't it? > > /David > -- Rob Bateman Flash Development & Consultancy [email protected] www.infiniteturtles.co.uk www.away3d.com
