alvaro zabala wrote:
>
> We use an easier terrain navigator than this.
>
> We have a "Terrain" class, which has a property called geometry which is a
> double[ ] [ ] array.
> the same array which we use to create a QuadArray with the terrain.
Yes, as I said at the top of the tutorial - this is a *generalised*
terrain following algorithm. If you can always guarantee that the
terrain is always in a certain form and that viewer's position does not
have any transformation above it then you can make a lot of
optimisations. That is, if you don't let your viewer look up and down or
roll side to side, and you should be fine. However, if they can move in
anything other than the X-Z plane you will have to do intersections.
--
Justin Couch http://www.vlc.com.au/~justin/
Freelance Java Consultant http://www.yumetech.com/
Author, Java 3D FAQ Maintainer http://www.j3d.org/
-------------------------------------------------------------------
"Humanism is dead. Animals think, feel; so do machines now.
Neither man nor woman is the measure of all things. Every organism
processes data according to its domain, its environment; you, with
all your brains, would be useless in a mouse's universe..."
- Greg Bear, Slant
-------------------------------------------------------------------
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
