|
![](/i/fill.gif) |
Aarqon nous illumina en ce 2008/05/05 13:32 -->
> Alain <ele### [at] netscape net> 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
|
![](/i/fill.gif) |