 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi All,
I've created a model in a 3rd party software and exported it to POV(for
finishing), that has multiple objects in it. I want to use the "union"
statement/function to group all the objects for moving, rotating, etc.
I've seen the examples shown here, but I have a question.
When exported to POV from another software, POV shows each object as
"mesh2" with it's list of vectors, faces, etc., but no location
coordinates or scaling values. So when declaring each object, and giving
them names, is there a defalut set of values in POV that will keep your
objects sizes/coordinates(in relation to the model) the same, or does
this have to be written in? If someone could give me a good clear
example of how to do this, I would appreciate it.
Les
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
<nospam@nospam> wrote in message news:3B61C022.7060803@nospam...
>
> I've created a model in a 3rd party software and exported it to POV(for
> finishing), that has multiple objects in it. I want to use the "union"
> statement/function to group all the objects for moving, rotating, etc.
> I've seen the examples shown here, but I have a question.
> When exported to POV from another software, POV shows each object as
> "mesh2" with it's list of vectors, faces, etc., but no location
> coordinates or scaling values. So when declaring each object, and giving
> them names, is there a defalut set of values in POV that will keep your
> objects sizes/coordinates(in relation to the model) the same, or does
> this have to be written in? If someone could give me a good clear
> example of how to do this, I would appreciate it.
Hopefully this is the answer: min_extent and max_extent, keywords in
MegaPOV.
Plus writing it in :-)
These are known as the Bounds Patch (section 9.1 of the MP doc, examples
there) for getting the smallest and largest vector (corners) of a object.
You would then need to apply those in some way to place and scale your
separate objects to a uniform size. CSG union of them in itself is no
problem.
Bob H.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Bob H. <omn### [at] msn com> wrote:
: These are known as the Bounds Patch (section 9.1 of the MP doc, examples
: there) for getting the smallest and largest vector (corners) of a object.
Not the object, but its bounding box.
This is a very important difference as the bounding box of some objects
may not be perfect (eg. they are much bigger than the object itself).
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
nospam@nospam wrote:
> Hi All,
> When exported to POV from another software, POV shows each object as
> "mesh2" with it's list of vectors, faces, etc., but no location
> coordinates or scaling values.
I don't know what software you used, but a converter like 3DWin outputs in
the povray file the coordinates of the containing box.
G.
--
**********************
http://www.oyonale.com
**********************
Graphic experiments
Pov-ray gallery
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
