 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
3.1.2.1.5 Field Rendering
Do modern HD video standards still use alternating scan lines?
3.1.2.2.4 Resuming Options
"This option reads in the previously generated output file, displays the
partial image rendered so far, then proceeds with the ray-tracing."
I still don't quite understand this. Does this work only for the very
latest render? Is there a way to resume a render from a day ago, or a
week? What if I've renamed the output image or other files in the meantime?
--
http://isometricland.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 23.06.10 18:58, SharkD wrote:
> 3.1.2.1.5 Field Rendering
>
> Do modern HD video standards still use alternating scan lines?
<http://en.wikipedia.org/wiki/High-definition_television>
> 3.1.2.2.4 Resuming Options
>
> "This option reads in the previously generated output file, displays the
> partial image rendered so far, then proceeds with the ray-tracing."
>
> I still don't quite understand this. Does this work only for the very
> latest render? Is there a way to resume a render from a day ago, or a
> week? What if I've renamed the output image or other files in the meantime?
Consider asking these questions in povray.newusers. The alternative might be
to try it and see ... which would also be faster than asking.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"SharkD" <pos### [at] gmail com> schreef in bericht
news:4c223d46$1@news.povray.org...
> 3.1.2.2.4 Resuming Options
>
> "This option reads in the previously generated output file, displays the
> partial image rendered so far, then proceeds with the ray-tracing."
>
> I still don't quite understand this. Does this work only for the very
> latest render? Is there a way to resume a render from a day ago, or a
> week? What if I've renamed the output image or other files in the
> meantime?
>
With +C you resume the render at the place where you last stopped the render
of a scene. Any changes to the scene in between will of course be visible as
a clear break in the resulting image. So it is generally not a good idea to
changes the scene while in the render process. I don't know about renaming
files in the meantime. If you are consistent in the name giving, the render
may continue, but you will have to try that out.
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 6/24/2010 4:07 AM, Thomas de Groot wrote:
> With +C you resume the render at the place where you last stopped the render
> of a scene. Any changes to the scene in between will of course be visible as
> a clear break in the resulting image. So it is generally not a good idea to
> changes the scene while in the render process. I don't know about renaming
> files in the meantime. If you are consistent in the name giving, the render
> may continue, but you will have to try that out.
>
> Thomas
I was hoping for a method to restart an arbitrary failed render,
regardless of its age or whether the files have moved to other locations
or renamed in the meantime.
The Start/End_Row commands will most likely suffice, though determining
the exact row value might be /slightly/ tricky.
--
http://isometricland.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 25.06.2010 14:57, schrieb SharkD:
> On 6/24/2010 4:07 AM, Thomas de Groot wrote:
>> With +C you resume the render at the place where you last stopped the
>> render
> I was hoping for a method to restart an arbitrary failed render,
> regardless of its age or whether the files have moved to other locations
> or renamed in the meantime.
Strictly speaking, there is no way to /continue/ a /failed/ render:
Whatever the reason was for failure, another attempt is pretty likely to
fail for the very same reason.
+C only gives you a way to continue /aborted/ renders, i.e. where you
said, "screw it, I don't have the patience for this today".
The mechanism is that when you abort a render preliminarily, POV-Ray (A)
writes the output file as far as it got, and (B) dumps some internal
state variables to a file, the name of which will be derived from (IIRC)
the main scene file name (might be the output file name though, I'd have
to look that up).
What you still need to make sure yourself when picking up the render
again, is that (A) you use the same command line and INI file parameters
(except for the +C and possibly radiosity and photons load/save
options), and (B) the scene file parses the same as before.
If you're using the Start/End_Row options, essentially the same
limitations will apply, or you'll risk a visible transition between the
"old" and "new" portions of the resulting image. And you'll have more
work to do.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 6/25/2010 9:42 AM, clipka wrote:
> Strictly speaking, there is no way to /continue/ a /failed/ render:
> Whatever the reason was for failure, another attempt is pretty likely to
> fail for the very same reason.
>
> +C only gives you a way to continue /aborted/ renders, i.e. where you
> said, "screw it, I don't have the patience for this today".
>
> The mechanism is that when you abort a render preliminarily, POV-Ray (A)
> writes the output file as far as it got, and (B) dumps some internal
> state variables to a file, the name of which will be derived from (IIRC)
> the main scene file name (might be the output file name though, I'd have
> to look that up).
>
> What you still need to make sure yourself when picking up the render
> again, is that (A) you use the same command line and INI file parameters
> (except for the +C and possibly radiosity and photons load/save
> options), and (B) the scene file parses the same as before.
>
> If you're using the Start/End_Row options, essentially the same
> limitations will apply, or you'll risk a visible transition between the
> "old" and "new" portions of the resulting image. And you'll have more
> work to do.
Thanks for the explanation!
--
http://isometricland.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
