OK, what really dumb mistakes am I making?

#declare this_function =IC_Sphere(<0,0,0>, 1);

isosurface { function { this_function }
      contained_by { box { -2, 2} }
                        texture { pigment { color rgb <0.5, 0.5, 0> } }}

returns:

isosurface { function { this_function }


While

#declare this_function = IC_Sphere(<0,0,0>, 1);

isosurface { function { this_function(<0,0,0>,1) }
      contained_by { box { -2, 2} }
                        texture { pigment { color rgb <0.5, 0.5, 0> } }}

returns:

#declare this_function = IC_Sphere(<



So, leaving out the #declare statement entirely, and going it directly:

isosurface { function { IC_Sphere(<0,0,0>, 1)}
      contained_by { box { -2, 2} }
                        texture { pigment { color rgb <0.5, 0.5, 0> } }}


highlighting the first line of below:

function {
    f_sphere(x-Cx, y-Cy, z-Cz, _ICSG_Radius)

and returning the error message:





(I started with the IC_HF_Sphere function, but to make sure my problem
wasn't somehow with my image map, I simplified to the above, with the same
results.)

Normally, after several hours, I can fight my way through my obtuseness, but
not this time.

Please help.

Post a reply to this message

In article <web.3ef9165ee559a9c37196f5900@news.povray.org> , "Dave Matthews"
<mat### [at] dinecollegeedu> wrote:

> function { this_function(<0,0,0>,1) }

Maybe you should read the POV-Ray 3.5 manual how to use functions first?
This is no valid syntax at all!

    Thorsten

Post a reply to this message

Dave Matthews wrote:
> 
> OK, what really dumb mistakes am I making?
> 
> [...]

Like Thorsten said your syntax is simply not valid - none of the methods
you tried could be found anywhere in the docs or sample scenes of IsoCSG
or POV-Ray.  

The correct syntax can be found in any of the sample scenes coming with
the library.  It would be strongly advisable to also read the relevant
chapters of the POV-Ray docs.

Christoph

-- 
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 17 Jun. 2003 _____./\/^>_*_<^\/\.______

Post a reply to this message

Thorsten Froehlich wrote:
>In article <web.3ef9165ee559a9c37196f5900[at]news.povray.org> , "Dave Matthews"
><mat### [at] dinecollegeedu> wrote:
>
>> function { this_function(<0,0,0>,1) }
>
>Maybe you should read the POV-Ray 3.5 manual how to use functions first?

Believe me, I did, but I missed the only example that showed how to use a
#declare with a function, i.e.

"3.6.3.5 Combining isosurface functions"

>This is no valid syntax at all!

Obviously, else it would have worked, wouldn't it.
>
>    Thorsten
>

Anyway, after re-looking through the manual, yes, I realized that I needed
to use:

function { this_function(x,y,z) } and now it works.

Sorry for wasting your time.

Post a reply to this message

Christoph Hormann wrote:

>The correct syntax can be found in any of the sample scenes coming with
>the library.

You're right.  I don't know why I didn't look at the sample scenes.  Sorry.

Dave

Post a reply to this message

Dave Matthews <mat### [at] dinecollegeedu> wrote in message
news:web.3ef9b1fd7472fddc7196f5900@news.povray.org...
> Christoph Hormann wrote:
>
> >The correct syntax can be found in any of the sample scenes coming with
> >the library.
>
> You're right.  I don't know why I didn't look at the sample scenes.
Sorry.
>
> Dave
>

bleh! sometimes you just need to post here to get a fresh perspective on
mess-ups and clear your head.

Post a reply to this message

Ross Litscher wrote:

> bleh! sometimes you just need to post here to get a fresh perspective on
> mess-ups and clear your head.
> 
In which case, it definitely worked (but I'll try to avoid this method 
in the future.)

After getting the rather-more-politely-worded advice to RTFM, which also 
means
re-RTFM, I did re-RTFM, and found:

(In section 6.5.4.2 Functions in Isosurface)

"By default a function takes three parameters (x,y,z) and you do not 
have to explicitly specify the
parameter names when declaring it.  When using the identifier, the 
parameters must be specified."

which exactly answered my question, and I could swear was not there the 
first 50 or so times
I read the manual.

Someplace I learned the advice, which I must remember to follow:

(and I'm probably messing up the syntax and/or the logic, but I'm not 
going to ask about it!)

#while ((hell_frozen_over = 0) & (understanding < 1) )
read(manual)
evaluate(understanding)
evaluate(hell_frozen_over)
#end

which, I know, might include an extra evaluation of the status of hell, 
but that's usually something
good to know for other purposes, anyway.

Dave

Post a reply to this message