Currently doing what I hope will be my final, final render.  :-)  As
suspected, I seem to have made the scene render more slowly than it did in
October.  I hope I've enhanced it in the process.

I've heard a couple people mention that they had dropped out of the
competition, but I hope we will have more participants in the extended
competition.  If not, well perhaps I've got a chance.  ;-)

Good luck to everyone!

-- 
Jeremy
www.beantoad.com

news:41e1ce6a@news.povray.org...
> Currently doing what I hope will be my final, final render.  :-)  As
> suspected, I seem to have made the scene render more slowly than it did in
> October.  I hope I've enhanced it in the process.
>
> I've heard a couple people mention that they had dropped out of the
> competition, but I hope we will have more participants in the extended
> competition.  If not, well perhaps I've got a chance.  ;-)
>
> Good luck to everyone!
>
> -- 

Hi
I joined The Comp since deadline was extended.
My final render is currently tracing ...about 10 days to run (6 hours for
the upper 80% of the image!!)
Well... luck has few to do here, just hope no more hardware failure.
My CPU/motherboard/RAM fried once during my WIP so no more, please, Gods of
raytracing.
(Any advice if sacrificing a primitive -and which one- could be helpfull?)
Knowing some who are competiting I expect a postcard size Zazzle poster. (I
guess the dual opteron will come with a spanish keyboard :p)

Regards

Marc

 > ...
> guess the dual opteron will come with a spanish keyboard :p)

Unfair :-((((

> Regards
> 
> Marc

news:41e560b0@news.povray.org...

>  > ...
> > guess the dual opteron will come with a spanish keyboard :p)
>
> Unfair :-((((
>
I do think it's fair :-)

Marc

"Marc Jacquier" <jac### [at] wanadoofr> wrote in message 
news:41e239bb$1@news.povray.org...
>
> Well... luck has few to do here, just hope no more hardware failure.
> My CPU/motherboard/RAM fried once during my WIP so no more, please, Gods 
> of
> raytracing.


Windows XP decided to install an update last night (I forgot to turn that 
feature off), so I got rebooted at 3:00am, about 75% complete.  I just 
discovered this a few minutes ago.  Arrgghh.

But, now I see a couple of things that I want to nitpick over, so I probably 
would have restarted anyway.

-- 
Jeremy
www.beantoad.com

> Windows XP decided to install an update last night (I forgot to turn that
> feature off), so I got rebooted at 3:00am, about 75% complete.  I just
> discovered this a few minutes ago.  Arrgghh.


+C ? Unless you're using radiosity...

 - Slime
 [ http://www.slimeland.com/ ]

Slime <fak### [at] emailaddress> wrote:
> +C ? Unless you're using radiosity...

  At least in the past using +C with radiosity was not a problem.
  If it's a problem currently, it's a bug, imho.

-- 
plane{-x+y,-1pigment{bozo color_map{[0rgb x][1rgb x+y]}turbulence 1}}
sphere{0,2pigment{rgbt 1}interior{media{emission 1density{spherical
density_map{[0rgb 0][.5rgb<1,.5>][1rgb 1]}turbulence.9}}}scale
<1,1,3>hollow}text{ttf"timrom""Warp".1,0translate<-1,-.1,2>}//  - Warp -

news:41e7a1ab@news.povray.org...
> Slime <fak### [at] emailaddress> wrote:
> > +C ? Unless you're using radiosity...
>
>   At least in the past using +C with radiosity was not a problem.
>   If it's a problem currently, it's a bug, imho.
>
Here I've not any issue with +C and radiosity

Marc

"Warp" <war### [at] tagpovrayorg> wrote in message 
news:41e7a1ab@news.povray.org...
> Slime <fak### [at] emailaddress> wrote:
>> +C ? Unless you're using radiosity...
>
>  At least in the past using +C with radiosity was not a problem.
>  If it's a problem currently, it's a bug, imho.
>

I did a +C and it looks ok (even with radiosity), but it happened to crash 
right where there is a natural horizontal line in the image, so any problems 
wouldn't likely be noticed anyway.  It's only a 4-day render, and there are 
a couple things that I'm still not 100% happy with, so it will likely be 
re-rendered regardless.

But...  If I recall correctly, using +C with radiosity was a problem in 3.5. 
Is that what you mean?  If there was a way around it (short of saving the 
radiosity data before doing the render), I was never aware of it.  You 
basically end-up with a line where the continuation took place.  At least, 
that's what I recall.

-- 
Jeremy
www.beantoad.com

> >  At least in the past using +C with radiosity was not a problem.
> >  If it's a problem currently, it's a bug, imho.
>
> But...  If I recall correctly, using +C with radiosity was a problem in
3.5.
> Is that what you mean?  If there was a way around it (short of saving the
> radiosity data before doing the render), I was never aware of it.  You
> basically end-up with a line where the continuation took place.  At least,
> that's what I recall.


Yeah, that's what I was referring to. Without a save_file and load_file, I
would be surprised if the horizontal line could be avoided, since the second
time through, POV-Ray can't have the radiosity data from the first time
through.

Of course, it *works*, in that the image continues to render from where it
left off, but the results can be bad.

 - Slime
 [ http://www.slimeland.com/ ]