I'm working on a scene with a table made of iso-plankes (just like those in
the isowood include file). With the beta 7 these isos render MUCH slower:
beta 6: 1 m 45 s
beta 7: 8 m 22 s.
These planks are simple f_rounded_box displaced with a wood pigment.
Christoph, can you confirm?

POV-Ray 3.5 beta 7 Windows ME Athlon
(Intel compile)

--
Jonathan.

Post a reply to this message

In article <3bdf24b3$1@news.povray.org> , "JRG" <jrg### [at] hotmailcom> wrote:

> I'm working on a scene with a table made of iso-plankes (just like those in
> the isowood include file). With the beta 7 these isos render MUCH slower:
> beta 6: 1 m 45 s
> beta 7: 8 m 22 s.
> These planks are simple f_rounded_box displaced with a wood pigment.

Providing a scene might be useful....

    Thorsten

Post a reply to this message

Right:
Here is the code without modifications:


#include "functions.inc"
#include "colors.inc"
//#include "woodmaps.inc"
#include "woods.inc"

#declare table_x=150;
#declare table_y=3;
#declare table_z=90;
#declare n=8;
#declare RS=seed(0);

#declare i=0;
#while (i<n)

#declare pig_wood=
pigment {
    wood
    scale 0.5
    turbulence 0.07
    rotate 90*y
    warp {
        black_hole
        <0,3/2,0>, 2
        strength 2
        falloff 2
        inverse
        repeat 2*<10,0,10>
        turbulence 0.5
    }
     rotate <rand(RS),rand(RS),rand(RS)>*2 translate
<rand(RS),rand(RS)*0,rand(RS)>*30


    }

#declare pig_func=
function { pigment {pig_wood color_map {[0 rgb 0][1 rgb 1]}}}


isosurface {
    function {
        f_rounded_box (x,y,z,0.5,table_x/2,table_y/2,table_z/2/n) +
pig_func(x,y,z).gray*0.08
    }
    accuracy 10^-3
    max_gradient 2
    evaluate 1,10,.99
    contained_by {box {-<table_x,table_y,table_z/n>/2,
<table_x,table_y,table_z/n>/2}}

    pigment {
        pig_wood
        color_map {M_Wood3A}
    }
    finish {ambient 0 diffuse 0.8 specular 0.1 roughness 0.02 brilliance
1.25}
    scale <1,1,0.99>
    translate (-table_z/n/2-table_z/n*i)*z+(-0.25+0.5*rand(RS))*y
    translate 50*z

}

#undef pig_func //without this one it crashes (in beta 6. I don't know about
beta 7 (which I have to reinstall))
#declare i=i+1;
#end


camera {
    location <0,20,-50>
    look_at 0
    rotate 10*y}

light_source {
    <150,150,-150>
    rgb 1.5
    fade_power 2
    fade_distance 300}

background {rgb 0.5}

Post a reply to this message

In article <3bdf2d82@news.povray.org> , "JRG" <jrg### [at] hotmailcom> wrote:

>  evaluate

I can confirm that isosurfaces that use "evaluate", and *only* isosurfaces
that use "evaluate" exhibit this speed problem in beta 7.  The workaround is
to use "evaluate" only if absolutely necessary.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:
: I can confirm that isosurfaces that use "evaluate", and *only* isosurfaces
: that use "evaluate" exhibit this speed problem in beta 7.  The workaround is
: to use "evaluate" only if absolutely necessary.

  Is this phenomenon temporary or has it came to stay?

-- 
#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

In article <3bdf9c43@news.povray.org> , Warp <war### [at] tagpovrayorg>  wrote:

> : The workaround is
> : to use "evaluate" only if absolutely necessary.
>
>   Is this phenomenon temporary or has it came to stay?

Workaround usually suggests something temmporary for me.  As far as details
are concerned, after looking a bit closer into the code for "evaluate" it
seems like it is almost redundant:  The parameters you specifc after the
"evaluate" keyword only had a function if no max_gradient was set.
Consequently this would lead to the odd behavior that if and only if the
default max_gradient (which is 1.1) was used, max_gradient itself would be
adjusted.  Unfortunately, due to a logic mistake I kept one of these
modifications of max_gradient also it should have been removed.  I think I
have a fix for this already*.


    Thorsten

* Warp: Do a sync (get change 1235) to try it.


____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Thorsten Froehlich wrote:
> 
> I can confirm that isosurfaces that use "evaluate", and *only* isosurfaces
> that use "evaluate" exhibit this speed problem in beta 7.  The workaround is
> to use "evaluate" only if absolutely necessary.
> 

That's really sad, i was just starting to use it intensively.  Apart from
being incredibly slow it also seems to produce wrong results.

Christoph

-- 
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other 
things on: http://www.schunter.etc.tu-bs.de/~chris/

Post a reply to this message

In article <3BDFBF72.F7D52C4F@gmx.de> , Christoph Hormann 
<chr### [at] gmxde>  wrote:

> That's really sad, i was just starting to use it intensively.

That is part of beta testing.  It is not really a serious problem, it is
just very slow...

> Apart from
> being incredibly slow it also seems to produce wrong results.

No, it only changes your max_gradient.  The reported found maximum gradient
value is still correct.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

JRG wrote:
> 
> I'm working on a scene with a table made of iso-plankes (just like those in
> the isowood include file). With the beta 7 these isos render MUCH slower:
> beta 6: 1 m 45 s
> beta 7: 8 m 22 s.
> These planks are simple f_rounded_box displaced with a wood pigment.
> Christoph, can you confirm?
> 

I can confirm that evaluate can be quite slow.  NTL, with the isowood
sample i tried, evaluate led to faster results for some reason.  Note that
it only worked with the MSVC compile, the intel version still crashes
(probably because of the function declaration problems)

Christoph

-- 
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other 
things on: http://www.schunter.etc.tu-bs.de/~chris/

Post a reply to this message

In article <3BDFC6D1.332E1CE6@gmx.de> , Christoph Hormann 
<chr### [at] gmxde>  wrote:

> (probably because of the function declaration problems)

No, those should be gone.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message