 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Massimo Valentini wrote:
>"Ken" ha scritto
>:
>: Mesh bug report -
>:
>: A mesh object (w/inside_vector used) evaluates properly only when it is a
>: top level object in a CSG operation. The behavior is incorrect when it is a
>: second level object. This bug has been confirmed.
>:
>: POV-Ray for Windows version 3.5.icl.win32, Win 98, Athlon 950, 256meg sdram.
>:
>: Ken Tyler
>:
>
>I Xposted this reply to both p.bugreports and p.programming
>and set the follow-up to p.programming.
>
>
>I would say this is NOT a bug. Well, I'm not entitled to say what's
>a bug and what's not, but I think the behaviour is easily explained.
>
>When you render this scene, a warning is issued saying:
>
>"Patch objects not allowed in intersection"
>
>and given the fact that mesh objects have no inside, what you obtain
>is a difference when the second object is a box, and an intersection
>when it is a mesh. In other words you obtain the same image as with:
>
>//////////////////
>camera { location<-2,3,-5> look_at y*.5 }
>
>light_source { <-5,5,-5> 1 }
>
>default { pigment {red 1} finish { ambient .4 diffuse .6 }}
>
>difference
>{
> box{<-1,-1,-1>,<1,1,1>}
> box{<-.75,-.75,-1.1>,<.75,.75,1.1> pigment{rgb 1}}
> translate x*-1.2
>}
>
>intersection
>{
> box{<-1,-1,-1>,<1,1,1> pigment{rgb 1}}
> box {<-.75,-.75,-1.1>,<.75,.75,1.1>}
> translate x*1.2
>}
>
>intersection
>{
> box { <-1,-1,-1>,<1,1,1> }
> box {<-.75,-.75,-1.1>,<.75,.75,1.1>}
> translate y*2
>}
>//////////////////////
>
If you could confirm that a mesh completely encloses an inner area could you
then find a way to declare it as a solid object? Perhaps use a mesh to
shape an isosurface?
--normdoering
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <web.3dd02a8c6e9e93e4cbb77c320@news.povray.org>,
"normdoering" <nor### [at] yahoo com> wrote:
> If you could confirm that a mesh completely encloses an inner area could you
> then find a way to declare it as a solid object? Perhaps use a mesh to
> shape an isosurface?
Do you bother to read the material you quote? That thread is about the
inside_vector feature, which lets a closed mesh be used as a solid
object. It has nothing to do with isosurfaces, they wouldn't be of any
use for this. The poster you replied to seems to have been confused, and
apparently didn't know about that addition. I can't even find the post
you replied to, though...it doesn't seem to exist except for on the web
interface.
--
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Christopher James Huff" ha scritto
:
: Do you bother to read the material you quote? That thread is about the
: inside_vector feature, which lets a closed mesh be used as a solid
: object. It has nothing to do with isosurfaces, they wouldn't be of any
: use for this. The poster you replied to seems to have been confused, and
: apparently didn't know about that addition.
Well, I've been confused by the doc, in particular,
<QUOTE>
6.5.6 Constructive Solid Geometry
...
6.5.6.1 Inside and Outside
....
You should note that triangles and triangle-based shapes cannot be used
as solid objects in CSG since they have no well defined inside and outside.
</QUOTE>
and by the warning povray issues with the bug-report scene.
In fact, the point is that Invert_Mesh(OBJECT *) is an empty function,
so it's not possible to distinguish between intersection and
difference (that internally is an intersection among the first object
and the "inverse" of every other object), when the mesh object is not
the first.
:I can't even find the post
: you replied to, though...it doesn't seem to exist except for on the web
: interface.
:
I don't see that message too. I replied to the last message I see in
povray.bugreports, and cross posted to povray.programming.
Hope that's the correct way to do.
Massimo
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <chr### [at] netplexaussieorg> ,
Christopher James Huff <chr### [at] maccom> wrote:
> I can't even find the post
> you replied to, though...it doesn't seem to exist except for on the web
> interface.
This is because the message he is quoting was apparently cross-posted to
povray.bugreports. Apparently be the newsserver moderation is handled on a
per-message and not per-group basis. Thus if not approved by the moderator
for povray.bugreports the message will not appear on the newsserver at all.
I suppose this has to do with the newsserver tracking messages by their
message ID, which would be the same (as it is cross-posted).
Probably I will have to adjust the web news interface scripts to behave the
same as the newsserver when I find the time (it happens very infrequently,
so it isn't top priority).
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
normdoering <nor### [at] yahoocom> wrote:
> Perhaps use a mesh to shape an isosurface?
You know... you seem to have some odd obsession about isosurfaces... ;)
Isosurfaces are not the answer for everything.
--
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3dd0aeac@news.povray.org>,
"Massimo Valentini" <six### [at] inwindit> wrote:
> Well, I've been confused by the doc, in particular,
>
> <QUOTE>
> 6.5.6 Constructive Solid Geometry
> 6.5.6.1 Inside and Outside
> and by the warning povray issues with the bug-report scene.
Looks like some documentation needs to be updated, the inside_vector
feature is supposed to let meshes be used like any other solid object.
> In fact, the point is that Invert_Mesh(OBJECT *) is an empty function,
> so it's not possible to distinguish between intersection and
> difference (that internally is an intersection among the first object
> and the "inverse" of every other object), when the mesh object is not
> the first.
That would be a definite bug.
> I don't see that message too. I replied to the last message I see in
> povray.bugreports, and cross posted to povray.programming.
>
> Hope that's the correct way to do.
It apparently isn't, only bug reports go to *.bugreports, and your
crossposted reply got deleted. It probably would work if you modified
the reply to only go to *.programming.
--
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
in news:chr### [at] netplexaussieorg Christopher
James Huff wrote:
>> <QUOTE>
>> 6.5.6 Constructive Solid Geometry
>> 6.5.6.1 Inside and Outside
>> and by the warning povray issues with the bug-report scene.
>
> Looks like some documentation needs to be updated, the inside_vector
> feature is supposed to let meshes be used like any other solid object.
>
I'll do so,
Ingo
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
