POV-Ray : Newsgroups : povray.unofficial.patches : MEGAPov error in mesh differences Server Time
2 Sep 2024 16:20:51 EDT (-0400)
  MEGAPov error in mesh differences (Message 3 to 12 of 12)  
<<< Previous 2 Messages Goto Initial 10 Messages
From: GrimDude
Subject: Re: MEGAPov error in mesh differences
Date: 14 Jan 2000 00:43:56
Message: <387eb79c@news.povray.org>
Nope.

I have used this technique since the introduction of the mesh object.

#declare Ball = mesh { smooth_triangle.... }

difference {
   object { Ball }
   object { box ... } }

This worked in the official release, in SuperPov, but not with MegaPov. :(

Actually, it still works. There are, however, extraneous objects showing up.

--
GrimDude
gri### [at] isonet


Post a reply to this message

From: omniVERSE
Subject: Re: MEGAPov error in mesh differences
Date: 14 Jan 2000 06:05:59
Message: <387f0317@news.povray.org>
What happens if you use 'inverse' for either the Ball or the box or the
difference itself.

Bob

"GrimDude" <gri### [at] netfreecom> wrote in message
news:387eb79c@news.povray.org...
> Nope.
>
> I have used this technique since the introduction of the mesh object.
>
> #declare Ball = mesh { smooth_triangle.... }
>
> difference {
>    object { Ball }
>    object { box ... } }
>
> This worked in the official release, in SuperPov, but not with MegaPov. :(
>
> Actually, it still works. There are, however, extraneous objects showing up.
>
> --
> GrimDude
> gri### [at] isonet
>
>


Post a reply to this message

From: Ron Parker
Subject: Re: MEGAPov error in mesh differences
Date: 14 Jan 2000 08:28:27
Message: <387f247b@news.povray.org>
On Thu, 13 Jan 2000 23:43:50 -0600, GrimDude wrote:
>Nope.
>
>I have used this technique since the introduction of the mesh object.
>
>#declare Ball = mesh { smooth_triangle.... }
>
>difference {
>   object { Ball }
>   object { box ... } }
>
>This worked in the official release, in SuperPov, but not with MegaPov. :(
>
>Actually, it still works. There are, however, extraneous objects showing up.

It shouldn't work in any of them, with the possible exception of MegaPOV.  
Parts of the box that are properly inside the ball should still show up.  
If it did work, it was a lucky coincidence.

-- 
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

From: Ron Parker
Subject: Re: MEGAPov error in mesh differences
Date: 14 Jan 2000 08:29:48
Message: <387f24cc@news.povray.org>
On 14 Jan 2000 08:28:27 -0500, Ron Parker wrote:
>On Thu, 13 Jan 2000 23:43:50 -0600, GrimDude wrote:
>>Nope.
>>
>>I have used this technique since the introduction of the mesh object.
>>
>>#declare Ball = mesh { smooth_triangle.... }
>>
>>difference {
>>   object { Ball }
>>   object { box ... } }
>>
>>This worked in the official release, in SuperPov, but not with MegaPov. :(
>>
>>Actually, it still works. There are, however, extraneous objects showing up.
>
>It shouldn't work in any of them, with the possible exception of MegaPOV.  
>Parts of the box that are properly inside the ball should still show up.  
>If it did work, it was a lucky coincidence.

er... s/inside/outside/, if you would.

-- 
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

From: Spider
Subject: Re: MEGAPov error in mesh differences
Date: 14 Jan 2000 15:59:53
Message: <387F5B24.7EA4BE13@bahnhof.se>
Ron Parker wrote:
> 
> er... s/inside/outside/, if you would.

No no no.. Compile it and make a binary statemachine out of the regexp, apply to
the. . . . .

(I've been around a comp.sci. stud for far too long... he got me hooked :p )
 
-- 
//Spider    --  [ spider@bahnhof.se ]-[ http://darkmere.wanfear.com/ ]
And the devil in black dress watches over
    My guardian angel walks away
Life is short and love is always over in the morning
    Black wind come carry me far away
            --"Sisters of Mercy" -- "Temple Of Love"


Post a reply to this message

From: GrimDude
Subject: Re: MEGAPov error in mesh differences
Date: 15 Jan 2000 01:52:05
Message: <38801915@news.povray.org>
Well, so far I've come across more then 2000 lucky coincidences. :)

I worked alright. Everytime too. I know, I was warned my Ron Parker (and
Chris Colefax, too, who both recommended clipping years ago I think), that
it wasn't proper coding and shouldn't work. But, it did, so I continued the
practice. The worst part is, after I got all of the independant portions
coded I merged it with the overall code, so now I have a real mess!

Ah, well! Clipping (w/wo inverse) fixes it.

--
GrimDude
gri### [at] isonet


Post a reply to this message

From: GrimDude
Subject: Re: MEGAPov error in mesh differences
Date: 15 Jan 2000 02:01:12
Message: <38801b38@news.povray.org>
The same extraneous portion shows up, but with the disected section rather
then the
host.

--
GrimDude
gri### [at] isonet
omniVERSE <inv### [at] aolcom> wrote in message
news:387f0317@news.povray.org...
> What happens if you use 'inverse' for either the Ball or the box or the
> difference itself.
>
> Bob
>
> "GrimDude" <gri### [at] netfreecom> wrote in message
> news:387eb79c@news.povray.org...
> > Nope.
> >
> > I have used this technique since the introduction of the mesh object.
> >
> > #declare Ball = mesh { smooth_triangle.... }
> >
> > difference {
> >    object { Ball }
> >    object { box ... } }
> >
> > This worked in the official release, in SuperPov, but not with MegaPov.
:(
> >
> > Actually, it still works. There are, however, extraneous objects showing
up.
> >
> > --
> > GrimDude
> > gri### [at] isonet
> >
> >
>
>


Post a reply to this message

From: omniVERSE
Subject: Re: MEGAPov error in mesh differences
Date: 15 Jan 2000 04:14:11
Message: <38803a63@news.povray.org>
Is there a texture (pigment at least) on the differencing object (box in this
case)?  Reason I ask is that I had a similar sounding situation a couple years
ago.

Bob

"GrimDude" <gri### [at] netfreecom> wrote in message
news:38801b38@news.povray.org...
> The same extraneous portion shows up, but with the disected section rather
> then the
> host.
>


Post a reply to this message

From: omniVERSE
Subject: Re: MEGAPov error in mesh differences
Date: 15 Jan 2000 04:17:39
Message: <38803b33@news.povray.org>
I was wondering what might happen depending on texture location in the script.
For example inside the 'difference' only, or in both objects only.
If you got it fixed no need to try that.  I came across something like this once
and that seemed to be the problem.

Bob

"GrimDude" <gri### [at] netfreecom> wrote in message
news:38801915@news.povray.org...
> Well, so far I've come across more then 2000 lucky coincidences. :)
>
> I worked alright. Everytime too. I know, I was warned my Ron Parker (and
> Chris Colefax, too, who both recommended clipping years ago I think), that
> it wasn't proper coding and shouldn't work. But, it did, so I continued the
> practice. The worst part is, after I got all of the independant portions
> coded I merged it with the overall code, so now I have a real mess!
>
> Ah, well! Clipping (w/wo inverse) fixes it.
>
> --
> GrimDude
> gri### [at] isonet
>
>


Post a reply to this message

From: GrimDude
Subject: Re: MEGAPov error in mesh differences
Date: 15 Jan 2000 14:57:27
Message: <3880d127@news.povray.org>
No, I don't apply textures, etc., until after I have the section defined. :)
--
GrimDude
gri### [at] isonet
omniVERSE <inv### [at] aolcom> wrote in message
news:38803a63@news.povray.org...
> Is there a texture (pigment at least) on the differencing object (box in
this
> case)?  Reason I ask is that I had a similar sounding situation a couple
years
> ago.
>
> Bob
>
> "GrimDude" <gri### [at] netfreecom> wrote in message
> news:38801b38@news.povray.org...
> > The same extraneous portion shows up, but with the disected section
rather
> > then the
> > host.
> >
>
>
>


Post a reply to this message

<<< Previous 2 Messages Goto Initial 10 Messages

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.