POV-Ray : Newsgroups : povray.general : POV features : Re: POV features Server Time
7 Aug 2024 11:17:08 EDT (-0400)
  Re: POV features  
From:
Date: 29 Nov 2001 02:15:54
Message: <38nb0ustvl38012clbvf7o71mqbehv43oo@4ax.com>
On Wed, 28 Nov 2001 14:26:08 +0000, s1631001 <s16### [at] namtarqubacuk> wrote:
> W?odzimierz ABX Skiba <abx### [at] babilonorg> wrote:
> > Do you know #include and #declare directive?
> I know I could just #declare a value for the golden ratio, (as I often
> do), but then we could do that for pi as well surely; we don't really
> _need_ them built-in, it's just handy.

Perhaps it is some kind of backward compatibility ?

> Mark Wagner <mar### [at] gtenet> wrote:
> > #fkill("c:\windows\win.com")
> Excellent point; I had considered that and, as Warp says, we would need
> restrictions on #fkill. Perhaps it could only kill files created by
> POV-Ray?

Why POV should introduce another level of privilages if it is rule of system
administrator ? AFAIK POV 3.5 inherits privilages from system.

> W?odzimierz ABX Skiba <abx### [at] babilonorg> wrote:
> > Are you thinking about matrices with transformations ?
> No, general matrices of arbitrary size. I guess my #macros will do the
> job (when finished), but I'd like to see built-in support.

So, the answer is IMO "POV-Ray is not mathematical tool but reytracer". POV
supports data structures nad programing tools to extend usage but base rule is
to trace objects.

> Now for the really contraversial one...
> I came up with the idea for the polygonal preview after a particulary
> long trace on my laptop (known as "The Breezeblock") which took several
> minutes for a test render (and this a fairly simple scene).
> isosurface{
>  $ISOSURFACE_STUFF$
>  approx_object{
>    union{
>      cylinder{ -2*x, 2*x, 1 }
>      cylinder{ -2*y, 2*y, 1 }
>      cylinder{ -2*z, 2*z, 1 }
>    }
>  }
> }

But you can still do that. Look below.

#declare Preview=yes; // or no
#if(Preview)
  isosurface{$ISOSURFACE_STUFF$}
#else
    union{
      cylinder{ -2*x, 2*x, 1 }
      cylinder{ -2*y, 2*y, 1 }
      cylinder{ -2*z, 2*z, 1 }
    }
#end

and this way is much more better
becouse you can mix previews with real appearances.

> Here's some more ideas for you to argue over...
>
> 5> animation variables "current_frame", "initial_frame", "total_frames"
> I am SO tired of having to redo an animation render because I #declared
> the wrong value for final_frame (usually because I test-render at a
> lower framecount)

you can find it in POV 3.5

> 6> The ability to tell POV-Ray when we only want an include file to be
> parsed once, instead of having to use special handling systems (check
> the very top and bottom of any standard include for example).

There is everything ok with 'special handling systems'. But you can read about
'project' idea sended by me in another thread.

ABX
--
#declare _=function(a,b,x){((a^2)+(b^2))^.5-x}#default {pigment{color rgb 1}}
union{plane{y,-3}plane{-x,-3}finish{reflection 1 ambient 0}}isosurface{ //ABX
function{_(x-2,y,1)|_((x+y)*.7,z,.1)|_((x+y+2)*.7,z,.1)|_(x/2+y*.8+1.5,z,.1)}
contained_by{box{<0,-3,-.1>,<3,0,.1>}}translate z*15finish{ambient 1}}//POV35


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.