POV-Ray : Newsgroups : povray.bugreports : Crash in POV-Ray 3.5 Windows (number overflow??) Server Time
14 May 2024 11:01:59 EDT (-0400)
  Crash in POV-Ray 3.5 Windows (number overflow??) (Message 1 to 2 of 2)  
From: Andrew Coppin
Subject: Crash in POV-Ray 3.5 Windows (number overflow??)
Date: 7 May 2003 21:31:58
Message: <3eb9b38e@news.povray.org>
(Confirmed by Ken Tyler)

The following short scene causes POV-Ray to give me an "internal error"
warning. I would imagine the problem is the exp() function, but surely a
simple high-valued result shouldn't crash the whole of POV-Ray... I would
have expected to just get some kind of "number overflow" message instead...

POV-Ray 3.5.icl.win32
Windows XP (Home), Mobile AMD Athlon +1400 CPU, 256MB RAM, etc.

--- Scene ---
global_settings
{
  noise_generator 3
}

camera
{
  location <0, 0, -500>
  direction z
  look_at <0, 0, 0>
}

light_source {<0, 0, -500>, colour rgb 1}

#declare TBase =
texture
{
  pigment {colour rgb 0.5}
  finish {ambient 0 specular 0.5}
}

#declare TDrip =
texture
{
  pigment {colour rgb <0.95, 0.82, 0.71>}
  finish {ambient 0 specular 0.2}
}

#declare RND = seed(31415);

object
{
  blob
  {
    #declare Angle = 0;
    #while (Angle<360)
      sphere {<sin(radians(Angle))*exp(Angle),
cos(radians(Angle))*exp(Angle), Angle>, 10, strength 7}

      #declare Angle = Angle + 5;
    #end
    #undef Angle

    threshold 1
  }
  texture {TBase}
}
--- End Scene ---


Post a reply to this message

From: Chris Cason
Subject: Re: Crash in POV-Ray 3.5 Windows (number overflow??)
Date: 10 Aug 2003 20:44:03
Message: <3f36e6d3$1@news.povray.org>
This is fixed in 3.51.

--- Chris


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.