Hey Mogg
thanx for the report, but if you look a few lines dwon you'll see gz and gy
are swapped back in the output:
x = gx;
y = gy;
z = gz;
so i'm not sure whether your correction is necessary! the current code looks
like it was done in a hurry ;) but i think to all intents and purposes it is
correct
Rob
On Sat, Nov 28, 2009 at 4:52 AM, mogg <[email protected]> wrote:
>
> HoverCamer.as line 131 is linking Target.y with gz when it should be
> linking Target.y with gy instead. The same problem for line 132...gy =
> target.z when it should be gz = target.z.
>
> 131 var gz:Number = target.y + ...
> 132 var gy:Number = target.z - ...
>
>
> On Nov 16, 3:59 pm, Rob Bateman <[email protected]> wrote:
> > Hey Mogg
> >
> > not seeming able to reproduce the bug - do you have an example class that
> to
> > hand that demonstrates the problem?
> >
> > cheers
> >
> > Rob
> >
> > On Fri, Nov 13, 2009 at 7:53 PM, mogg <[email protected]> wrote:
> > > *ping* :)
> >
> > > On Nov 8, 7:11 am, mogg <[email protected]> wrote:
> > > > In Away3Dlite (trunk): if theHoverCamera'starget is at 0,0,0 then it
> > > > works perfectly!
> >
> > > > If the target is anywhere like 0,-200,0 then thehovercamerais always
> > > > below the object looking up. Even with a tilt setting of 0.
> >
> > > > if the target is anywhere like 0,200,0 then thehovercamerais always
> > > > above the object looking down. Even with a tilt setting of 0.
> >
> > --
> > Rob Bateman
> > Flash Development & Consultancy
> >
> > [email protected]
>
--
Rob Bateman
Flash Development & Consultancy
[email protected]
www.infiniteturtles.co.uk
www.away3d.com
