> Alain <aze### [at] qwertyorg> wrote:

>>> I'm not sure if this is the right place or not but recently I wanted to start
>>> doing 3d circuits and do some animation so when I do tutorials for the
>>> paranormal group I work with, I can show where everything goes and what it'll
>>> look like and stuff, but each time I render I get the following errors in pov
>>> ray.
>>>
>>> File: C:\Documents and Settings\user\My
>>> Documents\POV-Ray\v3.6\include\glass_old.inc Line: 18
>>> Parse Warning: Due to changes in version 3.1, you must add interior {I_Glass} to
>>> all objects calling glass_old.inc textures and finishes...
>>>
>>> My renders look like this...I assume I'm doing something wrong, but need to fix
>>> this glass error thing and I got no idea what to do.
>>>
>>> <img src="http://www.freewebs.com/evps/problems.JPG">
>>>
>>>
>> That's not an error but a warning.
>>
>> It tells you that glass objects should have an interior{} block where
>> you set the object's ior (index of refraction).
>>
>> If you don't set an ior, your transparent objects will usualy lack
>> "substence" and apears to flat.
>>
>>
>>
>> Alain
> 
> where exactly in line 18 am I supposed to put the iglass thingy...keep in mind
> this is my first time and it's pretty much greek to me. There isn't like a
> simpler way to handle these huh?

The line 18 mentionned is the 18th line from the file glass_old.inc. You 
don't need to change it. That warning is unconditionaly issued 
everytimes that include is used. Take it as a reminder.

The glass_old.inc files provide the finishes in a section, and some 
interiors in another. Textures are distinct from the interior. The 
texture describe the surface of the object. The interior affect the 
beviour if the interior of the object, how the light refract and fade 
inside the object, and if there is any media there.

You don't need to change anything at all in the file, exept, maybe, the 
actual line where the warning is issued. You can comment out that single 
line, add a "//" in front of it.

In the scene, not the .inc file, in the declaration of the object. AFTER 
the texture block last "}", add the following:

interior{ior 1.5}

or the proposed "interior {I_Glass}" that uses a value declared in that 
include file.

to get a material with about the refraction strenght of normal glass.

> 
> 
> File: C:\Documents and Settings\user\My
> Documents\POV-Ray\v3.6\include\glass_old.inc  Line: 18
> Parse Warning:  Due to changes in version 3.1, you must add interior {I_Glass}
> to all objects calling
> glass_old.inc textures and finishes...

> File: C:\Documents and Settings\user\My
> Documents\eagle\lm555\timer-555-based.pov  Line: 214
> Parse Warning: Should have at least 2 objects in csg.
> File: C:\Documents and Settings\user\My
> Documents\eagle\lm555\timer-555-based.pov  Line: 218
> Parse Warning: Should have at least 2 objects in csg.
This means that you have an union, difference or intersection with only 
one component. The warning is a reminder. It can point you to a possible 
error, maybe you forgot some elements, maybe you removed them for any 
reason.

All the preceding are only warnings. The parsing does continue and the 
image is traced.

The following is an actual error and causes the parsing to abort, and no 
image get traced.

> File: C:\Documents and Settings\user\My Documents\POV-Ray\v3.6\include\cap.inc
> Line: 30
> File Context (5 lines):
>  #local cap = object {superellipsoid{<1, 1>scale<diam,diam*0.25,diam>rotate
> <-90,-7.5,0>translate<0,diam*1.1,0>} }
>  #local txt = text{handelgo_font
> Parse Error: Expected 'ttf', undeclared identifier 'handelgo_font' found instead
> 
> 
> 

The first parameter of a text object MUST be "ttf"
Your text object should be declares this way:
#local Txt = text{ttf "handelgo_font.ttf"....

The way it's writen here, the parser expect to find a previously 
declared variable with the name "handelgo_font". There are no variable 
by that name.

Raster fonts, *.fon, are not supported.

Take the habit of ALWAYS starting the name of ANY user defined variable 
with an upper case letter. ALL builtin variables and keywords always 
start with a lower case letter, and some more may eventualy get added.



Alain

Post a reply to this message