MathGroup Archive 2011

[Date Index] [Thread Index] [Author Index]

Search the Archive

How to avoid partially visible hidden edges

  • To: mathgroup at smc.vnet.net
  • Subject: [mg121163] How to avoid partially visible hidden edges
  • From: Yves Klett <yves.klett at googlemail.com>
  • Date: Thu, 1 Sep 2011 06:04:11 -0400 (EDT)
  • Delivered-to: l-mathgroup@mail-archive0.wolfram.com

Hi,

consider these two nearly overlapping polygons which :

Graphics3D[{Polygon[{{-0.3141433158711031`,-29.791675066388876`,-20.`},{0.`,-11.79441655357383`,-20.`},{0.`,0.`,0.`},{-0.3141433158711031`,-17.997258512815044`,0.`}}],Polygon[{{-0.3141433158711031`,-17.997258512815044`,0.`},{0.`,0.`,0.`},{0.`,11.79441655357383`,-20.`},{-0.3141433158711031`,-6.202841959241214`,-20.`}}]}]

In Mathematica 8.01 you can see a part of the hidden polygon edge
shining through. With the legacy Version 5 Graphics engine these edges
were properly hidden (but you get all of the former awkwardness and no
opacity etc.).

So, I'd like to get a proper rendering with the current engine. The
BSPTree rendering method works better and in fact solves the problem for
this simple case, but for larger number of polygons I still get these
hidden edge artefacts.

Any tips are welcome.

Regards,
Yves




  • Prev by Date: Re: FullSimplify and Coefficient
  • Next by Date: Re: Difference table via DifferenceDelta[ ]. Why do I need two Table[ ] calls?
  • Previous by thread: Re: FullSimplify and Coefficient
  • Next by thread: Re: Difference table via DifferenceDelta[ ]. Why do I need two Table[ ] calls?