 | | Re: Hidden surface removal, and vertex order in part/primitive DAT files
|
|
Michael Lachmann: (...) I think we agreed to use 0 CW and 0 CCW lines in the beginning of the files to indicate (C)CW compliancy, but you should have a look at what Steve actually has written in his parts. (...) It would be very nice if you (...) (25 years ago, 1-Oct-99, to lugnet.cad.dev)
|
| |
| | Re: Hidden surface removal, and vertex order in part/primitive DAT files
|
|
You mentioned that some parts have a "0 CW-Compliant" tag. Could we do something to make this a standard? Because than I could read this tag in MLCad and make the drawing faster!!!!! Tell me what you think! Mike (...) John VanZwieten wrote in (...) (25 years ago, 1-Oct-99, to lugnet.cad.dev)
|
| |
| | Re: CW/CCW, vertex sequence, co-planar, convex, (115kB)
|
|
(...) MAX2DAT isn't really meant to be a comprehensive part authoring tool... it's easy to build simple objects (like a 2x2 tile or 1x1 round plate) directly in LEdit with primatives... but objects like complex technic pieces, wheels, etc often have (...) (25 years ago, 1-Oct-99, to lugnet.cad.dev)
|
| |
| | Re: Hidden surface removal, and vertex order in part/primitive DAT files
|
|
Gary Williams wrote in message ... (...) Okay, I made a bad assumption there, since a group of polygons may terminate flush against another polygon, without touching its edges. But still I think a performance improvement could be realized by using (...) (25 years ago, 30-Sep-99, to lugnet.cad.dev)
|
| |
| | Re: Hidden surface removal, and vertex order in part/primitive DAT files
|
|
Jean-Pierre PARIS wrote in message <37F3B871.74AE196F@w...doo.fr>... (...) My algorithm doesn't require the vertices to exactly match; I was intending to pass one ray per polygon through the dat object, not an arbitrarily large number. And only if (...) (25 years ago, 30-Sep-99, to lugnet.cad.dev)
|
