 | | 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 (...) (22 years ago, 6-Nov-02, to lugnet.cad)
|
| |
| | Re: Overlapping polygons - how bad is it?
|
|
(...) I don't really see any problem as long as the polygins are of the same color. Some may complain that improper use of overlaps make transparent parts look wierd but I don't think that that's a significant enough problem to prevent using this (...) (22 years ago, 6-Nov-02, to lugnet.cad)
|
| |
| | Re: Overlapping polygons - how bad is it?
|
|
(...) IMHO it is bad if the part can exist in transparent. Alpha-transparency makes any overlapping visible. Otherwise it is harmless. If you have no other solution and the part clearly exists in transparent color(s), then "needs work" in the part (...) (22 years ago, 6-Nov-02, to lugnet.cad)
|
| |
| | Re: Overlapping polygons - how bad is it?
|
|
(...) That's the cool thing about LDraw, any part can exist in transparent. -Orion (22 years ago, 7-Nov-02, to lugnet.cad)
|
| |
| | Re: Overlapping polygons - how bad is it?
|
|
(...) Can't you create missing primitives to solve the problem? /Niels (22 years ago, 7-Nov-02, to lugnet.cad)
|
| |
| | Re: Overlapping polygons - how bad is it?
|
|
(...) 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 (...) (22 years ago, 10-Nov-02, to lugnet.cad)
|
