Subject:
|
Re: Overlapping polygons - how bad is it?
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Sun, 10 Nov 2002 19:45:52 GMT
|
Viewed:
|
1725 times
|
| |
|
|
In lugnet.cad, Tore Eriksson wrote:
> If, for example, I can use a n-4disc primitive but not a n-4ndis close to
> it, I may want to let the polygon that touches the disc overlap a bit so
> that there won't be any bleeding when the part is converted by L3P.
>
> How "bad" is that overlap (if disc and polygon share the same color, of
> course)? When does it present a problem (bigger than making the disc a polygon)?
I don't consider it all that bad.
Although I recognize that some (perhaps many) rendering methods will
render overlaid transparent areas as darker than non-overlaid areas.
But studs drawn in the normal way (stud.dat primitives plopped on the
top of a box5.dat primitive) will do the same thing.
In this case of discs (or ndis, or cyli's, or whatever) adjoining
'non-curved' areas, maybe there could be a meta-statement to identify
this situation?
Steve
|
|
Message is in Reply To:
 | | Overlapping polygons - how bad is it?
|
| If, for example, I can use a n-4disc primitive but not a n-4ndis close to it, I may want to let the polygon that touches the disc overlap a bit so that there won't be any bleeding when the part is converted by L3P. How "bad" is that overlap (if disc (...) (24 years ago, 6-Nov-02, to lugnet.cad)
|
6 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
