WinPOV 3.5 b 10

In 6.11.11.2.7 about low_error_bound there is sentence "(...) The solution to
this is the mosaic preview: it goes over the image one or more times beforehand,
calculating radiosity values." But it is not clearly described is this the same
mosaic preview available with +SP and +EP or is this mosaic preview described in
6.11.11.2.13 in pretrace section ? Or in case of radiosity old mosaic preview is
the same as pretrace ? It's not clearly explained IMO.

ABX

Post a reply to this message

Skiba wrote: 

> "(...) The solution to
> this is the mosaic preview: it goes over the image one or more times
> beforehand, calculating radiosity values."

"(...) The solution to
this is the mosaic preview, controled by pretrace: it goes over the image 
one or more times beforehand, calculating radiosity values."

with pretrace linked to its own section.

Ingo

Post a reply to this message

ingo <ing### [at] homenl> wrote:
: "(...) The solution to
: this is the mosaic preview, controled by pretrace: it goes over the image 
: one or more times beforehand, calculating radiosity values."

  Note, however, that if you use +SP and +EP command line options, they'll
override the pretrace settings.
  I don't know if this is intentional or something left by mistake.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

On 4 Feb 2002 07:38:30 -0500, Warp <war### [at] tagpovrayorg> wrote:
> Note, however, that if you use +SP and +EP command line options, they'll
> override the pretrace settings.
> I don't know if this is intentional or something left by mistake.

It is described in '2.6.2  Photons, Dispersion and Improved Radiosity' however
it is not clear what should have priority:

  Instead of using the INI options "Preview_Start_Size" and "Preview_End_Size"
  to control the radiosity pre-trace gathering step, use the keywords
  pretrace_start and pretrace_end within the radiosity block inside
  global_settings.

BTW: I think it is enough important to be placed in main radiosity chapter
instead of "What's new in 3.5".

ABX

Post a reply to this message

Skiba <abx### [at] babilonorg>  wrote:

> It is described in '2.6.2  Photons, Dispersion and Improved Radiosity' however
> it is not clear what should have priority:

As the mosaic preview is a _preview_ feature it doesn't really make sense
when used with radiosity.  One should not use the mosaic preview and
radiosity.  If one does, it may work or won't.  This has never been
different before.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

On Tue, 02 Jul 2002 10:00:15 +0200, "Thorsten Froehlich" <tho### [at] trfde>
wrote:
> As the mosaic preview is a _preview_ feature it doesn't really make sense
> when used with radiosity.  One should not use the mosaic preview and
> radiosity.  If one does, it may work or won't.  This has never been
> different before.

But radiosity worked differently. Previously it required ingerention as ini
switch. Now it is on just with radiosity{} block. Usually users have scenes
controlled with switches like:
  #declare Use_Focal     = on;
  #declare Use_Radiosity = on;
When something is specified in script (like focal) and interfere with ini
switch (like AA) then script has priority. When radiosity is invoked it
automatically turn on pretrace. There is neither warning that it could
interfere with ini setting nor good note in documentation.

ABX

Post a reply to this message

Warp <war### [at] tagpovrayorg> wrote:
>   Note, however, that if you use +SP and +EP command line options, they'll
> override the pretrace settings.
>   I don't know if this is intentional or something left by mistake.

> -- 
> #macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
> [1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
> -1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

  Uh... I don't know if I'm suffering from some lapsus or what, but I can't
remember writing this. I remember *reading* this previously, but not writing
it myself.
  This is weird, but I have the strong feeling that this was not written by
me, even though it has my signature, and the text indentation is the same
which I use. Am I getting old or what?
  (On the other hand, I never use the expression "they'll". And I usually
write command-line parameters in lowercase in my posts.)

  Am I becoming crazy or what?

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

Warp wrote:

> Am I getting old or what?
> Am I becoming crazy or what?

Yes to both :)

-- 
Ken Tyler

Post a reply to this message

Ken <tyl### [at] pacbellnet> wrote:
>> Am I getting old or what?
>> Am I becoming crazy or what?

> Yes to both :)

  I hoped that as I get older I would get wiser, but you can't get
everything, seemingly.

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

> As the mosaic preview is a _preview_ feature it doesn't really make sense
> when used with radiosity.

I disagree.

  1: I may need radiosity in a preview, e.g. when I want to test wether
     radiosity suffices to shed enough light on some part of a scene.
  2: I may not mind the 33% overhead, e.g. when I render somebody
     else's scene and I want to know quickly what it is and only
     eventually obtain the final image.
  3: The doc (5.2.2.2.4) reads:
       Future versions of POV-Ray will include some system
       of temporary files or buffers which will eliminatethese
       inefficiencies and limitations.
     As soon as that is established, mosaic preview will be as quick as
     line-by-line preview, but more informative. At that time everybody
     will mix radiosity and mosaic, so why disallow now?

Mark Weyer

Post a reply to this message