 |
|
|
|
|
|
| |
| |
|
|
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>
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
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>
|
|
|
| |
| |
|
|
Christoph Hormann <chr### [at] gmxde> 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
|
|
| |
| |
|
|
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>
|
|
|
| |
| |
|
|
> 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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3A648358.7C22C85F@gmx.de>, Christoph Hormann
<chr### [at] gmxde> 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] maccom, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tagpovrayorg, http://tag.povray.org/
<><
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3a6479cc@news.povray.org>, Warp <war### [at] tagpovrayorg>
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] maccom, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tagpovrayorg, http://tag.povray.org/
<><
Post a reply to this message
|
|
| |
| |
|
|
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>
|
|
|
| |
| |
|
|
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] faricynet> ICQ 55354965
My raytracing gallery: http://davidf.faricy.net/
Post a reply to this message
|
|
| |
| |
|
|
From: Jim Kress
Subject: Re: Seems that the tesselation patch died before even being born
Date: 17 Jan 2001 01:25:19
Message: <3a653acf$1@news.povray.org>
|
|
|
| |
| |
|
|
Did you try the tessellation method for which I sent you a link? It even
included C++ source code and was free (GPL)
Jim
"Warp" <war### [at] tagpovrayorg> wrote in message
news:3a6479cc@news.povray.org...
> 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
|
|
| |
| |
|
|
From: Warp
Subject: Re: Seems that the tesselation patch died before even being born
Date: 17 Jan 2001 05:09:08
Message: <3a656f44@news.povray.org>
|
|
|
| |
| |
|
|
Chris Huff <chr### [at] maccom> wrote:
: 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...
Ok.
I could release it right now, with the current syntax, that is, the
tesselate-block is a separate object, or I could see if it's easy to
put the tesselate-block inside the mesh-block and make the proper
modifications (that would really add flexibility to it).
Which one do you people prefer?
I doubt that anyone can use the patch for anything serious, though.
Although the bug happens rather rarely, it still happens too often. You
only need an object that is large enough, and you'll get holes here and
there...
--
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
|
|
| |
| |
|
|
From: Warp
Subject: Re: Seems that the tesselation patch died before even being born
Date: 17 Jan 2001 05:10:19
Message: <3a656f8a@news.povray.org>
|
|
|
| |
| |
|
|
Jim Kress <kre### [at] kressworkscom> wrote:
: Did you try the tessellation method for which I sent you a link? It even
: included C++ source code and was free (GPL)
Nope, sorry.
I don't think that the problem is in the tesselation algorithm, but
somewhere else, that's why I haven't looked into other algorithms.
--
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
>
> Chris Huff <chr### [at] maccom> wrote:
> : 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...
>
> Ok.
> I could release it right now, with the current syntax, that is, the
> tesselate-block is a separate object, or I could see if it's easy to
> put the tesselate-block inside the mesh-block and make the proper
> modifications (that would really add flexibility to it).
> Which one do you people prefer?
>
<fool speaking>
Release it now, just like it is as a separate object,
so I can try to add it to my pov-source and try to find where is that bug...
> I doubt that anyone can use the patch for anything serious, though.
> Although the bug happens rather rarely, it still happens too often. You
> only need an object that is large enough, and you'll get holes here and
> there...
>
<More fool to come>
If you can also provide two sample scenes, one without any bug and
one in which the bug manifest itself (holding a big sign and asking
for recognition of bug's rights...)
<no more fool (?)>
Whatever your choice for the syntax, please release this patch...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
