"MichaelJF" <mi-### [at] t-onlinede> wrote:
..
>
> 7. The continue-option is still a bit buggy. Having a multi-core machine you are
> only save if you stop the rendering when the rendered area is "closed" in a way.
> That means, if you use the default render pattern, all blocks
> left and above the last rendered block must be rendered. If one is missing, the
> resume option will forget and not render it.
I forgot to mention that +c only works with the default render pattern.

Sorry,
Michael

Post a reply to this message

"MichaelJF" <mi-### [at] t-onlinede> wrote:
> Hello Lennie,
>
> some additional remarks.
>
> 1. Since you mentioned a start and a stop button, I assume you're using the
> windows version. In this case you don't need an ini-file. Simply type +c into
> the command line field (the one below the show-, ini- and sel-run-button) and
> better do so for the second and all subsequent runs and not for the first, as
> John suggested.
>
> 2. The radiosity settings you gave, have to be specified within the pov-file
> within the global_settings. The inclusion of "rad_def.inc" seems to be redundant
> here, since it is not used. The definitions of p_start and p_end_final are fine,
> but produce long rendering times for the radiosity
> step.
>
> 3. The parsing of the scene is not part of the "continue"-option. Every time you
> you restart a Rendering with +c the whole scene will be parsed again.
>
> 4. For photons it is the best to save them during the first render, and load
> them in subsequent ones.
>
> 5. radiosity can be saved with the first run, but you need other global settings
> to load them. And an ini-file is needed in this case.
>
> 6. radiosity is recalculated with every retrace, but only the part which is not
> rendered already.
>
> 7. The continue-option is still a bit buggy. Having a multi-core machine you are
> only save if you stop the rendering when the rendered area is "closed" in a way.
> That means, if you use the default render pattern, all blocks
> left and above the last rendered block must be rendered. If one is missing, the
> resume option will forget and not render it.
> See
>
>
http://news.povray.org/povray.binaries.images/thread/%3C5239bc36%40news.povray.org%3E/?ttop=390778&toff=50
>
> for an example.
>
> Best regards,
> Michael

Fantastic! Michael, and you others, thank you! This is all much clearer to me
now. I'm not just new to POV-Ray, but to 3D rendering overall. Trying out
different software and renderers at the moment, and I must say POV-Ray gives
really nice, characteristic, results.

Regards,

Lennie

Post a reply to this message

On 27/01/14 20:57, IceflakeCS wrote:
> 
> Fantastic! Michael, and you others, thank you! This is all much clearer to me
> now. I'm not just new to POV-Ray, but to 3D rendering overall. Trying out
> different software and renderers at the moment, and I must say POV-Ray gives
> really nice, characteristic, results.
> 
> Regards,
> 
> Lennie
> 
> 

When you are ready to post them, I am sure we all would like to see some
of your images - since you seem to have long render times, they must be
fairly complex.

Welcome to the community.

John
-- 
Protect the Earth
It was not given to you by your parents
You hold it in trust for your children

Post a reply to this message

> Hi,
>
> I hope someone is able to help me.
>
> I am quite new to POV-Ray, although I have known about it for 15-20 years.
>
> When I'm trying to render a scene which takes more than a day to render, I use
> the resuming option. I have read the documentation numerous of times, but I
> can't really get it to work. In the QUICKRES.INI file (I have also tried the
> command line options), I have added the following two lines:
>
> Continue_Trace=on
> Create_Ini=rerun.ini
>
> When I start rendering, POV-Ray is creating the rerun.ini file as well as the
> ..pov-state file. The Messages tab also claims "Continued trace......On".
>
> However, if I have stopped the rendering using the Stop button, and later
> (doesn't matter if I have or have not closed POV-Ray) decide to continue, it
> doesn't matter what I do. I can't resume from where I left off.
>
> I have tried both command line, like the documentation suggests:
>
> pvengine64.exe RERUN +C
> (Also tried with rerun.ini instead of RERUN)
>
> I have tried opening the .pov file in POV-Ray and pushing Run, as well as
> opening the created rerun.ini file pushing Run.
>
> Is there something I'm missing? Why doesn't POV-Ray continuing rendering my
> scene from where it stopped earlier?
>
> Regards,
>
> Lennie
>
>

Apparently, you are using the Windows version.

Don't use +c when first starting the render, only on an interupted render.

Put +c in the command line box, then click the Run button.. It's the 
only thing you need to do.

Make sure that you resume using the SAME resolution that you used initialy.

If your scene use radiosity, the radiosity pretrace will be performed 
again, but only for the un-rendered part of your image.

If using photons AND you did NOT save the photons to a file anr reload 
that file, the photons shooting phase will need to be done again in it's 
totality.

You don't need to use any rerun.ini file.

I highly recomment that you remove
Continue_Trace=on
Create_Ini=rerun.ini
from your quickres.ini file. That file is to be used EXCLUSIVELY to 
store predefined image dimentions/resolution. Nothing else.

If you start from the console using pvengine64.exe RERUN, i don't think 
that you need the +c. In fact, it may be the cause of your problems...

So, just une +c in the command line box.



Alain

Post a reply to this message

Doctor John <j.g### [at] gmailcom> wrote:

>
> When you are ready to post them, I am sure we all would like to see some
> of your images - since you seem to have long render times, they must be
> fairly complex.
>
> Welcome to the community.
>
> John
> --
Seconded,
Michael

Post a reply to this message

"MichaelJF" <mi-### [at] t-onlinede> wrote:
> Doctor John <j.g### [at] gmailcom> wrote:
>
> >
> > When you are ready to post them, I am sure we all would like to see some
> > of your images - since you seem to have long render times, they must be
> > fairly complex.
> >
> > Welcome to the community.
> >
> > John
> > --
> Seconded,
> Michael

Since you are new to POV I assume you are new to the newsgroups as well. You
cannot post images here. You must use the group "povray-binary-images". Be sure,
we will notice your uploads there.

Best regards,
Michael

Post a reply to this message

Doctor John <j.g### [at] gmailcom> wrote:
> On 27/01/14 20:57, IceflakeCS wrote:
> >
> > Fantastic! Michael, and you others, thank you! This is all much clearer to me
> > now. I'm not just new to POV-Ray, but to 3D rendering overall. Trying out
> > different software and renderers at the moment, and I must say POV-Ray gives
> > really nice, characteristic, results.
> >
> > Regards,
> >
> > Lennie
> >
> >
>
> When you are ready to post them, I am sure we all would like to see some
> of your images - since you seem to have long render times, they must be
> fairly complex.
>
> Welcome to the community.
>
> John
> --
> Protect the Earth
> It was not given to you by your parents
> You hold it in trust for your children

Thank you John.

But really, they are nothing special at all. At the moment I'm just fooling
around with different scenes and settings. The reason they take so long to
render is because of the radiosity function.

Example 1
https://dl.dropboxusercontent.com/u/10144729/POVRAY/01.png

Rendered with radiosity, render time 14+ hours

Example 2
https://dl.dropboxusercontent.com/u/10144729/POVRAY/02.png

Rendered without radiosity, render time about 1.5 minutes.

It's a big difference between those images, but not 14 hour difference.

Post a reply to this message

"IceflakeCS" <nomail@nomail> wrote:
> Doctor John <j.g### [at] gmailcom> wrote:
> > On 27/01/14 20:57, IceflakeCS wrote:
> > >
> > > Fantastic! Michael, and you others, thank you! This is all much clearer to me
> > > now. I'm not just new to POV-Ray, but to 3D rendering overall. Trying out
> > > different software and renderers at the moment, and I must say POV-Ray gives
> > > really nice, characteristic, results.
> > >
> > > Regards,
> > >
> > > Lennie
> > >
> > >
> >
> > When you are ready to post them, I am sure we all would like to see some
> > of your images - since you seem to have long render times, they must be
> > fairly complex.
> >
> > Welcome to the community.
> >
> > John
> > --
> > Protect the Earth
> > It was not given to you by your parents
> > You hold it in trust for your children
>
> Thank you John.
>
> But really, they are nothing special at all. At the moment I'm just fooling
> around with different scenes and settings. The reason they take so long to
> render is because of the radiosity function.
>
> Example 1
> https://dl.dropboxusercontent.com/u/10144729/POVRAY/01.png
>
> Rendered with radiosity, render time 14+ hours
>
> Example 2
> https://dl.dropboxusercontent.com/u/10144729/POVRAY/02.png
>
> Rendered without radiosity, render time about 1.5 minutes.
>
> It's a big difference between those images, but not 14 hour difference.

Forgot to mentioned these were originally rendered in 3840x2160.

Post a reply to this message

On 28/01/14 21:21, IceflakeCS wrote:
>> Example 1
>> https://dl.dropboxusercontent.com/u/10144729/POVRAY/01.png
>>
>> Rendered with radiosity, render time 14+ hours
>>
>> Example 2
>> https://dl.dropboxusercontent.com/u/10144729/POVRAY/02.png
>>
>> Rendered without radiosity, render time about 1.5 minutes.
>>
>> It's a big difference between those images, but not 14 hour difference.
> 
> Forgot to mentioned these were originally rendered in 3840x2160.
> 
> 

...which is why they take so long ;-) That's approximately 8.25
Megapixels. As a rule of thumb, I try not to render anything larger than
1 Mp when I'm developing a scene. It's only when I'm happy with it that
I go large.

BTW Your example was really good. Are you sure you're just a beginner?

John
-- 
Protect the Earth
It was not given to you by your parents
You hold it in trust for your children

Post a reply to this message

Doctor John <j.g### [at] gmailcom> wrote:
> On 28/01/14 21:21, IceflakeCS wrote:
> >> Example 1
> >> https://dl.dropboxusercontent.com/u/10144729/POVRAY/01.png
> >>
> >> Rendered with radiosity, render time 14+ hours
> >>
> >> Example 2
> >> https://dl.dropboxusercontent.com/u/10144729/POVRAY/02.png
> >>
> >> Rendered without radiosity, render time about 1.5 minutes.
> >>
> >> It's a big difference between those images, but not 14 hour difference.
> >
> > Forgot to mentioned these were originally rendered in 3840x2160.
> >
> >
>
> ...which is why they take so long ;-) That's approximately 8.25
> Megapixels. As a rule of thumb, I try not to render anything larger than
> 1 Mp when I'm developing a scene. It's only when I'm happy with it that
> I go large.
>
> BTW Your example was really good. Are you sure you're just a beginner?
>
> John
> --
> Protect the Earth
> It was not given to you by your parents
> You hold it in trust for your children

I was just surprised by the difference in time between the one rendered with
radiosity and the one without :)

And yes, still claim to be just a beginner. Installed Blender during Christmas
holidays, and in the beginning of January I decided to install POV-Ray as well.
This scene hasn't been coded in POV-Ray, that I would never (probably) be able
to do as programming (not even the easy languages) is far from my best quality
:)

But I will have a look into the coding later on, as it seems you can create some
really crazy stuff (abstract 3D) using it.

Post a reply to this message