Here's a file that I created and rendered on the Mac using MegaPOV 5a. When
I run it on the PC under either 5.0 or 5.0a, it crashes. The rendering
actually starts, then crashes right at line 20, when the isosurface is
called.
Any thoughts?
d.

camera {
 perspective
 location <0.0, 10.0, -10>
 sky<0.0, 1.0, 0.0>
 look_at <0.0, 0.0, 0.0>
}
light_source {
 <0.0, 100, -100>
 rgb <1.0, 1.0, 1.0>
}
// Persistence of Vision Ray Tracer Scene Description File

#include "colors.inc"
#version unofficial MegaPov 0.4;
#default { texture { pigment { color rgb < 1, 0, 0 > } finish { ambient
0.4 } } }
#declare P0 = 0.25;     //period X
#declare P1 = 0.25;     //period Z
#declare P2 = 0.8;     //shape parameter 1 (x-z)
#declare P3 = 0.125; //amplitude
#declare P4 = 0.8;     //shape parameter 2 (y)
isosurface {
        normal on
 function { "mesh1" ,<P0,P1,P2,P3,P4> }
 accuracy  0.001
 threshold  0.02
 contained_by { box { <-10.0, -10.0, -10.0>, <10.0, 10.0, 10.0> } }
 eval
 texture {
 pigment {
  function {
  sqrt(x*x*0.1 + y*y*0.1 + z*z*0.1)
   }
  color_map {
  [ 0.000 rgbft <1.0, 0.5, 1.0, 0.0, 0.0> ]
  [ 1.000 rgbft <1.0, 0.2, 0.2, 0.0, 0.0> ] }  }  } }
--
dhm### [at] mediaonenet
http://www.casdn.neu.edu/~dmiller

Post a reply to this message

Attachments:
Download 'iso2.pov.txt' (1 KB)

It's the normal on statement. remove and it will not crash on the PC. Anyone
know why?
d.


--
dhm### [at] mediaonenet
http://www.casdn.neu.edu/~dmiller
D. H. Miller <dhm### [at] mediaonenet> wrote in message
news:395fa4d6$1@news.povray.org...
> Here's a file that I created and rendered on the Mac using MegaPOV 5a.
When
> I run it on the PC under either 5.0 or 5.0a, it crashes. The rendering
> actually starts, then crashes right at line 20, when the isosurface is
> called.
> Any thoughts?
> d.
>
> camera {
>  perspective
>  location <0.0, 10.0, -10>
>  sky<0.0, 1.0, 0.0>
>  look_at <0.0, 0.0, 0.0>
> }
> light_source {
>  <0.0, 100, -100>
>  rgb <1.0, 1.0, 1.0>
> }
> // Persistence of Vision Ray Tracer Scene Description File
>
> #include "colors.inc"
> #version unofficial MegaPov 0.4;
> #default { texture { pigment { color rgb < 1, 0, 0 > } finish { ambient
> 0.4 } } }
> #declare P0 = 0.25;     file://period X
> #declare P1 = 0.25;     file://period Z
> #declare P2 = 0.8;     file://shape parameter 1 (x-z)
> #declare P3 = 0.125; file://amplitude
> #declare P4 = 0.8;     file://shape parameter 2 (y)
> isosurface {
>         normal on
>  function { "mesh1" ,<P0,P1,P2,P3,P4> }
>  accuracy  0.001
>  threshold  0.02
>  contained_by { box { <-10.0, -10.0, -10.0>, <10.0, 10.0, 10.0> } }
>  eval
>  texture {
>  pigment {
>   function {
>   sqrt(x*x*0.1 + y*y*0.1 + z*z*0.1)
>    }
>   color_map {
>   [ 0.000 rgbft <1.0, 0.5, 1.0, 0.0, 0.0> ]
>   [ 1.000 rgbft <1.0, 0.2, 0.2, 0.0, 0.0> ] }  }  } }
> --
> dhm### [at] mediaonenet
> http://www.casdn.neu.edu/~dmiller
>
>
>

Post a reply to this message

"D. H. Miller" <dhm### [at] mediaonenet> wrote in message
news:395fc8b1$1@news.povray.org...
| It's the normal on statement. remove and it will not crash on the PC. Anyone
| know why?

Maybe because 'normal on' only goes into the 'radiosity' statement far as I
know.  And I looked it up in the html doc to make sure and it's not a part of
the possible things for 'isosurface'.
I meant to ask before why you were using #version unofficial MegaPov 0.4
instead of 0.5?  Just curious.

Bob

Post a reply to this message

In article <395ff75b@news.povray.org>, "Bob Hughes" 
<per### [at] aolcom?subject=PoV-News:> wrote:

> Maybe because 'normal on' only goes into the 'radiosity' statement 
> far as I know.  And I looked it up in the html doc to make sure and 
> it's not a part of the possible things for 'isosurface'.

It also goes in isosurfaces, isoblobs, and parametrics. It should 
specify a more accurate normal calculation, but doesn't work well with 
atan2 or noise3d. I think it also has problems with built in functions, 
which this object uses.

It is documented in the MegaPOV manual, just not where you expect. Look 
in the isoblob section, under "Technical notes on the function normal 
patch:".

-- 
Christopher James Huff - Personal e-mail: chr### [at] maccom
TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
Personal Web page: http://homepage.mac.com/chrishuff/
TAG Web page: http://tag.povray.org/

Post a reply to this message

The normal on is part of the template that you get inside the MegaPOV Mac
patch. I didn't actually add it; I better ask Mr. Smellenbergh about that.
Yet it runs fine with that statement in the  script on the Mac, but crashes
the PC..
No reason for the version # error; it's also just something that was in my
own template.

Also, thought the accuracy would do it. I too can run 10 frames in a 1 - 10
job. But when I try to run 300 frames, I get an out of memory error; cannot
allocate 2097152 bytes for precompute... Wonder why it doesn't happen when I
only run 10?
Without the precompute statement, it crashes instantly on the first frame...
Thanks for your help on this.
D.


--
dhm### [at] mediaonenet
http://www.casdn.neu.edu/~dmiller
Bob Hughes <per### [at] aolcom?subject=PoV-News:> wrote in message
news:395ff75b@news.povray.org...
> "D. H. Miller" <dhm### [at] mediaonenet> wrote in message
> news:395fc8b1$1@news.povray.org...
> | It's the normal on statement. remove and it will not crash on the PC.
Anyone
> | know why?
>
> Maybe because 'normal on' only goes into the 'radiosity' statement far as
I
> know.  And I looked it up in the html doc to make sure and it's not a part
of
> the possible things for 'isosurface'.
> I meant to ask before why you were using #version unofficial MegaPov 0.4
> instead of 0.5?  Just curious.
>
> Bob
>
>
>

Post a reply to this message

In article <395ffe09@news.povray.org> , "D. H. Miller" 
<dhm### [at] mediaonenet> wrote:

> Yet it runs fine with that statement in the  script on the Mac, but crashes
> the PC..

I presume on Windows it crashes with a segment fault?  As Macs don't have
memory protection, this won't happen - it will just destroy some data in
memory, but as long as the data is not used nothing else happens.


      Thorsten

Post a reply to this message

Just for the heck of it, try moving 'normal on' below the function and see if
it still crashes.

~Samuel

eg:

isosurface {
 function { "mesh1" ,<P0,P1,P2,P3,P4> }
         normal on
accuracy  0.001
 threshold  0.02
 contained_by { box { <-10.0, -10.0, -10.0>, <10.0, 10.0, 10.0> } }
 eval
 texture {
 pigment {
  function {
  sqrt(x*x*0.1 + y*y*0.1 + z*z*0.1)
   }
  color_map {
  [ 0.000 rgbft <1.0, 0.5, 1.0, 0.0, 0.0> ]
  [ 1.000 rgbft <1.0, 0.2, 0.2, 0.0, 0.0> ] }  }  } }

Post a reply to this message