I'd like to use a previously-declared object with clipped_by.
Unfortunately this object has a texture, so of course errors are raised
when using it for clipping. Is there a syntax that would allow me to
"remove" the texture from an object, or create a new object without a
texture that is otherwise a copy of another?

-Eamon

Post a reply to this message

Eamon Caddigan <eca### [at] uiucedu> wrote:
> I'd like to use a previously-declared object with clipped_by.
> Unfortunately this object has a texture, so of course errors are raised
> when using it for clipping. Is there a syntax that would allow me to
> "remove" the texture from an object, or create a new object without a
> texture that is otherwise a copy of another?

  Sorry, there's no currently a way of doing that.
  You'll have to modify the original object to easily remove its
texture (eg. enclose its texture definitions inside #ifdef blocks).

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

Warp <war### [at] tagpovrayorg> wrote:
> Eamon Caddigan <eca### [at] uiucedu> wrote:
>> I'd like to use a previously-declared object with clipped_by.
>> Unfortunately this object has a texture, so of course errors are raised
>> when using it for clipping. Is there a syntax that would allow me to
>> "remove" the texture from an object, or create a new object without a
>> texture that is otherwise a copy of another?
>
>   Sorry, there's no currently a way of doing that.
>   You'll have to modify the original object to easily remove its
> texture (eg. enclose its texture definitions inside #ifdef blocks).

Thanks for the reply, even if it isn't what I wanted to hear.

Just out of curiosity (and feel free to not waste your time answering
this), why enforce the "no texture" rule for clipping objects anyway? I
can think of plenty of reasons to clip by an object that's also drawn,
and in my case (programically-created scene files), it would be pretty
convenient. I tried to think of a good reason to insist that clip
objects not be textured from POV-Ray's standpoint, but couldn't come up
with anything.

-Eamon

Post a reply to this message

In article <409706ca$1@news.povray.org>,
 Eamon Caddigan <eca### [at] uiucedu> wrote:

> Just out of curiosity (and feel free to not waste your time answering
> this), why enforce the "no texture" rule for clipping objects anyway? I
> can think of plenty of reasons to clip by an object that's also drawn,
> and in my case (programically-created scene files), it would be pretty
> convenient. I tried to think of a good reason to insist that clip
> objects not be textured from POV-Ray's standpoint, but couldn't come up
> with anything.

No technical reason that it couldn't be done, but it would waste memory 
to store the texture for an object that will never be visible. 
Personally, I think it should let the memory be wasted for the time 
being, it would be less likely to be a problem.

-- 
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: <chr### [at] tagpovrayorg>
http://tag.povray.org/

Post a reply to this message