|
 |
On Fri, 20 Nov 1998 13:09:34 -0500, Lewis Sellers <lse### [at] usit net> wrote:
>1) ability to determine the bounds of any complex object (esp. text
>objects) which would be useful for collision detection.
What do you mean by bounds? Do you want to find the surface of the object,
or the bounding box? My contributions to the superpatch allow you to
trace arbitrary rays (thus allowing you to at least sample the surface of
the object) and to compute the bounding box.
>2)ability to read heightfields data like a 2d array (so random tree and
>rock objects, for example, sit ON the ground and not 10 ft under. :)
Since you can sample the surface of an object, you can easily determine
the elevation of a heightfield at any given point, as well as the slope.
>3)and the addition of translate_path, rotate_path and scale_path, which
>are curve-based animation functions (operating similiar to say
>color_map) using the 0 to 1 of the clock variable. Operating on all
>objects including camera.
Please explain this in more detail. Specifically, what syntax should this
have? Also, I'm having trouble determining how scale can be correlated
with a path. If all you're looking for is a convenient way to generate a
spline through a series of points or scalar values, this too is in the
superpatch (though I didn't write that patch) or available as an include
file from Chris Colefax's page.
Granted, none of these things are yet in the official version (well, the
include file is) but anything could happen. The superpatch is at
http://twysted.net/patchstation and I hope to have a new version with
the new 3.1 windows editor, as well as a Linux and maybe a DOS port,
online very soon.
s
Post a reply to this message
|
|
