Hard to say what you are trying to achieve/encountering since there is no compiled version, but the problem might be with the lookAt function. I and maybe a few others had trouble using the lookAt function. http://groups.google.com/group/away3d-dev/browse_thread/thread/97f7f439a321873/99323699b3fecfe6?lnk=gst&q=simple+camera+problem#99323699b3fecfe6
I just wanted the camera to look directly downwards, or along a global axis, but the camera would would not rotate for some reason unless I skewed the vector away from the the unit axis vectors. (i.e., instead of looking at (0, 0, 0), I made it look at (0, 0, 0.001) ). Never found a fix to it or why it was happening. Such a bug did not occur in Away 3.5 as I had many demos/projects that did such a thing. This is why we need a forum. I would post a new issue, but I just hate the fact that there's no way of telling if they have been reviewed. I already have two outstanding issues that I don't know whether they will be solved or addressed, or just fixed in away3d 4.0 On Apr 7, 8:36 am, Bob Warfield <b...@thewarfields.com> wrote: > I have attached source code for a real simple demo. It does nothing other > than show the Trident. If you compile it with 3.5 libraries, the Trident is > correct. If you compile with 3.6, the Trident is cockeyed. > > There are 2 changes required to switch between the libraries: > > - Comment or uncomment the import of Number3D. > - Comment or uncomment the routines at the top that say "3.5 Version" or > "3.6 Version". > > There's not an awful lot that changes between the two versions other than > whether I user Number3D or Vector3D yet the two Tridents are very > different. That doesn't seem right. > > Can somebody please help? > > Best, > > BW > > GWAway3D.mxml > 1KViewDownload > > GWizCamDemo.as > 10KViewDownload
