The following scene file gives a black screen.  IMHO it should give a
green screen. This bug/feature caused me considerable headaches 'till I
figured it out.  Consider for example the difference when the distance
is 1e-6.

  fog {
    distance 0
//    distance 1e-6
    color rgb<0.3, 0.5, 0.2>
  }

Post a reply to this message

On Tue, 06 Nov 2001 08:41:43 -0500, "Greg M. Johnson"
<"gregj56590[:-0]"@aol.com> wrote:

> The following scene file gives a black screen.  IMHO it should give a
> green screen.

The behaviour is probably undefined becouse of fog formula from 6.9.3 chapter. 

ABX
--
#declare _=function(a,b,x){((a^2)+(b^2))^.5-x}#default {pigment{color rgb 1}}
union{plane{y,-3}plane{-x,-3}finish{reflection 1 ambient 0}}isosurface{ //ABX
function{_(x-2,y,1)|_((x+y)*.7,z,.1)|_((x+y+2)*.7,z,.1)|_(x/2+y*.8+1.5,z,.1)}
contained_by{box{<0,-3,-.1>,<3,0,.1>}}translate z*15finish{ambient 1}}//POV35

Post a reply to this message

"Greg M. Johnson" wrote:
> 
> The following scene file gives a black screen.  IMHO it should give a
> green screen. This bug/feature caused me considerable headaches 'till I
> figured it out.  Consider for example the difference when the distance
> is 1e-6.

Philosophical objection?

It does not behave any differently than it did in POV-Ray v3.1g. This
means it is not a bug and this message does not belong in this group.

If you want to discuss feature behavior you might try one of the
other groups on this news server such as povray.general.

Let's keep focused on bug reports, please.

-- 
Ken Tyler - POV-Ray Technical Assistance Group

Post a reply to this message

On Tue, 06 Nov 2001 06:27:12 -0800, Ken <tyl### [at] pacbellnet> wrote:

>Let's keep focused on bug reports, please.

Could it be treated as bug report if I say there is no simple small example for
mesh2 in scene files ? Only within advanced balcony.

ABX
--
#declare _=function(a,b,x){((a^2)+(b^2))^.5-x}#default {pigment{color rgb 1}}
union{plane{y,-3}plane{-x,-3}finish{reflection 1 ambient 0}}isosurface{ //ABX
function{_(x-2,y,1)|_((x+y)*.7,z,.1)|_((x+y+2)*.7,z,.1)|_(x/2+y*.8+1.5,z,.1)}
contained_by{box{<0,-3,-.1>,<3,0,.1>}}translate z*15finish{ambient 1}}//POV35

Post a reply to this message

> On Tue, 06 Nov 2001 08:41:43 -0500, "Greg M. Johnson"
> <"gregj56590[:-0]"@aol.com> wrote:
>
> > The following scene file gives a black screen.  IMHO it should give a
> > green screen.
>
> The behaviour is probably undefined becouse of fog formula from 6.9.3 chapter.

This bug-carry-over-from 3.1g could be fixed by changing:

PIXEL_COLOR = exp(-d/D) * OBJECT_COLOR + (1-exp(-d/D)) * FOG_COLOR

to

PIXEL_COLOR = exp(-d/(D+GGG)) * OBJECT_COLOR + (1-exp(-d/(D+GGG))) * FOG_COLOR

Where GGG= an infitesimal, just bigger than the smallest number pov can handle

Post a reply to this message

On Tue, 06 Nov 2001 10:39:40 -0500, "Greg M. Johnson"
<"gregj56590[:-0]"@aol.com> wrote:

> This bug-carry-over-from 3.1g could be fixed by changing:
> PIXEL_COLOR = exp(-d/D) * OBJECT_COLOR + (1-exp(-d/D)) * FOG_COLOR
> to
> PIXEL_COLOR = exp(-d/(D+GGG)) * OBJECT_COLOR + (1-exp(-d/(D+GGG))) * FOG_COLOR
> Where GGG= an infitesimal, just bigger than the smallest number pov can handle

Balancing between floating point accuracy and division by zero is rather not
very best thing. "The smallest number pov can handle" depends on platform.
Morover why this addition should be done for all values (even large integers)?
It is rather bug in parser which allows even "distance -1".

ABX
--
#declare _=function(a,b,x){((a^2)+(b^2))^.5-x}#default {pigment{color rgb 1}}
union{plane{y,-3}plane{-x,-3}finish{reflection 1 ambient 0}}isosurface{ //ABX
function{_(x-2,y,1)|_((x+y)*.7,z,.1)|_((x+y+2)*.7,z,.1)|_(x/2+y*.8+1.5,z,.1)}
contained_by{box{<0,-3,-.1>,<3,0,.1>}}translate z*15finish{ambient 1}}//POV35

Post a reply to this message

> 
> Could it be treated as bug report if I say there is no simple small example for
> mesh2 in scene files ? Only within advanced balcony.
> 

Hmm, certainly not a bug, but relevant for this group anyway.  I think the
main reason is that mesh2 is particularly useful for large meshes which
would be too large for the scene file collection.  I had quite a lot of
trouble getting the cloth mesh in balcony down to the current 300k and
this is still quite a lot.

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

On Tue, 06 Nov 2001 17:24:45 +0100, Christoph Hormann <chr### [at] gmxde>
wrote:

> Hmm, certainly not a bug, but relevant for this group anyway.  I think the
> main reason is that mesh2 is particularly useful for large meshes which
> would be too large for the scene file collection.

But there could be comparision of mesh with two faces - one with mesh{} and the
same with mesh2{}. Bezier patch is supposed to be generated with external
programs but there is sample for it within scenes/objects.

> I had quite a lot of
> trouble getting the cloth mesh in balcony down to the current 300k and
> this is still quite a lot.

You can remove some space by replacing "0." with "." but I think you have
considered this. I don't know how many signs are there but perhaps you can also
change negative to positive and positive to negative in vertices and normals and
use scale -1.

I think it could be also good idea to make universal macros to generate
face_indices and uv-vectors for grids like yours within standard include files.

ABX
--
#declare _=function(a,b,x){((a^2)+(b^2))^.5-x}#default {pigment{color rgb 1}}
union{plane{y,-3}plane{-x,-3}finish{reflection 1 ambient 0}}isosurface{ //ABX
function{_(x-2,y,1)|_((x+y)*.7,z,.1)|_((x+y+2)*.7,z,.1)|_(x/2+y*.8+1.5,z,.1)}
contained_by{box{<0,-3,-.1>,<3,0,.1>}}translate z*15finish{ambient 1}}//POV35

Post a reply to this message

"Ken" wrote:
> It does not behave any differently than it did in
> POV-Ray v3.1g. This means it is not a bug and this
> message does not belong in this group.

While I agree that this message of Greg's is perhaps more of a feature
request than a bug report (since a distance of 0 may be undefined for good
reasons), I would like to point out that even if something works the same
way in POV-Ray 3.1 it can still be a bug. POV-Ray 3.1 is not entirely
bug-free.

There have been lots of bugs reported here that also were present in POV-Ray
3.1, and AFAIK no Team member has ever complained about that, but on the
contrary they have tried to fix them.

Rune
--
3D images and anims, include files, tutorials and more:
Rune's World:    http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users:   http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk

Post a reply to this message

> 
> But there could be comparision of mesh with two faces - one with mesh{} and the
> same with mesh2{}. Bezier patch is supposed to be generated with external
> programs but there is sample for it within scenes/objects.

Although the scene file collection is to some extend 'fixed' this might by
a good idea, i will see what i can do.

> You can remove some space by replacing "0." with "." but I think you have
> considered this. I don't know how many signs are there but perhaps you can also
> change negative to positive and positive to negative in vertices and normals and
> use scale -1.

Yes, removing the 0's would reduce size although compression (for the
installation package) will work quite well on them.

> 
> I think it could be also good idea to make universal macros to generate
> face_indices and uv-vectors for grids like yours within standard include files.
> 

I think Ingo has already made such macros, i don't know if they are
already well tested though.

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