|
|
 | | high-res version of 3960 (4x4 radar dish) [DAT]
|
| This file uses these two subfiles: "(URL) not posting this to the Parts Tracker 'cuz someone else (Paul Easter?) has already been working on a high-res version. But, in the meantime, here's an interim version you can use. Thanks, Franklin 0 Space (...) (23 years ago, 31-Mar-02, to lugnet.cad.dat.parts)
| | | | | Re: Two questions on primitives
|
| (...) One other thing,[1] the primitives which are most commonly used with the INVERTNEXT flag/statement are the *-*cyli.dat files. All of these files (the regular cylinder primitives) have BFC'ed versions posted on the Parts Tracker. -- Steve 1) (...) (23 years ago, 31-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives, lugnet.cad.dev)
| | | | | Re: Two questions on primitives
|
| Thanks guys. You cleared up my only question with BFC -Orion (23 years ago, 30-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives, lugnet.cad.dev)
| | | | | Re: Two questions on primitives
|
| (...) You've got it. When existing part files are made BFC-compliant, they have to be checked through completely. The main changes are fixing polygon wrapping and adding INVERTNEXT statements. Until a file is labeled BFC-compliant, renderers (...) (23 years ago, 30-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives, lugnet.cad.dev)
| | | | | Re: Two questions on primitives
|
| (...) Is this a real issue? Parts can't be truly BFC compliant until all of their subparts are BFC compliant. So yes, you'll have to insert those INVERTNEXT commands. But the part wasn't BFC compliant before, and this is just another part of (...) (23 years ago, 29-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives, lugnet.cad.dev)
|
|
