 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I am using PovRay 3.5 Beta 5 and when I try to render a scene (in this case
a large image in BMP format 10240 x 7680) the render will create say 80
lines or so. (These are finished lines.) Then if I stop the render and then
restart with the +c switch the render starts at 7679 again. Why won't it
continue where it left off? I am using the load_file and save_file commands
within the radiosity section. I am setting the +c switch in the small
window next to the resolution window. The actual parms are -D +c
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
AFAIK the save_file and load_file are used only for whole renders. That is,
if you render the whole image, then you get a radiosity file which you can
reuse if you render again.
As for interrupted renders, there's no need for save_file and load_file as
POV-Ray does this automatically (it's that .rca file which appears when you
render with radiosity and which disappears if you let it render through the
end).
Or at least this is how it worked in 3.1. I haven't tested if it works
right with 3.5.
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Well I was told (and tested to prove to myself) that the load and save are
needed for partial renders to keep the continued render "correct." Without
the load and save the render changes each time you continue and causes
coloration/brightness changes to surfaces. With the save and load those
things don't happen.
The problem with the image continuing where it left off last time is my main
issue. For some reason when I continue this render it starts over (as
though I wasn't using the +c switch) even though I am using the +c switch.
"Warp" <war### [at] tag povrayorg> wrote in message
news:3bcde07c@news.povray.org...
> AFAIK the save_file and load_file are used only for whole renders. That
is,
> if you render the whole image, then you get a radiosity file which you can
> reuse if you render again.
> As for interrupted renders, there's no need for save_file and load_file
as
> POV-Ray does this automatically (it's that .rca file which appears when
you
> render with radiosity and which disappears if you let it render through
the
> end).
> Or at least this is how it worked in 3.1. I haven't tested if it works
> right with 3.5.
>
> --
> #macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
> rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
> ],13),8)-3,10>#end blob{N(array[6]{11117333955,
> 7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Patrick Dugan <pat### [at] usnetcomcorpcom> wrote:
: Well I was told (and tested to prove to myself) that the load and save are
: needed for partial renders to keep the continued render "correct." Without
: the load and save the render changes each time you continue and causes
: coloration/brightness changes to surfaces. With the save and load those
: things don't happen.
If this is so in 3.5 then it has changed since 3.1. The idea of that .rca
file is precisely to be able to continue interrupted renders.
AFAIK if you render half-image in one computer and then copy the pov files,
the partial image *and* the .rca-file to another computer and continue
rendering there (with +c), the result should be the same is if you had
rendered the whole image in one run.
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
>
> If this is so in 3.5 then it has changed since 3.1. The idea of that .rca
> file is precisely to be able to continue interrupted renders.
> AFAIK if you render half-image in one computer and then copy the pov files,
> the partial image *and* the .rca-file to another computer and continue
> rendering there (with +c), the result should be the same is if you had
> rendered the whole image in one run.
>
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 usual way to go is to use load_file and save_file plus 'always_sample
off' if you want to render in several parts, but i remember Gilles often
renders scenes in parts with just '+sr' and '+er' and without pretrace and
this apparently seems to work quite well too.
Christoph
--
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other
things on: http://www.schunter.etc.tu-bs.de/~chris/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Well my main issue is the continue.
After rendering x amount of lines, then stopping, exiting, restarting povray
and continuing the render it starts at the very top again even though I
specify +c.
I don't if radiosity has anything to do with that problem.
Why won't my render continue where it left off?
Why does it start at the top again even though it had previously completed
80 lines or so? I am using +c
"Christoph Hormann" <chr### [at] gmxde> wrote in message
news:3BC### [at] gmxde...
>
>
> Warp wrote:
> >
> > If this is so in 3.5 then it has changed since 3.1. The idea of that
.rca
> > file is precisely to be able to continue interrupted renders.
> > AFAIK if you render half-image in one computer and then copy the pov
files,
> > the partial image *and* the .rca-file to another computer and continue
> > rendering there (with +c), the result should be the same is if you had
> > rendered the whole image in one run.
> >
>
> 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 usual way to go is to use load_file and save_file plus 'always_sample
> off' if you want to render in several parts, but i remember Gilles often
> renders scenes in parts with just '+sr' and '+er' and without pretrace and
> this apparently seems to work quite well too.
>
> Christoph
>
> --
> Christoph Hormann <chr### [at] gmxde>
> IsoWood include, radiosity tutorial, TransSkin and other
> things on: http://www.schunter.etc.tu-bs.de/~chris/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3bcf27ef$1@news.povray.org> , "Patrick Dugan"
<pat### [at] usnetcomcorpcom> wrote:
> Why won't my render continue where it left off?
> Why does it start at the top again even though it had previously completed
> 80 lines or so? I am using +c
What output image format are you using?
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
BMP
"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3bcf29af@news.povray.org...
> In article <3bcf27ef$1@news.povray.org> , "Patrick Dugan"
> <pat### [at] usnetcomcorpcom> wrote:
>
> > Why won't my render continue where it left off?
> > Why does it start at the top again even though it had previously
completed
> > 80 lines or so? I am using +c
>
> What output image format are you using?
>
> Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
If I'm not crazy (because it doesn't work for me) then could the issue be
due to the radiosity block size? In other words lets say the initial block
size of the rendering using radiosity is ~100 lines (100x100) or so. (First
pass) Since my image is large (10240x7680) If during my render the actual
LINES rendered (after the "blocks" are done and its now line-by-line) are
lower than the initial block size, then Povray feels it has to start over or
at least start at an even initial block size amount and not the actual line
it was on?
___________
---------------------------------------
|
---------------------------------------
| | Initial (first pass) block size 100 x
--------------------------------------- Actual lines rendered when
stopped (81)
| |
| |
--------------
So in this case it starts at zero because it hadn't actually rendered at
least 100 lines
Just trying to understand how to make the continue actually work on this
large image.
"Patrick Dugan" <pat### [at] usnetcomcorpcom> wrote in message
news:3bcf467a$1@news.povray.org...
> BMP
>
> "Thorsten Froehlich" <tho### [at] trfde> wrote in message
> news:3bcf29af@news.povray.org...
> > In article <3bcf27ef$1@news.povray.org> , "Patrick Dugan"
> > <pat### [at] usnetcomcorpcom> wrote:
> >
> > > Why won't my render continue where it left off?
> > > Why does it start at the top again even though it had previously
> completed
> > > 80 lines or so? I am using +c
> >
> > What output image format are you using?
> >
> > Thorsten
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Patrick Dugan" <pat### [at] netinsnet> wrote in message
news:3bd22d77@news.povray.org...
> If I'm not crazy (because it doesn't work for me) then could the issue be
> due to the radiosity block size? In other words lets say the initial
block
> size of the rendering using radiosity is ~100 lines (100x100) or so.
(First
> pass) Since my image is large (10240x7680) If during my render the actual
> LINES rendered (after the "blocks" are done and its now line-by-line) are
> lower than the initial block size, then Povray feels it has to start over
or
> at least start at an even initial block size amount and not the actual
line
> it was on?
>
> So in this case it starts at zero because it hadn't actually rendered at
> least 100 lines
>
> Just trying to understand how to make the continue actually work on this
> large image.
I hadn't tried the same resolution, would take awhile for that. I didn't
see a restart back to the beginning with a smaller render, whether larger
percentages (blocks) were used or not. Have you checked this out against a
small resolution?
What I did see is the infamous coloration shift from a continued partial
render. Beta 6 BTW, and you stated this was about beta 5.
Haven't seen what system that was on, if it makes a difference such as
memory amount or something.
Bob H.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
