|
|
 | | Track names (was Re: To Tore Eriksson)
|
| (...) I'm curious Chris, in what sets was that the case ? And do these gray ones have those "negative" tapered ends, just like the old blue track had ? In lugnet.cad.dev, Larry Pieniazek writes: (...) Gimme a set number for "the wildwest miningish" (...) (25 years ago, 4-Oct-99, to lugnet.cad.dev)
| | | | | Re: Comprehensive meta-command list
|
| (...) Yes, they do. In the example above, the first meta-command, 0 TRANSLATE 20 0 0, would persist until the end of the file. (...) I think I know the answer to this question, but just to be sure: is the 0 INVERT meta-command transparent to (...) (25 years ago, 4-Oct-99, to lugnet.cad.dev)
| | | | | Re: CW/CCW, vertex sequence, co-planar, convex, (115kB)
|
| (...) I've been thinking the exact opposite -- mirroring should be a valid method for turning subfiles inside-out, and the software doesn't need to do anything special to deal with it (except to notice the inversion, and pass that info on to the (...) (25 years ago, 4-Oct-99, to lugnet.cad.dev)
| | | | | Re: Interpreting the proposed FACE meta-command
|
| (...) Why not recognize it all ways: 0 FACE ACW 0 FACE ANTICLOCKWISE 0 FACE CCW 0 FACE CLOCKWISE 0 FACE COUNTERCLOCKWISE 0 FACE CW 0 FACE DOUBLESIDED 0 FACE DS 0 FACE UNKNOWN This adds a bit to the parser, but not so much. The recommended standard (...) (25 years ago, 4-Oct-99, to lugnet.cad.dev)
| | | | | Re: Hidden surface removal, and vertex order in part/primitive DAT files
|
| (...) No (like Gary said). Two reasons: 1. The 0 FACE directive would be an operative switch, not a global setting. This is convenient, but it is also necessary in some cases. Most importantly, it would allow the 0 FACE meta-statement to appear (...) (25 years ago, 4-Oct-99, to lugnet.cad.dev)
|
|
