> orienting the local coordsys of a branch is pretty hackish > tho -- as there is no easy way to set orientation to match something > (excluding calculating matrix transformations :), it first moves the > local cs to where the branch begins, then uses the nice look_at to > orientate it towards the end of the branch, and then moves the cs to > the end where the next branch should grow from.. some addition to the > API might be in place?
I think you can also use a "vectorial look_at", i.e. pass a vector to look_at instead that a position. In this case, you don't need to move the local cs before looking_at. Jiba
