1) PROGRESSIVE RENDER.
The one thing I like about Bryce is that it does a progressive render:
first shows you a 40 x 30 render of your scene, then a 160 x 120, and so
on up to the resolution you're asking for. When positioning my camera, I
often want to do something like this. If I have a really complex object
or special effect, I have to wait a long time to see the "feet" of my
image just to see if it's positioned right.   I suppose I could change
my quickres.ini file to include these scenes and do the extra dozen
mouseclicks each time to see a progressively greater resolution, but
isn't that what we have computers for?

2) VOLUME
I'd like to be able to know the volume of an object.

Post a reply to this message

"Greg M. Johnson" wrote:
> 
> 1) PROGRESSIVE RENDER.

You will be happy : it's already there !! Command-line options
+SP +EP ..

> 2) VOLUME

For simple primitives, knowing the volume is easy.  For more
complex stuff, you could write a #macro that samples the volume
of an object, using the "object" pattern (in MegaPOV).

Fabien.

Post a reply to this message

Fabien Mosen wrote:

> "Greg M. Johnson" wrote:
> > 1) PROGRESSIVE RENDER.
>
> You will be happy : it's already there !! Command-line options
> +SP +EP ..

Could you please tell me the menu for the Windows version and the phrase
I could add to POVRAY.INI?

>
> > 2) VOLUME
>
> For simple primitives, knowing the volume is easy.  For more
> complex stuff, you could write a #macro that samples the volume
> of an object, using the "object" pattern (in MegaPOV).
>
> Fabien.

I can imagine how to do this with a few zillion trace calls and counting
cubes, but not immediately how to do with object pattern.

Post a reply to this message

--

Ian

Inkwell: Ian's Homepage
http://www.topcities.com/cartoon/inkwell/index.htm
"Greg M. Johnson" <gre### [at] my-dejanewscom> wrote in message
news:39B79C30.E480F2D9@my-dejanews.com...
> 1) PROGRESSIVE RENDER.

What's wrong with mosaic preview?? from memory its +sp in the .ini file
followed by a multiple of 4.  +sp 32 for example.


--

Ian

Inkwell: Ian's Homepage
http://www.topcities.com/cartoon/inkwell/index.htm

Post a reply to this message

Ian Witham wrote:

> What's wrong with mosaic preview?? from memory its +sp in the .ini file
> followed by a multiple of 4.  +sp 32 for example.

Wow! This is neat!

For us non-switch-typing mortals, we would add

Preview_Start_Size=4

to POVRAY.INI,

Post a reply to this message

that's why it's a good idea to have a printed version of the docs and to
read them once a month.  there's always something new to learn.

"Greg M. Johnson" wrote:
> 
> Ian Witham wrote:
> 
> > What's wrong with mosaic preview?? from memory its +sp in the .ini file
> > followed by a multiple of 4.  +sp 32 for example.
> 
> Wow! This is neat!
> 
> For us non-switch-typing mortals, we would add
> 
> Preview_Start_Size=4
> 
> to POVRAY.INI,

Post a reply to this message

"Greg M. Johnson" <gre### [at] my-dejanewscom> wrote in message
news:39B7AFF0.B38E4942@my-dejanews.com...

> Wow! This is neat!
>
> For us non-switch-typing mortals, we would add
>
> Preview_Start_Size=4
>
> to POVRAY.INI,
>

In megaPov, Mosaic preview doesn't work with radiosity enabled.... and even
if you turn radiosity off, the preview won't work until you restart MegaPov.
I'd call that a bug ;-)

sorry just a random rant.....

--

Ian

Inkwell: Ian's Homepage
http://www.topcities.com/cartoon/inkwell/index.htm

Post a reply to this message

I would really like that POV-4 had associative arrays of heterogeneous
elements. For example:

arr["location"] = <1,1,1>;
arr["texture"] = texture { ... }
arr["show"] = true;

etc.

Why?

Well, with this kind of containers it would be possible to fake object
oriented programming. For example

#macro MySmartBox_Create(this)
    this = assoc_array();
    this["location"] = 0;
    this["side"] = 1;
#end

#macro MySmartBox_Display(this)
    object {
        this["location"] - <Side/2, Side/2, Side2>,
        this["location"] + <Side/2, Side/2, Side2>
        texture {
            this["texture"]
        }
    }
#end

etc.

Having associative heterogeneous arrays + macros is all that is needed for
OOP in POVRay.

Post a reply to this message

On Thu, 7 Sep 2000 22:17:53 +0200, Alessandro Coppo wrote:
>
>Well, with this kind of containers it would be possible to fake object
>oriented programming. For example

[...]

>Having associative heterogeneous arrays + macros is all that is needed for
>OOP in POVRay.

Careful there, you'll get Warp all revved up again.  What you're talking
about is structured programming, not OOP.

-- 
Ron Parker   http://www2.fwi.com/~parkerr/traces.html
My opinions.  Mine.  Not anyone else's.

Post a reply to this message

In article <39B79FDF.16E6555D@my-dejanews.com>, 
gre### [at] my-dejanewscom wrote:

> I can imagine how to do this with a few zillion trace calls and counting
> cubes, but not immediately how to do with object pattern.

Use eval_pattern() with the object pattern, using the object you are 
calculating the volume of as the control object for the pattern. Check 
eval_pattern() multiple times in a 3D grid and use the results to 
calculate the volume.

-- 
Christopher James Huff
Personal: chr### [at] maccom, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tagpovrayorg, http://tag.povray.org/

<><

Post a reply to this message