|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I see some pictures on the IRTC that took hours to render on powerful computers,
yet I can render a scene with almost 200,000 objects in just a matter of minutes
on an average computer. What is happening here?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Aarqon" <aar### [at] gmailcom> wrote in message
news:web.481a0daf93e49df8fd5d0c920@news.povray.org...
>I see some pictures on the IRTC that took hours to render on powerful
>computers,
> yet I can render a scene with almost 200,000 objects in just a matter of
> minutes
> on an average computer. What is happening here?
advanced textures (texture_maps), advanced lighting (area_light), media,
radiosity, isosurfaces... they all slow down the render by massive amounts,
but add equal amounts of realism :)
cu!
--
#macro G(b,e)b+(e-b)*C/50#end#macro _(b,e,k,l)#local C=0;#while(C<50)
sphere{G(b,e)+3*z.1pigment{rgb G(k,l)}finish{ambient 1}}#local C=C+1;
#end#end _(y-x,y,x,x+y)_(y,-x-y,x+y,y)_(-x-y,-y,y,y+z)_(-y,y,y+z,x+y)
_(0x+y.5+y/2x)_(0x-y.5+y/2x) // ZK http://www.povplace.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Aarqon <aar### [at] gmailcom> wrote:
> I see some pictures on the IRTC that took hours to render on powerful computers,
> yet I can render a scene with almost 200,000 objects in just a matter of minutes
> on an average computer. What is happening here?
Try defining transparency, reflection and refraction to those objects.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp napsal(a):
> Aarqon <aar### [at] gmailcom> wrote:
>> I see some pictures on the IRTC that took hours to render on powerful computers,
>> yet I can render a scene with almost 200,000 objects in just a matter of minutes
>> on an average computer. What is happening here?
>
> Try defining transparency, reflection and refraction to those objects.
>
Dispersion will do perfectly (you can crank up the sample count).
Strong antialiasing also takes its time.
Blurred reflection is very intensive.
The slowest object in povray is a parametric surface but it is rarely used.
Complex isosurfaces (as Zeger mentioned) are common and may be very slow.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Zeger Knaepen" <zeg### [at] povplacecom> wrote:
> "Aarqon" <aar### [at] gmailcom> wrote in message
> news:web.481a0daf93e49df8fd5d0c920@news.povray.org...
> >I see some pictures on the IRTC that took hours to render on powerful
> >computers,
> > yet I can render a scene with almost 200,000 objects in just a matter of
> > minutes
> > on an average computer. What is happening here?
>
> advanced textures (texture_maps), advanced lighting (area_light), media,
> radiosity, isosurfaces... they all slow down the render by massive amounts,
> but add equal amounts of realism :)
>
> cu!
> --
> #macro G(b,e)b+(e-b)*C/50#end#macro _(b,e,k,l)#local C=0;#while(C<50)
> sphere{G(b,e)+3*z.1pigment{rgb G(k,l)}finish{ambient 1}}#local C=C+1;
> #end#end _(y-x,y,x,x+y)_(y,-x-y,x+y,y)_(-x-y,-y,y,y+z)_(-y,y,y+z,x+y)
> _(0x+y.5+y/2x)_(0x-y.5+y/2x) // ZK http://www.povplace.com
I didn't really use any of those, so that explains it.
PS One of the IRTC pics apparently took over four days to render just the top
half. :P Granted it was a really cool pic. Fire and Water I think.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Aarqon nous illumina en ce 2008/05/01 14:36 -->
> I see some pictures on the IRTC that took hours to render on powerful computers,
> yet I can render a scene with almost 200,000 objects in just a matter of minutes
> on an average computer. What is happening here?
>
>
Take your scene with about 1/10th the object count.
Use some complex layered textures.
Make them partialy transparent and add some variable reflection.
Add an interior block with ior, dispersion and color fading. Crank op
max_trace_level to 255 as you'll need that.
Add some blured reflection,... and refraction.
Turn on antialiasing: +am2 +a0.01 +r5
Now, your scene that rendered in minutes will render in hours, if not days.
And you don't have any isosurface nor parametric.
--
Alain
-------------------------------------------------
HAMMER: Originally employed as a weapon of war, the hammer nowadays is used as
a kind of divining rod to locate expensive bike parts not far from the object we
are trying to hit.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alain <ele### [at] netscapenet> wrote:
> Aarqon nous illumina en ce 2008/05/01 14:36 -->
> > I see some pictures on the IRTC that took hours to render on powerful computers,
> > yet I can render a scene with almost 200,000 objects in just a matter of minutes
> > on an average computer. What is happening here?
> >
> >
> Take your scene with about 1/10th the object count.
> Use some complex layered textures.
> Make them partialy transparent and add some variable reflection.
> Add an interior block with ior, dispersion and color fading. Crank op
> max_trace_level to 255 as you'll need that.
> Add some blured reflection,... and refraction.
>
> Turn on antialiasing: +am2 +a0.01 +r5
>
> Now, your scene that rendered in minutes will render in hours, if not days.
> And you don't have any isosurface nor parametric.
>
> --
> Alain
> -------------------------------------------------
> HAMMER: Originally employed as a weapon of war, the hammer nowadays is used as
> a kind of divining rod to locate expensive bike parts not far from the object we
> are trying to hit.
So a lot of work goes into it, work that isn't in mine. :B
I try.
Also, how long would it take if I did all that with my 200,000 objects?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Aarqon wrote:
> Also, how long would it take if I did all that with my 200,000 objects?
Try it and see? :)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nicolas Alvarez wrote:
> Aarqon wrote:
>> Also, how long would it take if I did all that with my 200,000 objects?
>
> Try it and see? :)
In this case, when applying all known trickery to 200.000 objects, you may
not live long enough to see the result
--
Ger
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Aarqon nous illumina en ce 2008/05/05 13:32 -->
> Alain <ele### [at] netscapenet> wrote:
>> Aarqon nous illumina en ce 2008/05/01 14:36 -->
>>> I see some pictures on the IRTC that took hours to render on powerful computers,
>>> yet I can render a scene with almost 200,000 objects in just a matter of minutes
>>> on an average computer. What is happening here?
>>>
>>>
>> Take your scene with about 1/10th the object count.
>> Use some complex layered textures.
>> Make them partialy transparent and add some variable reflection.
>> Add an interior block with ior, dispersion and color fading. Crank op
>> max_trace_level to 255 as you'll need that.
>> Add some blured reflection,... and refraction.
>>
>> Turn on antialiasing: +am2 +a0.01 +r5
>>
>> Now, your scene that rendered in minutes will render in hours, if not days.
>> And you don't have any isosurface nor parametric.
>>
>> --
>> Alain
>> -------------------------------------------------
>> HAMMER: Originally employed as a weapon of war, the hammer nowadays is used as
>> a kind of divining rod to locate expensive bike parts not far from the object we
>> are trying to hit.
>
> So a lot of work goes into it, work that isn't in mine. :B
> I try.
> Also, how long would it take if I did all that with my 200,000 objects?
>
>
I don't think that going from 10 000 to 200 000, or 500 000 or even 1 000 000,
objects will make a big difference on the render time, but it will have a big
effect on the parsing time. Available ram and swaping can become a big factor in
the render time.
Now, add some area_light, then, add scathering media, not fog.
--
Alain
-------------------------------------------------
If you can’t get your work done in the first 24 hr’s, work nights.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|