 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I could not find a command line switch for, nor any mention of, periodically
saving the image to a file while rendering it. Is this done automatically? I'm
not talking about animation. I'm talking about rendering a single very high
resolution image.
I see how to initiate a controlled abort, and how to resume where you left off
later. What I'm not sure about is how to resume from a power outage, which would
effectively be an uncontrolled abort. If POVray provides no way to periodically
and automatically save what has been rendered so far to a file, that does not
bode well. Please tell me I am wrong about this. Thanks for any clue.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"peyrol" <nomail@nomail> wrote:
> I could not find a command line switch for, nor any mention of, periodically
> saving the image to a file while rendering it. Is this done automatically? I'm
> not talking about animation. I'm talking about rendering a single very high
> resolution image.
>
> I see how to initiate a controlled abort, and how to resume where you left off
> later. What I'm not sure about is how to resume from a power outage, which would
> effectively be an uncontrolled abort. If POVray provides no way to periodically
> and automatically save what has been rendered so far to a file, that does not
> bode well. Please tell me I am wrong about this. Thanks for any clue.
I am rather new to POV-Ray compared to all the gurus around here, but here is
what I believe:
POV-Ray allows you to use the +C command line, which means "Continue Trace"
to start rendering from an interrupted render BUT it doesn't do so by starting
from an image since there are numerous other things involved besides pixel in a
frame's process, such as photons and their gathering pre calulated before them,
so instead, POV regularly saves its state of the scenes calculation, including
what was necessary to build it so far, and to refine it later if some new light
bounces in unrendered pixels require the previous bounces occured elsewhere.
This file would be very big but temporary, and not be deleted until image is
fully rendered, (or the whole animation?). that way, if you turn off your
computer and start rendering again from empty pov editor with "+C" the scene
will just go on rendering.
Am I correct so far guys?
About what you ask that is, saving pixels progressively, I for one would be
interested to know whether it's possible because that's one of the defaults of
Blender/POV-Ray integration: since I don't know where pixels are, when we
interrupt a render, the image simply disappears from editors while with other
renderers in Blender, you get to keep what has been rendered so far, so you can
still use it e.g. to patch another image or just compare. I also believe the
real time rendering process could more easily be made available to Blender
editor with this feature.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"peyrol" <nomail@nomail> wrote:
> I could not find a command line switch for, nor any mention of, periodically
> saving the image to a file while rendering it. Is this done automatically? I'm
> not talking about animation. I'm talking about rendering a single very high
> resolution image.
>
> I see how to initiate a controlled abort, and how to resume where you left off
> later. What I'm not sure about is how to resume from a power outage, which would
> effectively be an uncontrolled abort. If POVray provides no way to periodically
> and automatically save what has been rendered so far to a file, that does not
> bode well. Please tell me I am wrong about this. Thanks for any clue.
The procedure is the same as for an intentional abort: Unless you specify the
`-CC` command-line switch, POV-Ray automatically saves all the Rendering
Progress in the infamous "state file", allowing it to pick up on it later with
the `+C` abort-continue command-line switch.
Progress is saved not at specific time intervals, but each time a render block
is completed.
If the power outage strikes at a time where POV-Ray is just updating the state
file, there might be a possibility that the state file gets corrupted; I've
never had a look how robust POV-Ray's abort-continue mechanism would be with
respect to a truncated state file.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 6/1/2017 8:30 AM, Mr wrote:
> and not be deleted until image is
> fully rendered, (or the whole animation?). that way, if you turn off your
> computer and start rendering again from empty pov editor with "+C" the scene
> will just go on rendering.
>
> Am I correct so far guys?
>
On all of the Windoze machines I've had. The state file is not always
deleted.
>
> About what you ask that is, saving pixels progressively, I for one would be
> interested to know whether it's possible because that's one of the defaults of
> Blender/POV-Ray integration: since I don't know where pixels are, when we
> interrupt a render, the image simply disappears from editors while with other
> renderers in Blender, you get to keep what has been rendered so far, so you can
> still use it e.g. to patch another image or just compare. I also believe the
> real time rendering process could more easily be made available to Blender
> editor with this feature.
>
I believe you can do this. Bishop3D has a debug render screen (Ctrl +
Shift + Alt + F9) that displays the image as PovRay renders it. I think
that this is done via a GUI Extension. Moray used its own GUI Extension
to start PovRay.
Detail from pvengine.ini .
[GUIExtensions]
UseExtensions=1
ExtDLL16=C:\Program Files (x86)\Bishop3D\Bishop3DPovComm.dll
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"clipka" <nomail@nomail> wrote:
>
> Progress is saved not at specific time intervals, but each time a render block
> is completed.
>
> If the power outage strikes at a time where POV-Ray is just updating the state
> file, there might be a possibility that the state file gets corrupted; I've
> never had a look how robust POV-Ray's abort-continue mechanism would be with
> respect to a truncated state file.
Curious about this and I couldn't cause power loss with my notebook computer
because the battery isn't accessible without dismantling it. So I only tried End
Task from Windows 10 and the file remains usable.
However, I thought maybe I could remove the last portion of the state file and
still be able to continue a render that way. Idea being that if all it does is
append each render block info, and the last one was incomplete or corrupt, maybe
deleting back to the last complete good block would let it be usable again.
Well, no good. At least if simply editing in Notepad. Yet it is obvious, or so I
believe, where the blocks seem to begin and end. This is something like the end
of a good state file:
So removing everything from file end to next similar part was what I thought
might work okay. I'm thinking there must be something else other than just a
file append happening, or I didn't edit properly.
When I made the attempt to use +C with the edited state file the render only
restarts fresh again.
Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 02.06.2017 um 00:20 schrieb omniverse:
> However, I thought maybe I could remove the last portion of the state file and
> still be able to continue a render that way. Idea being that if all it does is
> append each render block info, and the last one was incomplete or corrupt, maybe
> deleting back to the last complete good block would let it be usable again.
>
> Well, no good. At least if simply editing in Notepad. Yet it is obvious, or so I
> believe, where the blocks seem to begin and end. This is something like the end
> of a good state file:
Notepad is not a good choice to try this. The data is binary, and I'd be
surprised if Notepad kept any binary data intact.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymous org> wrote:
> Am 02.06.2017 um 00:20 schrieb omniverse:
>
> > However, I thought maybe I could remove the last portion of the state file and
> > still be able to continue a render that way. Idea being that if all it does is
> > append each render block info, and the last one was incomplete or corrupt, maybe
> > deleting back to the last complete good block would let it be usable again.
> >
> > Well, no good. At least if simply editing in Notepad. Yet it is obvious, or so I
> > believe, where the blocks seem to begin and end. This is something like the end
> > of a good state file:
>
> Notepad is not a good choice to try this. The data is binary, and I'd be
> surprised if Notepad kept any binary data intact.
Figured it was a bad idea. Way back when I used Windows Write to change text
within programs that was usually okay, but only if I didn't touch anything else
not ever having learned C programming.
I installed a file code editor and got same result anyway when deleting back to
prior ViIdINT4, which is what I'm seeing a good state file always ends with.
Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"clipka" <nomail@nomail> wrote:
>
> The procedure is the same as for an intentional abort: Unless you specify the
> `-CC` command-line switch, POV-Ray automatically saves all the Rendering
> Progress in the infamous "state file", allowing it to pick up on it later with
> the `+C` abort-continue command-line switch.
>
> Progress is saved not at specific time intervals, but each time a render block
> is completed.
>
> If the power outage strikes at a time where POV-Ray is just updating the state
> file, there might be a possibility that the state file gets corrupted; I've
> never had a look how robust POV-Ray's abort-continue mechanism would be with
> respect to a truncated state file.
This is very helpful, thank you. If it matters, I use POVRay 3.7 under Linux
Mint with Mate 64-bit. So, if the power goes out, I should return to the
directory I was running from, and execute the same command line with the +C
option added, and it SHOULD pick up from the latest automatic save, yes?
If the latest save got corrupted, would an earlier save still be accessible?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 17-06-01 à 02:34, peyrol a écrit :
> I could not find a command line switch for, nor any mention of, periodically
> saving the image to a file while rendering it. Is this done automatically? I'm
> not talking about animation. I'm talking about rendering a single very high
> resolution image.
>
> I see how to initiate a controlled abort, and how to resume where you left off
> later. What I'm not sure about is how to resume from a power outage, which would
> effectively be an uncontrolled abort. If POVray provides no way to periodically
> and automatically save what has been rendered so far to a file, that does not
> bode well. Please tell me I am wrong about this. Thanks for any clue.
>
>
>
Unless you disabled the .povstate file, then, you are covered.
Using +c on the command line will always resume your render, no mather
how it was interupted. At most, you'll loose the last render block that
the was worked upon.
If you are rendering a photon using scene and you choose to save the
photons to a file, they are saved before the first render block is even
started. So, you can load them back, saving you the time required to
shoot them.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 17-06-01 à 04:47, Stephen a écrit :
> On 6/1/2017 8:30 AM, Mr wrote:
>> and not be deleted until image is
>> fully rendered, (or the whole animation?). that way, if you turn off your
>> computer and start rendering again from empty pov editor with "+C" the
>> scene
>> will just go on rendering.
>>
>> Am I correct so far guys?
>>
>
> On all of the Windoze machines I've had. The state file is not always
> deleted.
It's always deleted once the render finishes normally.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
