Well, that's all and well, but it doesn't solve the fact that I want to
generate some of these objects from publically available .INC files that use
macro's to create the objects.  I COULD write my own, but to be totally honest,
I don;t have the time with 5 side-projects, and trying to get one or two entries
to irtc finished up..

    Thomas Charron

Johannes Hubert wrote:

> Thomas Charron wrote in message <35AE262D.64CC0984@nermail.ups.com>...
> >    Hrm..  Ya, this would do it..  I'd only need to do it once, then import
> the
> >object into the modeller from the Povray script generated..  Maybee a
> couple of
> >times for random effect scripts..  Thanks for the tip!  I'll keep ya
> posted..
>
> Actually, have you thought about using UDOs?
>
> UDOs work like this:
>
> You have two files: one UDO file and one INC file.
> The UDO file follows a certain standard and describes how the object should
> look in Moray.
> The INC file can contain *any* POV-Ray compliant syntax (even while-loops,
> other includes etc.) and describes how the object looks in POV-Ray.
>
> In Moray you manipulate (translate, scale, rotate, even texture) the object
> representation as it is read from the UDO file. But when exporting, Moray
> doesn't export this UDO description or any POV-Ray primitives or such, but
> simply an include directive to include the INC file (with all the
> manipulations applied).
>
> This way, you can have *any* POV-Ray object (or collection of objects) as an
> object in Moray.
>
> The only drawback is, that you have to write the UDO file by hand, to create
> an adequate Moray-representation of your object. But that isn't to hard
> either, since UDO files are text files and essentially only contain a list
> of 3D vertices and a list of edges between them.
>
> Check it out!
>
> Johannes.

Post a reply to this message