Hi all.

I just got (for the second time) a strange error message.  Not strange in
and of itself, but because of where and how it occured.  I have serious
doubts as to whether it can be reproduced (it's happened at different times
each time) but it's happened twice on a simulation/animation I'm working on.
Here's the error:

  File: C:\My Documents\POVRay\Simulation\gel.pov  Line: 254
  #

  #local NLength = SpringD * VDist(C1, C0) <----ERROR

  Parse Error: Cannot open macro file C:\Program Files\POV-Ray for Windows
v3.5\INCLUDE\math.inc.
  File: C:\My Documents\POVRay\Simulation\gel.pov  Line: 254
  Warning: Check that the file is in a directory specifed with a +L switch
  or 'Library_Path=' .INI item. Standard include files are in the
  include directory or folder. Please read your documentation carefully.

Now, if this were an include line, I could understand.  But it's not, and at
that point in the file, macros from math.inc have been called several times.
I *think* it is the same line in the file, but it is a different place in
the animation sequence.  This one occured at frame 8, the previous time was
more like 20 or so.  I doubt I'll be able to whittle the scene file down
from 370 lines, especially since RL is about to catch up with me, but if
you'd like me to post it I will.  I'm going to continue working with the
file, so if I come up with any pattern, I'll post it here.

Sorry for not having a scene to work with, but maybe the error message will
help.

POV-Ray 3.5 beta 4 for Windows, Athlon 700, 192 MB RAM, Win98SE

Michael

P.S. I still think 3.5 is a great step forward, and of course POV-Ray is
hands down the best easily available raytracer around.

Post a reply to this message

"Redbeard \(MDJohnson\)" <red### [at] wvadelphianet> wrote:
: Now, if this were an include line, I could understand.  But it's not, and at
: that point in the file, macros from math.inc have been called several times.

  A macro call is parsed by opening the file where the macro is located (if
it's not the current file), seeking it to the position where the macro starts
and reading the file.
  Of course I don't know why #inluding math.inc works but then calling a macro
in it causes a reading failure...

  (And yes, it *IS* slow to parse macros like this, but you have to live with
that right now.)

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

Post a reply to this message