|
|
clipka <ano### [at] anonymousorg> wrote:
> Am 20.08.2017 um 00:51 schrieb Kenneth:
> > I actually didn't know (or remember?) that there was a *default*
> > inside_vector.
> > I should have re-read the docs; it has been awhile re: this topic.
>
> Not sure where that quote is from, but if it ever was true, it has been
> outdated for a long time.
>
> Fact is, in current versions of POV-Ray the default value for the
> `inside_vector` parameter is the null vector (`<0,0,0>`), which is used
> as a special value to turn off that feature.
Yes, IIRC that agrees with my own v3.6xx experience using meshes (i.e., there's
no *useful* default inside_vector.) I haven't actually used a mesh in awhile,
though.
BTW, this opens up a small 'can of worms' regarding SHAPES.INC: The various
mesh-generation macros there do not add an inside_vector, which precludes those
meshes being used in (other than union) CSG, as they are not generally #written
to a file but used 'internally' by POV-Ray, so to speak. However, the
HFCREATE() macro near the end of that file CAN be used to #write a mesh to a
text file for later use-- but it lacks an inside_vector as well. I modified my
own SHAPES.INC file years ago, to add that feature to HFCREATE-- but I currently
can't find it :-( I don't know for sure if an *arbitrary* vector can be added
there, although my own experience was that it worked OK (as I never created an
'open' mesh with Shapes.inc...although a few of the macros may allow open meshes
as an option. I think the 'cylinder mesh' macro may be one. In which case an
arbitrary vector would be hit-or-miss. <0,1,0> would probably work most of the
time, I'm guessing.)
Just wanted to mention this for future thought. And I apologize for getting way
off-topic...
Post a reply to this message
|
|