Le 2025-02-23 à 16:13, 00face a écrit :
> Alain Martel <kua### [at] videotronca> wrote:
>> Le 2025-02-21 à 16:16, 00face a écrit :
>>> Where is this located or how do I turn it on?:
>>>
>>> "3.5.7.3 Start Rendering (Go!)/Stop Rendering
>>> This is a toggle. If you are not currently rendering, the command Start
>>> Rendering instructs POV-Ray for Windows to start rendering the currently loaded
>>> POV file with the current settings. While POV-Ray for Windows is rendering, the
>>> command reads Stop Rendering and will interrupt the current rendering job. You
>>> can continue an interrupted rendering job by selecting 'Continue <filename>'
>>> from the Rerun Menu."
>>>
>>> Rendering a complex image on a cloud computer which will turn off after a while
>>> if it gets no user input. I need to be able to stop, then start rendering.
>>>
>>
>> Start the render with the «+c» flag added to the command line.
>> You may also add the «continue» parameter in the .ini file when you want
>> to continue an interrupted render.
>>
>> Both will do the same thing : Resume the render where it got
>> stopped/interrupted.
> 
> Are these settings different on Windows? I have no such menu. I do have
> Continue_Trace=on in my povray.ini file and I have +C in the console bar.
> 
Look just at the top of the editor. You have the resolutions list, and, 
just to the right, there is a box where you can write some text. That's 
the command line box. You can put a «+c» to continue an interrupted 
render there.

You can also use it to set the resolution, change the antialias options 
and other things.
+w36000 +h1000 +a0.0001 +r4
Will result in an image that is 36000 pixels wide, 1000 pixels high, set 
the antialias threshold to 0.0001 and use 4 levels of recursion.

Post a reply to this message

Alain Martel <kua### [at] videotronca> wrote:

> > Alain Martel <kua### [at] videotronca> wrote:

> >>> Where is this located or how do I turn it on?:
> >>>
> >>> "3.5.7.3 Start Rendering (Go!)/Stop Rendering
> >>> This is a toggle. If you are not currently rendering, the command Start
> >>> Rendering instructs POV-Ray for Windows to start rendering the currently loaded
> >>> POV file with the current settings. While POV-Ray for Windows is rendering, the
> >>> command reads Stop Rendering and will interrupt the current rendering job. You
> >>> can continue an interrupted rendering job by selecting 'Continue <filename>'
> >>> from the Rerun Menu."
> >>>
> >>> Rendering a complex image on a cloud computer which will turn off after a while
> >>> if it gets no user input. I need to be able to stop, then start rendering.
> >>>
> >>


> >> to continue an interrupted render.
> >>
> >> Both will do the same thing : Resume the render where it got
> >> stopped/interrupted.
> >
> > Are these settings different on Windows? I have no such menu. I do have
> > Continue_Trace=on in my povray.ini file and I have +C in the console bar.
> >
> Look just at the top of the editor. You have the resolutions list, and,
> just to the right, there is a box where you can write some text. That's

> render there.
>
> You can also use it to set the resolution, change the antialias options
> and other things.
> +w36000 +h1000 +a0.0001 +r4
> Will result in an image that is 36000 pixels wide, 1000 pixels high, set
> the antialias threshold to 0.0001 and use 4 levels of recursion.


Thank you for the detailed explanation. However, I believe there might be a
misunderstanding. My current settings are '+W1280 +H720 +A0.05 +AM3 +HR +RVP +R5
+Q11 +FE +KI1 +KF36 +KFI38 +KFF73 +RS8 +BS4 +B +C'  I am inquiring about how and
why the settings or menu options differ on Windows.

There seems to be a disconnect between what is stated on in the codices official
and otherwise about options that are currently available in the windows build
GUI. If there is another place I can look for start/stop/restart of renders I
would greatly appreciate the direction.

Post a reply to this message

Le 2025-02-23 à 22:06, 00face a écrit :
> Alain Martel <kua### [at] videotronca> wrote:
>> Le 2025-02-23 à 16:13, 00face a écrit :
>>> Alain Martel <kua### [at] videotronca> wrote:
>>>> Le 2025-02-21 à 16:16, 00face a écrit :
>>>>> Where is this located or how do I turn it on?:
>>>>>
>>>>> "3.5.7.3 Start Rendering (Go!)/Stop Rendering
>>>>> This is a toggle. If you are not currently rendering, the command Start
>>>>> Rendering instructs POV-Ray for Windows to start rendering the currently loaded
>>>>> POV file with the current settings. While POV-Ray for Windows is rendering, the
>>>>> command reads Stop Rendering and will interrupt the current rendering job. You
>>>>> can continue an interrupted rendering job by selecting 'Continue <filename>'
>>>>> from the Rerun Menu."
>>>>>
>>>>> Rendering a complex image on a cloud computer which will turn off after a while
>>>>> if it gets no user input. I need to be able to stop, then start rendering.
>>>>>
>>>>
>>>> Start the render with the «+c» flag added to the command line.
>>>> You may also add the «continue» parameter in the .ini file when you want
>>>> to continue an interrupted render.
>>>>
>>>> Both will do the same thing : Resume the render where it got
>>>> stopped/interrupted.
>>>
>>> Are these settings different on Windows? I have no such menu. I do have
>>> Continue_Trace=on in my povray.ini file and I have +C in the console bar.
>>>
>> Look just at the top of the editor. You have the resolutions list, and,
>> just to the right, there is a box where you can write some text. That's
>> the command line box. You can put a «+c» to continue an interrupted
>> render there.
>>
>> You can also use it to set the resolution, change the antialias options
>> and other things.
>> +w36000 +h1000 +a0.0001 +r4
>> Will result in an image that is 36000 pixels wide, 1000 pixels high, set
>> the antialias threshold to 0.0001 and use 4 levels of recursion.
> 
> 
> Thank you for the detailed explanation. However, I believe there might be a
> misunderstanding. My current settings are '+W1280 +H720 +A0.05 +AM3 +HR +RVP +R5
> +Q11 +FE +KI1 +KF36 +KFI38 +KFF73 +RS8 +BS4 +B +C'  I am inquiring about how and
> why the settings or menu options differ on Windows.
> 
> There seems to be a disconnect between what is stated on in the codices official
> and otherwise about options that are currently available in the windows build
> GUI. If there is another place I can look for start/stop/restart of renders I
> would greatly appreciate the direction.
> 
It's in the box found here. Second box. The one containing the +a0.0001.

You can start a render from an *.ini file.
If you add : «continue»
alone on a line, then, when you start the render from that *ini file, it 
will resume the rendering of the interrupted scene.

Post a reply to this message

Attachments:
Download 'clipboard01.jpg' (37 KB)

Preview of image 'clipboard01.jpg'

Alain Martel <kua### [at] videotronca> wrote:

> > Alain Martel <kua### [at] videotronca> wrote:

> >>> Alain Martel <kua### [at] videotronca> wrote:

> >>>>> Where is this located or how do I turn it on?:
> >>>>>
> >>>>> "3.5.7.3 Start Rendering (Go!)/Stop Rendering
> >>>>> This is a toggle. If you are not currently rendering, the command Start
> >>>>> Rendering instructs POV-Ray for Windows to start rendering the currently
loaded
> >>>>> POV file with the current settings. While POV-Ray for Windows is rendering,
the
> >>>>> command reads Stop Rendering and will interrupt the current rendering job. You
> >>>>> can continue an interrupted rendering job by selecting 'Continue <filename>'
> >>>>> from the Rerun Menu."
> >>>>>
> >>>>> Rendering a complex image on a cloud computer which will turn off after a
while
> >>>>> if it gets no user input. I need to be able to stop, then start rendering.
> >>>>>
> >>>>


> >>>> to continue an interrupted render.
> >>>>
> >>>> Both will do the same thing : Resume the render where it got
> >>>> stopped/interrupted.
> >>>
> >>> Are these settings different on Windows? I have no such menu. I do have
> >>> Continue_Trace=on in my povray.ini file and I have +C in the console bar.
> >>>
> >> Look just at the top of the editor. You have the resolutions list, and,
> >> just to the right, there is a box where you can write some text. That's

> >> render there.
> >>
> >> You can also use it to set the resolution, change the antialias options
> >> and other things.
> >> +w36000 +h1000 +a0.0001 +r4
> >> Will result in an image that is 36000 pixels wide, 1000 pixels high, set
> >> the antialias threshold to 0.0001 and use 4 levels of recursion.
> >
> >
> > Thank you for the detailed explanation. However, I believe there might be a
> > misunderstanding. My current settings are '+W1280 +H720 +A0.05 +AM3 +HR +RVP +R5
> > +Q11 +FE +KI1 +KF36 +KFI38 +KFF73 +RS8 +BS4 +B +C'  I am inquiring about how and
> > why the settings or menu options differ on Windows.
> >
> > There seems to be a disconnect between what is stated on in the codices official
> > and otherwise about options that are currently available in the windows build
> > GUI. If there is another place I can look for start/stop/restart of renders I
> > would greatly appreciate the direction.
> >
> It's in the box found here. Second box. The one containing the +a0.0001.
>
> You can start a render from an *.ini file.

> alone on a line, then, when you start the render from that *ini file, it
> will resume the rendering of the interrupted scene.
Again, I don't have any issue with putting the commands or what to do with the
input box, '+W3840 +H2160 +A0.05 +R5 +Q11 +FE +KI1 +KF36 +KFI38 +KFF73 +RS8 +BS4
+B +C' is what I'm currently using.

I can't get my render to restart where it left off, despite the proper settings
and a .ini file.

Rerun.ini:
//start
Antialias_Depth=5
Antialias=On
Antialias_Threshold=0.05
Bounding=On
Bounding_Threshold=3
Continue_Trace=On
Create_Ini="rerun.ini"
Display=On
Final_Clock=36
Final_Frame=73
Height=2160
Initial_Clock=1
Initial_Frame=38
Input_File_Name="D:\.art\WAP\marbles_dell_abstract_dark.pov"
Library_Path="C:\Users\Public\Documents\LDraw\LGEO"
Library_Path="C:\Users\Public\Documents\LDraw\LGEO\lg"
Library_Path="C:\Users\Public\Documents\LDraw\LGEO\ar"
Library_Path="C:\Users\Shadow\Documents\POV-Ray\v3.7\include"
Library_Path="C:\WINDOWS\Fonts"
Output_File_Type=E
Output_To_File=On
Quality=11
Render_Block_Size=4
Render_Block_Step=8
Verbose=On
Width=3840
Work_Threads=8
continue
//end

It starts with an image of the previous run, but it's just starting at 0% and
rendering over the last frame of the previous run, rather than starting where it
left off.

Post a reply to this message

Attachments:
Download 'screenshot 2025-02-24 165736.png' (242 KB)

Preview of image 'screenshot 2025-02-24 165736.png'

On 2/24/25 17:59, 00face wrote:
> Work_Threads=8
> continue
> //end
> 
> It starts with an image of the previous run, but it's just starting at 0% and
> rendering over the last frame of the previous run, rather than starting where it
> left off.

I've not been following this thread closely as I don't run on windows, 
but that 'continue' string caught my eye. I assume this is really 
pointing to a "continue.ini" file?

Did you create that file or is it some automatic windows interface thing?

What is in it?

Prior to trying to continue, do you see a state file with a .pov-state 
suffix for the frame number for which you are trying to continue the 
render? It will be in the directory where you are saving your frame images.

---

You must be running v3.7 as you don't have v3.8's 
create_continue_trace_log= ?

I'll attach my current yuqk documentation for continue_trace= / +c. The 
implementation is slightly different and I'm running on linux, but I 
expect the issues one might see are often similar. Maybe something 
therein a help.

Bill P.

Post a reply to this message

Attachments:
Download 'continue_trace.txt' (5 KB)

William F Pokorny <ano### [at] anonymousorg> wrote:
> On 2/24/25 17:59, 00face wrote:
> > Work_Threads=8
> > continue
> > //end
> >
> > It starts with an image of the previous run, but it's just starting at 0% and
> > rendering over the last frame of the previous run, rather than starting where it
> > left off.
>
> I've not been following this thread closely as I don't run on windows,
> but that 'continue' string caught my eye. I assume this is really
> pointing to a "continue.ini" file?
>
> Did you create that file or is it some automatic windows interface thing?
>
> What is in it?
>
> Prior to trying to continue, do you see a state file with a .pov-state
> suffix for the frame number for which you are trying to continue the
> render? It will be in the directory where you are saving your frame images.
>
> ---
>
> You must be running v3.7 as you don't have v3.8's
> create_continue_trace_log= ?
>
> I'll attach my current yuqk documentation for continue_trace= / +c. The
> implementation is slightly different and I'm running on linux, but I
> expect the issues one might see are often similar. Maybe something
> therein a help.
>
> Bill P.

William F Pokorny <ano### [at] anonymousorg> wrote:
> On 2/24/25 17:59, 00face wrote:
> > Work_Threads=8
> > continue
> > //end
> >
> > It starts with an image of the previous run, but it's just starting at 0% and
> > rendering over the last frame of the previous run, rather than starting where it
> > left off.
>
> I've not been following this thread closely as I don't run on windows,
> but that 'continue' string caught my eye. I assume this is really
> pointing to a "continue.ini" file?
>
> Did you create that file or is it some automatic windows interface thing?
>
> What is in it?
>
> Prior to trying to continue, do you see a state file with a .pov-state
> suffix for the frame number for which you are trying to continue the
> render? It will be in the directory where you are saving your frame images.
>
> ---
>
> You must be running v3.7 as you don't have v3.8's
> create_continue_trace_log= ?
>
> I'll attach my current yuqk documentation for continue_trace= / +c. The
> implementation is slightly different and I'm running on linux, but I
> expect the issues one might see are often similar. Maybe something
> therein a help.
>
> Bill P.
Thank you very much for taking the time. I have been reading the documents over
and over, some for UNIX some for LINUX, have not really seen anything
specifically for Windows, so it's been trial and error for what commands work.
That said Create_Ini=rerun.ini is what I am having created from povray.ini which
updates and is assisted by pvengine.ini. I would love to see you in the Discord
channel for POV-Ray on my server.

I am currently running my render AGAIN lol, so the rerun.ini below is the
current one generated. If my daily driver wasn't virtualized in the cloud, I
wouldn't be in this situation, this wouldn't be an issue. But here we are.

Do you recommend I use the beta 3.8 over 3.7. 🖖🏼 Again thanks
for your time so far.

//global settings from marbles_dell_abstract_photons.pov START

#version 3.7;
global_settings {
    assumed_gamma 1.0
    photons {
        count 100000          // Number of photons to shoot
        gather 20, 100        // Min/max photons to gather at each point
        jitter 0.4            // Jitter for sampling light rays
        max_trace_level 5     // Same as main trace level
        media 100, 1.5        // Enable media photons with max steps of 100
    }
    radiosity {
        pretrace_start 0.002
        pretrace_end 0.001
        count 1600
        gray_threshold 0.5
        nearest_count 1
        error_bound 0.8
        recursion_limit 1
        minimum_reuse 0.015
        maximum_reuse 0.3
        brightness 1
    }
    max_trace_level 5
    adc_bailout 0.01/255
}

//global settings from marbles_dell_abstract_photons.pov END

|------------------------------------------------------------------------...

//povray.ini START

Width = 800
;
;
; Height of image in pixels.  Accepts integer values.
;
Height = 600
;
; Sets minimum number of objects before auto bounding kicks in.
;
;
;
; Turn display on
Display=On
;
; Turn verbose mode on
Verbose=On

; Continue Settings
Continue_Trace=on
Create_Ini=rerun.ini

Library_Path="C:\Users\Public\Documents\LDraw\LGEO"
Library_Path="C:\Users\Public\Documents\LDraw\LGEO\lg"
Library_Path="C:\Users\Public\Documents\LDraw\LGEO\ar"
Output_File_Type=N
All_Console=On
Verbose=on
Pause_When_Done=on

//povray.ini END

|------------------------------------------------------------------------...

//rerun.ini START

All_Console=On
Antialias_Depth=1
Antialias=On
Antialias_Threshold=0.1
Continue_Trace=On
Create_Ini="rerun.ini"
Display=On
Height=2160
Input_File_Name="D:\.art\WAP\marbles_dell_abstract_photons.pov"
Library_Path="C:\Users\Public\Documents\LDraw\LGEO"
Library_Path="C:\Users\Public\Documents\LDraw\LGEO\lg"
Library_Path="C:\Users\Public\Documents\LDraw\LGEO\ar"
Library_Path="C:\Users\Shadow\Documents\POV-Ray\v3.7\include"
Library_Path="C:\WINDOWS\Fonts"
Output_File_Type=E
Output_To_File=On
Pause_When_Done=On
Quality=11
Render_Pattern=2
Sampling_Method=2
Verbose=On
Width=3840
Work_Threads=8

//rerun.ini END

|------------------------------------------------------------------------...

//pvengine.ini START

[Permitted Input Paths]
1=%INSTALLDIR%
2=%PROFILEDIR%
3=%FONTDIR%
4="C:\Program Files\LDraw (64 Bit)\LGEO"
5="C:\Program Files\LDraw (64 Bit)\LGEO\lg"
6="C:\Program Files\LDraw (64 Bit)\LGEO\ar"

[Permitted Output Paths]
1=%PROFILEDIR%\Insert Menu

[GUIExtensions]
UseExtensions=1

[Scripting]
ReadWriteSourceDir=1
NoShellOuts=1

[RTR]
VideoSource=

[Info]
Rendering=1

[General]
RunCount=3
CommandLine=+W3840 +H2160 +AM2 +A0.1 +R1 +Q11 +FE +RP2 +C
TextColour=16777215
WarningColour=65535
ErrorColour=16776960
BackgroundColour=4128799
DropToEditor=1
LastRenderName=marbles_dell_abstract_photons.pov
LastRenderPath=D:\.art\WAP\
LastQueuePath=C:\Users\Shadow\Documents\POV-Ray\v3.7\Scenes
SecondaryINISection=[480x270, 16:9 AA 0.3]
VersionNo64=3.7.0.msvc10.win64
LastBitmapName=*.bmp
LastBitmapPath=C:\Program Files\POV-Ray\v3.7\Tiles
LastINIPath=C:\USERS\SHADOW\DOCUMENTS\POV-RAY\V3.7\INI
SecondaryINIFile=C:\USERS\SHADOW\DOCUMENTS\POV-RAY\V3.7\INI\QUICKRES.INI
BackgroundFile=0
SaveSettingsOnExit=1
TileBackground=0
HideNewUserHelp=0
CheckNewVersion=1
SendSystemInfo=1
ItsAboutTime=1740849436
VersionNo32=3.7.0.msvc10.win32
[Editor]
LastPath=C:\Users\Shadow\Documents\POV-Ray\v3.7\Scenes\Advanced
[ToolBar]
Band0Width=543
Band1Width=200
Band2Width=200
Band3Width=180
Band4Width=405
[MainWindow]
ShowCmd=1
NormalPositionLeft=193
NormalPositionTop=0
NormalPositionRight=975
NormalPositionBottom=740
UseToolbar=1
UseTooltips=1
[RenderWindow]
NormalPositionX=478
NormalPositionY=73
Flags=536870912
Transparency=128
Use8BitMode=0
MakeActive=1
KeepAboveMain=1
HideWhenMainMinimized=1
AutoClose=0
PreserveBitmap=1
[Messages]
FontSize=8
FontWeight=400
Font=Lucida Console
KeepMessages=0
[Renderer]
AlertSound=64
Completion=2243
Priority=2305
DutyCycle=9
AlertOnCompletion=1
AutoRender=1
PreventSleep=1
NoShelloutWait=1
SystemNoActive=1
[Sounds]
RenderCompleteSoundEnabled=1
ParseErrorSoundEnabled=1
RenderErrorSoundEnabled=1
RenderCompleteSound=C:\Program Files\POV-Ray\v3.7\sounds\Render Finished.wav
ParseErrorSound=C:\Program Files\POV-Ray\v3.7\sounds\Parse Error.wav
RenderErrorSound=C:\Program Files\POV-Ray\v3.7\sounds\Render Cancelled.wav
[LastRender]
SceneFile=povray
CurrentDirectory=D:\.art\WAP
SourceFile=D:\.art\WAP\marbles_dell_abstract_photons.pov
OutputFile=
IniOutputFile=
[DontShowAgain]
RenderwinClose=1
OutputFileLocation=1
RenderErrorSound=1
ParserErrorSound=1
RenderCompleteSound=1
DropFiles=1
[FileQueue]
QueueCount=0
Output_File_Type=N
All_Console=On
Verbose=on
Pause_When_Done=on
Vista_Buffer=On

//pvengine.ini END

Post a reply to this message

On 2/27/25 13:12, 00face wrote:
> I am currently running my render AGAIN lol, so the rerun.ini below is the
> current one generated. If my daily driver wasn't virtualized in the cloud, I
> wouldn't be in this situation, this wouldn't be an issue. But here we are.

It happens I have a few minutes ahead of an appointment. I re-read the 
entire thread - paying more attention and I see Alain suggested adding 
that 'continue' string. In the linux/unix environment (and I expect 
yours too) raw strings like this cause POV-Ray to look for a 
'continue.ini' file.

My bet at this moment is that he is using 'Create_Ini=continue.ini' so 
adding a raw 'continue' to the command line works for him(*).

Try adding, instead, the string 'rerun' the next time you try to resume 
an interrupted render(*).

---

Aside: One of the things you mentioned was that you saw a complete last 
frame in your preview window on coming back after an interruption due 
some machine virtualization(**). If this is really true, it 'might' mean 
POV-Ray was sent a signal that caused it to stop immediately after the 
last frame was rendered - in which case it will have cleaned up the 
state file. I'm unsure how the windows v3.7 version works in that case. 
I believe linux/unix will see the image file and move on to the next 
frame - but It's not something I've checked in a while.

(If v3.7 is otherwise working for you, I'd say stick with it. There are 
differences in behavior along with a large collection of fixes, but if 
you don't need the latter...)

Bill P.

(*) - FWIW. The documentation for my yuqk fork strongly discourages 
specifying files without extensions unless you use 'include_ini=rerun'.

Rather than  a 'rerun' string use: 'rerun.ini'. I felt there was too 
much potential for confusing things to happen given how aggressively 
POV-Ray tries to find valid matching .ini files. (A new +-ini flag was 
added to the yuqk fork too as the command line flag version to include 
ini files explicitly)

(**) - One would hope the virtualization was orderly rather that 
something which completely crashes or stops POV-Ray rather than pauses 
it. Is the virtualization crashing POV-Ray or do you find it in a 
stopped or paused state when you resume working?

Post a reply to this message

On 2/27/25 16:58, William F Pokorny wrote:
> Try adding, instead, the string 'rerun' the next time you try to resume 
> an interrupted render

Real life always seems to keep me busy in late February and March...

While sitting in a waiting room this morning, the storm in my head asked 
me what happens on the second use of rerun.ini where both 
'create_ini=rerun.ini' and 'include_ini=rerun.ini' are present.

Is the code smart enough to not get into a recursive 'include 
ini=rerun.ini'. descent.

I'm going to look for a slice of time to experiment a little with a 
dummy animation where I quit and continue(*) frames...

Bill P.

(*) - continue.ini is a better name  when you are continuing a render... 
This is all stuff in the windows interface and render continuations that 
I don't do regularly. It might be I'm mostly clueless.

Post a reply to this message

On 2/28/25 18:13, William F Pokorny wrote:
> Is the code smart enough to not get into a recursive 'include 
> ini=rerun.ini'. descent.

The answer is, no, where a user creates something like this in an ini file:

...
Continue_Trace=On
Create_Ini="continue.ini"
...
include_ini="continue.ini"
...

we get recursive inclusion of the continue.ini file.

To POV-Ray's credit, in all versions of POV-Ray I have in hand, the 
recursion does eventually stop and we get a vague parse error. I believe 
the general recursion depth limit for including files stops things from 
getting too out of control.

--

We can specify continue.ini on the command line - without triggering 
recursive inclusion - with any of:

povray include_ini=continue.ini
povray continue.ini
povray continue

POV-Ray does not write any include_ini="continue.ini" equivalent into 
the continue.ini file when it is specified on the command line. In other 
words, it avoids creating a recursive inclusion of the ini file in the 
saved options file.

Speaking of the create_ini= / +gi option; Unsure about the how robust it 
is in v3.7, but in v3.8 versions (including yuqk) be sure it is 
capturing all the settings you need to capture to re-run or continue a 
render. I've never done a survey of all the options, but I know for 
example, file_gamma= and display_gamma= are NOT captured with v3.8 
versions and they should be.

In a few hours of testing I picked up a handful of other small details 
which I've added to my documentation, but I believe the advice given 
previously is mostly OK. On linux/unix at least, the continue / resume 
features look to be working well with all the v3.7, v3.8 and v3.8 (yuqk) 
versions I tested.

You can in fact skip using create_ini= / +gi if you are otherwise sure 
options are not changing. With v3.7 this means rendering with +c. In 
v3.8 versions it means rendering with +c and +cc (though +cc might not 
be the smart choice where per frame render times are short).

Bill P.

Post a reply to this message

On 2/28/25 21:01, William F Pokorny wrote:
> In a few hours of testing I picked up a handful of other small details 
> which I've added to my documentation,

A few years ago Thomas picked up an issue with continued renders and 
radiosity (*). I wanted to add an issues note to my documentation for 
that so I was searching the newsgroups.

I stumbled across this comment by Christoph Hormann from October of 2001 
in a thread about continuing radiosity renders:

"At least in WinPov, the .rca gets deleted when you press 'stop'. The 
only way to maintain it is to actually kill povray while rendering. ;-)"

The .rca-file being the .pov-state filename at the time.

I don't run windows so I cannot test if this is still true. FWIW.

Bill P.

(*) - You need to use save and load radiosity samples to avoid 
radiosity{} discontinuities when continuing or setting up to continue 
renders of scenes using radiosity{}.

Post a reply to this message