![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
First, I'm not familear with isosurface stuff (I haven't done any work on it
myself... well, except for preliminary work on UV mapping which has since
been scrapped).
Using the following for the isosurface function fixes the 'not enough
argumens' problem:
function {FUNC1(x,y+cos(TH(x,y,z)*7)*0.3,z)}
Somebody apparantly changed the implementation of isosurfaces while we
weren't looking and those default parameters aren't there anymore. maybe
that's the problem?
About that crash... I got it to crash once... but that happened before I
replaced the #declare TH=...
But can't get it to crash again now that I'm running the debugger.
Strange...
-Nathan
Ken <tyl### [at] pacbell net> wrote...
> The above returns the following warning:
>
> #declare TH= function{"TH"}
>
> isosurface {
> function {FUNC1(x,y+cos(TH* <----ERROR
>
> F:\Program Files\POV-Ray for Windows v3.1\megapov\demos\Multipatch NPov\
> Isosurface_isoblob\Iso demo\torus2.pov:15: error:
>
> The function 'TH' needs arguments. Should be TH(...)
>
> Returned from renderer (non-zero return value)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Nathan Kopp wrote:
>
> First, I'm not familear with isosurface stuff (I haven't done any work on it
> myself...
I haven't either. Right now I am simply rendering thumbnails of all of
the demos to help you track down bugs and to get a feel for what the
patch has to offer. I have been avoiding this for too long and it's
time I start to get up to speed on some of these new features.
> About that crash... I got it to crash once... but that happened before I
> replaced the #declare TH=...
>
> But can't get it to crash again now that I'm running the debugger.
> Strange...
With a little patience I was able to get it to stop crashing long enough
to return the following error message:
#declare TH=
function{"FUNC1"}
isosurface {
function {FUNC1(x,y+cos(TH <----ERROR
torus2.pov:16: error: cannot load function.
Returned from renderer (non-zero return value)
Obviously it is a user created problem but the program seems a little
too sensitive to it.
--
Ken Tyler - 1200+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Ken <tyl### [at] pacbell net> wrote...
>
> I haven't either. Right now I am simply rendering thumbnails of all of
> the demos to help you track down bugs and to get a feel for what the
> patch has to offer. I have been avoiding this for too long and it's
> time I start to get up to speed on some of these new features.
If you haven't noticed, the demos for my features are usually somewhat
lacking. If anyone wants to make up some demos for me to include, I'd be
happy. :-)
> Obviously it is a user created problem but the program seems a little
> too sensitive to it.
I've had it crash under two situations:
1) an error causes parsing to stop
2) the scene finishes rendering and I see a bunch of 'tried to free NULL
pointer' errors and then it crashes
-Nathan
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Your'e not, 'cause I think so too.
> >Well, yeah, that's one of my goals. Also, Nathan seems to be better able
> >to actually create a shipping product from a bunch of cool patches, whereas
> >I just sit around and tell y'all how cool the next one's gonna be without
> >ever taking the time to write the documentation and put it online.
>
> I think you've done a brilliant job anyway :)
> I'm quite certain that I'm not the only one with this opinion.
>
--
Samuel Benge
E-Mail: STB### [at] aol com
Visit the still unfinished isosurface tutorial: http://members.aol.com/stbenge
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Sat, 11 Dec 1999 00:44:03 -0500, "Nathan Kopp" <Nat### [at] Kopp com>
wrote:
>Somebody apparantly changed the implementation of isosurfaces while we
>weren't looking and those default parameters aren't there anymore. maybe
>that's the problem?
Why's everyone looking at me? :)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Ron Parker <par### [at] fwi com> wrote ...
> On Sat, 11 Dec 1999 00:44:03 -0500, "Nathan Kopp" <Nat### [at] Kopp com>
> wrote:
>
> >Somebody apparantly changed the implementation of isosurfaces while we
> >weren't looking and those default parameters aren't there anymore. maybe
> >that's the problem?
>
> Why's everyone looking at me? :)
>
Don't worry. It wasn't you.
-Nathan
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
An old Chief Engineer of mine once defined an engineer as someone who sat on
the bed and kept telling his girl friend how great it was going to be ...
--
Jim
Check out my web site http://www.kressworks.com/
It'll blow your mind (politically), stimulate your senses (artistically)
and provide scientific insights that boggle the mind!
Ron Parker <ron### [at] povray org> wrote in message
news:38510831@news.povray.org...
> On Fri, 10 Dec 1999 05:51:03 -0800, Ken wrote:
> >
> >Ron Parker wrote:
> >
> >> I'm chasing Mick's bug at the moment, and I will continue to do so
until
> >> I catch it, but I am considering doing so, yes.
> >
> > Well I personaly have no problem with this as long as it means it frees
> >up more of your time to work on the official release of POV-Ray v 3.5.
>
> Well, yeah, that's one of my goals. Also, Nathan seems to be better able
> to actually create a shipping product from a bunch of cool patches,
whereas
> I just sit around and tell y'all how cool the next one's gonna be without
> ever taking the time to write the documentation and put it online.
>
> --
> These are my opinions. I do NOT speak for the POV-Team.
> The superpatch: http://www2.fwi.com/~parkerr/superpatch/
> My other stuff: http://www2.fwi.com/~parkerr/traces.html
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |