![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
in <dvqvetgsa97drekp8a1d6nunenfuhrtoq9@4ax.com> Peter Popov wrote:
> You could do that with the Pre_Scene_Command and Post_Scene_Command
> INI file options.
>
My problem with this and Geoff's solution is that you have to render
the complete image twice. The render data are saved when the first
render is completly done, not just after the the pretrace is done.
When rendering the second image, the pretrace sequence seems to be
done again. Or is this just the reading of the data file?
Ingo
--
Photography: http://members.home.nl/ingoogni/
Pov-Ray : http://members.home.nl/seed7/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
ingo <ing### [at] home nl> wrote:
> in <dvqvetgsa97drekp8a1d6nunenfuhrtoq9@4ax.com> Peter Popov wrote:
>> You could do that with the Pre_Scene_Command and Post_Scene_Command
>> INI file options.
>>
> My problem with this and Geoff's solution is that you have to render
> the complete image twice. The render data are saved when the first
> render is completly done, not just after the the pretrace is done.
> When rendering the second image, the pretrace sequence seems to be
> done again. Or is this just the reading of the data file?
I would assume (perhaps incorrectly) that the pretrace would read in the
file, just as it does when you do it manually. Or is there something funky
you do in the manual reads?
Geoff
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
in <3af01891@news.povray.org> Geoff Wedig wrote:
>> Or is this just the reading of the data file?
>
> I would assume (perhaps incorrectly) that the pretrace would read
> in the file, just as it does when you do it manually. Or is there
> something funky you do in the manual reads?
Changed count from 80 to 1000 to see if there is a time difference.
First pass the pretrace is finished after 18 min. Total render time, 45
min.
Second pass, reading the data/ pretrace, 4 min. Total render time 6
min. Quite a big difference, I didn't notice in the earlier experiments
as the total rendertime's where mutch shorter.
Ingo
--
Photography: http://members.home.nl/ingoogni/
Pov-Ray : http://members.home.nl/seed7/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
ingo <ing### [at] home nl> wrote:
> in <3af01891@news.povray.org> Geoff Wedig wrote:
>>> Or is this just the reading of the data file?
>>
>> I would assume (perhaps incorrectly) that the pretrace would read
>> in the file, just as it does when you do it manually. Or is there
>> something funky you do in the manual reads?
> Changed count from 80 to 1000 to see if there is a time difference.
> First pass the pretrace is finished after 18 min. Total render time, 45
> min.
> Second pass, reading the data/ pretrace, 4 min. Total render time 6
> min. Quite a big difference, I didn't notice in the earlier experiments
> as the total rendertime's where mutch shorter.
Yes, that'd make a big difference. adding the always_sample off might also
make a difference.
Geoff
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |