http://news.povray.org/povray.general/message/%3Cweb.55d76b3d49d08eec7a3e03fe0%40news.povray.org%3E/#%3Cweb.55d76b3d49d
08eec7a3e03fe0%40news.povray.org%3E

Post a reply to this message

Attachments:
Download 'parametric.jpg' (243 KB)

Preview of image 'parametric.jpg'

"LanuHum" <Lan### [at] yandexru> wrote:
>
http://news.povray.org/povray.general/message/%3Cweb.55d76b3d49d08eec7a3e03fe0%40news.povray.org%3E/#%3Cweb.55d76b3d4
9d
> 08eec7a3e03fe0%40news.povray.org%3E

I waited for the end of a render (It is the notice!!! No material, no photons,
no radio, all - no):
Render Time:
  Photon Time:      No photons
  Radiosity Time:   No radiosity
  Trace Time:       1 hours 15 minutes 30 seconds (4530.792 seconds)
              using 4 thread(s) with 16423.073 CPU-seconds total
POV-Ray finished

Truth! It is the finish!

#version 3.7;

#include "functions.inc"
global_settings {
    assumed_gamma 1.000000
}
sky_sphere {
    pigment {rgb<0.050, 0.050, 0.050>}
}

#declare Default_texture = texture{pigment {rgb 0.8}}

#declare data_Parametric_shape_ob = parametric {
    function { cos(v)*(1+cos(u))*sin(v/8) }
    function { sin(u)*sin(v/8)+cos(v/8)*1.5 }
    function { sin(v)*(1+cos(u))*sin(v/8) }
    <0.0000,0.0000>, <6.2800,12.5700>
    contained_by { box{-1, 1} }
    max_gradient 5.000000
    accuracy 0.001000
    precompute 10 x,y,z
}
object {data_Parametric_shape_ob
    texture {Default_texture}
    matrix <1.000000, 0.000000, 0.000000,  0.000000, -0.000000, -1.000000,
0.000000, 1.000000, -0.000000,  0.000000, 0.000000, 0.000000>
}

light_source {
    <5.07,5.58,4.28>
    color rgb<1, 1, 1>
    fade_distance 25.0000000000
    fade_power 1
}
camera {
    perspective
    location  <0,0,0>
    look_at  <0,0,-1>
    right <-1.7777777777777777, 0, 0>
    up <0, 1, 0>
    angle  49.134343
    rotate  <-27.098163, 46.688390, -0.903519>
    translate <7.481132, 5.343666, 6.507640>
}

Post a reply to this message

Attachments:
Download 'parametric_final.jpg' (138 KB)

Preview of image 'parametric_final.jpg'

On 8/22/2015 8:55 PM, LanuHum wrote:
>      contained_by { box{-1, 1} }

Have you tried increasing the contained_by?

-- 

Regards
     Stephen

Post a reply to this message

Stephen <mca### [at] aolcom> wrote:
> On 8/22/2015 8:55 PM, LanuHum wrote:
> >      contained_by { box{-1, 1} }
>
> Have you tried increasing the contained_by?
>
> --
>
> Regards
>      Stephen

No!
I don't know an origin of these parameters.
I only try to connect the Blender with Povray.
Therefore I ask for help.
Thanks!
The increase in contained_by normalizes a situation.
Let the user choose.
I wouldn't begin to use objects of parametric in the scenes because of very long
time of a render.
Developers advance the ideas.
Sometimes these ideas incorrect, but I can't interfere
http://www.youtube.com/watch?v=nVO1zDQc5LU

Post a reply to this message

On 8/22/2015 10:13 PM, LanuHum wrote:
> Stephen <mca### [at] aolcom> wrote:
>> On 8/22/2015 8:55 PM, LanuHum wrote:
>>>       contained_by { box{-1, 1} }
>>
>> Have you tried increasing the contained_by?
>>
>> --
>>
>> Regards
>>       Stephen
>
> No!
> I don't know an origin of these parameters.
> I only try to connect the Blender with Povray.
> Therefore I ask for help.
> Thanks!
> The increase in contained_by normalizes a situation.
> Let the user choose.

You might want to try min_extent and max_extent to define the 
contained_by box (can also be a sphere)

Help 3.3.1.6.5 Functions

min_extent(OBJECT_IDENTIFIER), max_extent(OBJECT_IDENTIFIER). The 
min_extent and max_extent return the minimum and maximum coordinates of 
a #declared object's bounding box (Corner1 and Corner2), in effect 
allowing you to find the dimensions and location of the object.

Note: This is not perfect, in some cases (such as CSG intersections and 
differences or isosurfaces) the bounding box does not represent the 
actual dimensions of the object.

> I wouldn't begin to use objects of parametric in the scenes because of very long
> time of a render.

Me too :)

> Developers advance the ideas.
> Sometimes these ideas incorrect, but I can't interfere

True ;-)

> http://www.youtube.com/watch?v=nVO1zDQc5LU
>

I do not understand why you show this
Unless it is an example of this:

>> Developers advance the ideas.
>> Sometimes these ideas incorrect, but I can't interfere

:-)
-- 

Regards
     Stephen

Post a reply to this message

Am 23.08.2015 um 06:08 schrieb Stephen:
> On 8/22/2015 10:13 PM, LanuHum wrote:
>> Stephen <mca### [at] aolcom> wrote:
>>> On 8/22/2015 8:55 PM, LanuHum wrote:
>>>>       contained_by { box{-1, 1} }
>>>
>>> Have you tried increasing the contained_by?
>>>
>>> -- 
>>>
>>> Regards
>>>       Stephen
>>
>> No!
>> I don't know an origin of these parameters.
>> I only try to connect the Blender with Povray.
>> Therefore I ask for help.
>> Thanks!
>> The increase in contained_by normalizes a situation.
>> Let the user choose.
> 
> You might want to try min_extent and max_extent to define the
> contained_by box (can also be a sphere)

Unfortunately that won't help with this issue, as min_extent and
max_extent give you the extent of the object's bounding box (rather than
the object itself), which in case of parametrics is in turn simply based
on the contained_by object.

One possible solution would be to evaluate some sample points from the
function set (possibly using an adaptive algorithm), and create the
contained_by box based on the range of the results (with some additional
margin).

Post a reply to this message

I'm not sure if Pov-Ray converts a Parametric to a mesh for rendering. If  
it does, then maybe it would be faster if you use the Blender mesh rather  
than the Pov-Ray paramtric.

Another reason for the slow speed might be that the camera is placed in a  
position that results in too many computations - it almost looks like the  
camera is inside the shell or intersecting with the edge of the shell.

-- 
-Nekar Xenos-

Post a reply to this message

Stephen <mca### [at] aolcom> wrote:
> On 8/22/2015 10:13 PM, LanuHum wrote:
> > Stephen <mca### [at] aolcom> wrote:
> >> On 8/22/2015 8:55 PM, LanuHum wrote:
> >>>       contained_by { box{-1, 1} }
> >>
> >> Have you tried increasing the contained_by?
> >>
> >> --
> >>
> >> Regards
> >>       Stephen
> >
> > No!
> > I don't know an origin of these parameters.
> > I only try to connect the Blender with Povray.
> > Therefore I ask for help.
> > Thanks!
> > The increase in contained_by normalizes a situation.
> > Let the user choose.
>
> You might want to try min_extent and max_extent to define the
> contained_by box (can also be a sphere)
>
> Help 3.3.1.6.5 Functions
>
> min_extent(OBJECT_IDENTIFIER), max_extent(OBJECT_IDENTIFIER). The
> min_extent and max_extent return the minimum and maximum coordinates of
> a #declared object's bounding box (Corner1 and Corner2), in effect
> allowing you to find the dimensions and location of the object.
>
> Note: This is not perfect, in some cases (such as CSG intersections and
> differences or isosurfaces) the bounding box does not represent the
> actual dimensions of the object.
>
> > I wouldn't begin to use objects of parametric in the scenes because of very long
> > time of a render.
>
> Me too :)
>
> > Developers advance the ideas.
> > Sometimes these ideas incorrect, but I can't interfere
>
> True ;-)
>
> > http://www.youtube.com/watch?v=nVO1zDQc5LU
> >
>
> I do not understand why you show this
> Unless it is an example of this:
>
> >> Developers advance the ideas.
> >> Sometimes these ideas incorrect, but I can't interfere
>
> :-)
> --
>
> Regards
>      Stephen

Thanks! Yes, you correct understand :)



clipka <ano### [at] anonymousorg> wrote:
> Am 23.08.2015 um 06:08 schrieb Stephen:
> > On 8/22/2015 10:13 PM, LanuHum wrote:
> >> Stephen <mca### [at] aolcom> wrote:
> >>> On 8/22/2015 8:55 PM, LanuHum wrote:
> >>>>       contained_by { box{-1, 1} }
> >>>
> >>> Have you tried increasing the contained_by?
> >>>
> >>> --
> >>>
> >>> Regards
> >>>       Stephen
> >>
> >> No!
> >> I don't know an origin of these parameters.
> >> I only try to connect the Blender with Povray.
> >> Therefore I ask for help.
> >> Thanks!
> >> The increase in contained_by normalizes a situation.
> >> Let the user choose.
> >
> > You might want to try min_extent and max_extent to define the
> > contained_by box (can also be a sphere)
>
> Unfortunately that won't help with this issue, as min_extent and
> max_extent give you the extent of the object's bounding box (rather than
> the object itself), which in case of parametrics is in turn simply based
> on the contained_by object.
>
> One possible solution would be to evaluate some sample points from the
> function set (possibly using an adaptive algorithm), and create the
> contained_by box based on the range of the results (with some additional
> margin).

Thanks!


"Nekar Xenos" <nek### [at] gmailcom> wrote:
> I'm not sure if Pov-Ray converts a Parametric to a mesh for rendering. If
> it does, then maybe it would be faster if you use the Blender mesh rather
> than the Pov-Ray paramtric.
>
> Another reason for the slow speed might be that the camera is placed in a
> position that results in too many computations - it almost looks like the
> camera is inside the shell or intersecting with the edge of the shell.
>
> --
> -Nekar Xenos-

I test all objects at one position of the camera. If the sphere is rendered
quickly, I can't tell that it is rendered slowly.
But, my opinion is only my opinion. Let users decide that such quickly and that
such slowly. I can't use a renderer of Cycles, because very slowly. Others use
and rejoice, are happy.
Also, I give transformations to a renderer not to spend time for writing of the
file.
But, if to convert all objects in mesh, to the Blender it will be heavy

Post a reply to this message

"Nekar Xenos" <nek### [at] gmailcom> wrote:
> I'm not sure if Pov-Ray converts a Parametric to a mesh for rendering. If
> it does, then maybe it would be faster if you use the Blender mesh rather
> than the Pov-Ray paramtric.
>
>
> --
> -Nekar Xenos-

Certainly, the mesh is rendered very quickly.
On formulas the Blender creates mesh 1 second.
+ click on modifiers button, select modifier and press smooth button.
That with these formulas does Povray taking away more than an hour I don't even
assume. :)

Post a reply to this message

Attachments:
Download 'parametric_to_mesh.jpg' (278 KB)

Preview of image 'parametric_to_mesh.jpg'

On 8/23/2015 5:39 AM, clipka wrote:
>> You might want to try min_extent and max_extent to define the
>> >contained_by box (can also be a sphere)

> Unfortunately that won't help with this issue, as min_extent and
> max_extent give you the extent of the object's bounding box (rather than
> the object itself), which in case of parametrics is in turn simply based
> on the contained_by object.
>

Interesting

> One possible solution would be to evaluate some sample points from the
> function set (possibly using an adaptive algorithm), and create the
> contained_by box based on the range of the results (with some additional
> margin).
>

This makes me think that Nekar's idea of creating a mesh is a starting 
point.

If LanuHum could create and export a mesh of the object (declared but 
not called). PovRay could evaluate its bounding box and use those values 
as the parametrics contained by.

-- 

Regards
     Stephen

Post a reply to this message