So, as usual, I made a _minor_ modification to a working file and suddenly all
Hell broke loose.

At the end of the file I added a text object, and everything was fine except for
the orientation.

So I added two simple vector declarations in my camera section,
and then some calculations on those vectors just before the text object.

Suddenly, in the untouched MIDDLE of the file, POV-Ray's telling me that I'm
using > version 3.5 and I need a semicolon.   Great - but it's highlighting a
line of code that doesn't have anything to do with that (the #end of a for loop
in the #declare AllStrands union)

Huh?

So I comment out the vectors declarations, move them to the bottom of the scene
file, run the scene in 3.8-alpha, 3.71-beta-whatever, 3.7 official, ... same
thing, only now it's complaining about a perfectly formed #declare identifier =
value; a few lines down that's worked perfectly for dozens of test renders.
[though 3.7 official complained about a trailing comma in my sor{} defined by a
loop]

(#declare Ymax = 0;)
                  ^ LOOK, you confounded Parser!  There's your precious
semicolon!

I'm perplexed, confused, and possibly cursed.

It was late, I had a long, sweltering day, and the eyelids were drooping, so I
decided not to stay up until midnight hunting phantoms.

Perhaps someone else could just run the code to confirm this bizarre behaviour
and move some lines (at the end near the text block) around to see if the error
notification changes.  #declare Loc and LA were what I added at the top and then
moved to the bottom.

Pay no attention to the unattributed stolen texture and hdr lighting code behind
the curtain...

Post a reply to this message

Attachments:
Download 'bellhenge.pov.txt' (12 KB)