![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Warp
Subject: Seems that the tesselation patch died before even being born
Date: 16 Jan 2001 11:41:49
Message: <3a6479cc@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
I can't find the bug. No-one else can either (I have consulted with Ron,
Nathan and Chris H).
There's a persistent bug (I wrote about it some time ago) and I just can't
find what's wrong with the code. I don't think that it's typing mistake
or anything, but I have the feeling that some povray functions might work
a bit differently than I expect and that's what's causing the problem.
Finding the problem would require more knowledge about povray and/or a lot
of testing.
The patch would be more or less ready if there wasn't that bug.
So I'm sorry. I can't make it.
--
char*i="b[7FK@`3NB6>B:b3O6>:B:b3O6><`3:;8:6f733:>::b?7B>:>^B>C73;S1";
main(_,c,m){for(m=32;c=*i++-49;c&m?puts(""):m)for(_=(
c/4)&7;putchar(m),_--?m:(_=(1<<(c&3))-1,(m^=3)&3););} /*- Warp -*/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Wlodzimierz ABX Skiba
Subject: Re: Seems that the tesselation patch died before even being born
Date: 16 Jan 2001 11:49:40
Message: <3a647ba4@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Warp wrote in message <3a6479cc@news.povray.org>...
> So I'm sorry. I can't make it.
what a pity!
ABX
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Vahur Krouverk
Subject: Re: Seems that the tesselation patch died before even being born
Date: 16 Jan 2001 12:10:02
Message: <3A648119.70823724@aetec.ee>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Warp wrote:
>
> I can't find the bug. No-one else can either (I have consulted with Ron,
> Nathan and Chris H).
> There's a persistent bug (I wrote about it some time ago) and I just can't
> find what's wrong with the code. I don't think that it's typing mistake
> or anything, but I have the feeling that some povray functions might work
> a bit differently than I expect and that's what's causing the problem.
> Finding the problem would require more knowledge about povray and/or a lot
> of testing.
> The patch would be more or less ready if there wasn't that bug.
>
> So I'm sorry. I can't make it.
>
Oh, man, don't quit like this! This tesselation is quite promising (I
think about implementing displacement shaders in POV-Ray and tesselation
of POV-Ray primitives will become handy in this case, as it is
relatively easy to displace meshes).
Is this bug related to the translation of primitive (i.e. is this
described in message
Subject: Re: Tesselation and mesh data extraction patches
Date: 19 Dec 2000 04:14:55 -0500)?
Are the triangles teared off from others or are additional triangles
generated? Lighting in these pictures does not allow to see "under the
crack" and I can't make it out, which is the case.
Hmm, You make me really curious, can you make source available (or mail
me)? I feel challenge here...
Or alternatively:
You work in university? Here is tip: offer this bug hunting to some
student and promise to give assessment (is it right word?) or other
bonus, if he/she can find it. Next "Linus Torvalds" can spot it for
sure!
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Christoph Hormann
Subject: Re: Seems that the tesselation patch died before even being born
Date: 16 Jan 2001 12:22:31
Message: <3A648358.7C22C85F@gmx.de>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Warp wrote:
>
> I can't find the bug. No-one else can either (I have consulted with Ron,
> Nathan and Chris H).
> There's a persistent bug (I wrote about it some time ago) and I just can't
> find what's wrong with the code. I don't think that it's typing mistake
> or anything, but I have the feeling that some povray functions might work
> a bit differently than I expect and that's what's causing the problem.
> Finding the problem would require more knowledge about povray and/or a lot
> of testing.
> The patch would be more or less ready if there wasn't that bug.
>
> So I'm sorry. I can't make it.
>
Oh, please don't give up.
Anyway, do you mind giving some more detailed description about the
problem. Not that i think i can find a bug that you, Ron, Nathan and
Chris Huff have not found during long search, but i would be interested
where the problem lies.
Christoph
--
Christoph Hormann <chr### [at] gmx de>
IsoWood include, radiosity tutorial, TransSkin and other
things on: http://www.schunter.etc.tu-bs.de/~chris/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Warp
Subject: Re: Seems that the tesselation patch died before even being born
Date: 16 Jan 2001 12:24:59
Message: <3a6483ea@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Vahur Krouverk <vah### [at] aetec ee> wrote:
: Is this bug related to the translation of primitive
It's the same bug, but it's not related to the translation of the primitive.
It seems that it's just related to its location (that is, surfaces at
certain locations are not tesselated correctly for some reason).
Perhaps I should just make the patch public and let it be. Perhaps someone
would come up with a solution.
--
char*i="b[7FK@`3NB6>B:b3O6>:B:b3O6><`3:;8:6f733:>::b?7B>:>^B>C73;S1";
main(_,c,m){for(m=32;c=*i++-49;c&m?puts(""):m)for(_=(
c/4)&7;putchar(m),_--?m:(_=(1<<(c&3))-1,(m^=3)&3););} /*- Warp -*/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Warp
Subject: Re: Seems that the tesselation patch died before even being born
Date: 16 Jan 2001 13:03:54
Message: <3a648d0a@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Christoph Hormann <chr### [at] gmx de> wrote:
: Anyway, do you mind giving some more detailed description about the
: problem. Not that i think i can find a bug that you, Ron, Nathan and
: Chris Huff have not found during long search, but i would be interested
: where the problem lies.
Well, Ron and Nathan are quite busy with pov3.5 so they don't have too
much time to look at my code. However, Nathan already found a serious bug
earlier.
(This bug might be similar to the one fixed by Nathan because the
effects are similar, but I just can't find the reason.)
--
char*i="b[7FK@`3NB6>B:b3O6>:B:b3O6><`3:;8:6f733:>::b?7B>:>^B>C73;S1";
main(_,c,m){for(m=32;c=*i++-49;c&m?puts(""):m)for(_=(
c/4)&7;putchar(m),_--?m:(_=(1<<(c&3))-1,(m^=3)&3););} /*- Warp -*/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Rick [Kitty5]
Subject: Re: Seems that the tesselation patch died before even being born
Date: 16 Jan 2001 14:18:22
Message: <3a649e7e$1@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> The patch would be more or less ready if there wasn't that bug.
then publish and be dammed. ( a few bugs never stopped anybody else!)
> So I'm sorry. I can't make it.
just publish with an open request for bug hunters
--
Rick
POV-Ray News & Resources - http://povray.co.uk
Kitty5 WebDesign - http://kitty5.com
Hi-Impact web site design & database driven e-commerce
TEL : +44 (01625) 266358 - FAX : +44 (01625) 611913 - ICQ : 15776037
PGP Public Key
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x231E1CEA
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) |
In article <3A648358.7C22C85F@gmx.de>, Christoph Hormann
<chr### [at] gmx de> wrote:
> Anyway, do you mind giving some more detailed description about the
> problem.
It basically seems to be that triangles don't always end up where they
are expected...every once in a while, in a very reproduceable but
unpredictable manner, one (or more?) vertex of a triangle will end up
where it shouldn't be, leaving a hole in the mesh. At least, that is
what I could figure out...(A similar problem killed my warpable mesh
patch.)
I have been planning to dive into the main mesh functions to figure out
how they work, but I don't know much about the way that code works and
the code isn't very self explanatory...
--
Christopher James Huff
Personal: chr### [at] mac com, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tag povray org, http://tag.povray.org/
<><
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) |
In article <3a6479cc@news.povray.org>, Warp <war### [at] tag povray org>
wrote:
> The patch would be more or less ready if there wasn't that bug.
I'd release it anyway...it isn't useless, and someone else may see
something. At least people would be able to work on object-specific
tesselation, patches that will depend on the tesselation patch, etc...
--
Christopher James Huff
Personal: chr### [at] mac com, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tag povray org, http://tag.povray.org/
<><
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: David Fontaine
Subject: Re: Seems that the tesselation patch died before even being born
Date: 17 Jan 2001 00:56:21
Message: <3A6532CB.EE8078F3@faricy.net>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Warp wrote:
> I can't find the bug. No-one else can either (I have consulted with Ron,
> Nathan and Chris H).
> There's a persistent bug (I wrote about it some time ago) and I just can't
> find what's wrong with the code. I don't think that it's typing mistake
> or anything, but I have the feeling that some povray functions might work
> a bit differently than I expect and that's what's causing the problem.
> Finding the problem would require more knowledge about povray and/or a lot
> of testing.
> The patch would be more or less ready if there wasn't that bug.
>
> So I'm sorry. I can't make it.
Aagh. Debugging is the bain of your existence no doubt. Knowing your programming
skill no doubt if you can't find it it is quite a problem indeed. There's so
much complicated inner workings that can elude you, I remember a long time ago
trying to make some program with pointers to structures that read the structure
from a binary file, got all screwed up by byte alignment and I had to break the
fread()s down into the individual elements once my brother found the problem.
--
David Fontaine <dav### [at] faricy net> ICQ 55354965
My raytracing gallery: http://davidf.faricy.net/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |