 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi,
I'm trying to render a not so complicated scene: it's only a box with some parts
cut out. In the box a couple (9) of lights.
Now rendering this on a quadcore system in 1280x1024 (-A 0.1) takes days!
This is the result of the script with 1 lightsource (takes 10 hours to render):
http://vanheusden.com/pov/test4c.png
The script with 9 lights can be found here:
http://vanheusden.com/pov/pov-slow.zip
Has anyone any suggestions how i can speed up the rendering? I'm very much
surprised that 1 or 9 lights makes such a difference. But with one light it
still takes almost half a day to render.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"folkert" <fol### [at] vanheusden com> wrote:
> Hi,
>
> I'm trying to render a not so complicated scene: it's only a box with some parts
> cut out. In the box a couple (9) of lights.
> Now rendering this on a quadcore system in 1280x1024 (-A 0.1) takes days!
> This is the result of the script with 1 lightsource (takes 10 hours to render):
> http://vanheusden.com/pov/test4c.png
> The script with 9 lights can be found here:
> http://vanheusden.com/pov/pov-slow.zip
>
> Has anyone any suggestions how i can speed up the rendering? I'm very much
> surprised that 1 or 9 lights makes such a difference. But with one light it
> still takes almost half a day to render.
Well, it looks like it's not "only a box with some parts cut out".
There's at least two reflective planes with what looks like reflection 1.0.
This will greatly increase the number of rays shot.
Also, is the box material reflective? If so you have your answer why it's so
slow.
Regards
Aydan
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 01.08.11 17:03, folkert wrote:
> Has anyone any suggestions how i can speed up the rendering?
Don't use such a complex CSG object. For every ray traced, the whole
difference needs to be checked, so you get no benefit of bounding (which you
cannot add manually in a meaningful way to a difference like this object).
The best approach here is to split the outer cube into eight symmetrically
identical smaller cubes. This should get you a speed-up of roughly eight
times right there.
Also, note that you can texture CSGs as a whole, no need to texture each part.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 01/08/2011 17:03, folkert nous fit lire :
> I'm trying to render a not so complicated scene: it's only a box with some parts
> cut out. In the box a couple (9) of lights.
Lol, a difference of a Box with about 4000 box for a kind of menger sponge.
You should either:
1. try an additive approach (union of many smaller boxes)
2. have some spatial hierarchy in your difference (difference of
sub-union, even difference / union / union) so that the testing of
bounding box does not have to be perform on all objects.
The camera is also on the surface of the cube, which might be an issue
for finding the intersection. (hollow ?)
It might save some characters by declaring the texture and using its
reference
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 8/1/2011 8:03, folkert wrote:
> Has anyone any suggestions how i can speed up the rendering?
Look at the summary at the end of the render and see where POV is spending
its time.
I have a building with a ton of lights in it, and each light makes it
slower. I too was getting rendering times of days because the way I had
constructed the building meant there was no bounding, so every wall was
being tested against every ray from every light.
--
Darren New, San Diego CA, USA (PST)
How come I never get only one kudo?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> > Has anyone any suggestions how i can speed up the rendering?
>
> Don't use such a complex CSG object. For every ray traced, the whole
> difference needs to be checked, so you get no benefit of bounding (which you
> cannot add manually in a meaningful way to a difference like this object).
> The best approach here is to split the outer cube into eight symmetrically
> identical smaller cubes. This should get you a speed-up of roughly eight
> times right there.
>
> Also, note that you can texture CSGs as a whole, no need to texture each part.
As a quick test I replaced the CSG by a combination of individual boxes.
My quadcore took days for the CSG, in the new version my intel atom laptop takes
seconds :-)
Thanks you all for the suggestions!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Look at this site: http://www.econym.demon.co.uk/holetut/index.htm it
will answer some of your problems.
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
