 | | 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)
|
| |
| | Re: Why aren't the technic gear teeth primitives?
|
|
(...) If they were designed properly, the tooth profiles will be different between the 8t, 24t, etc. gears. The tooth profile of a gear follows an involute curve, which means the profile is the involute of a base circle slightly smaller than the (...) (23 years ago, 29-Mar-02, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Why aren't the technic gear teeth primitives?
|
|
(...) editing (...) The teeth on the small 8 tooth gear are slightly different from the larger ones(Though in the file they are pretty much drawn as trapezoidal boxes). But on the two beveled gears they apear practicly identical as far as I can (...) (23 years ago, 29-Mar-02, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Two questions on primitives
|
|
(...) I'm concerned that if we release those primitives that can be used as both inside and outside surfaces as BFC complient, we'll have to go back to all the other pieces that use them to insert the INVERTNEXT directive (where appropriate). (...) (23 years ago, 29-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Why aren't the technic gear teeth primitives?
|
|
(...) Are the teeth the same between different parts? If they are different, it doesn't make much sense to have primitives for each one. Even if the teeth are different, it would be possible to make subfiles for the teeth. This could make sense for (...) (23 years ago, 28-Mar-02, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Two questions on primitives
|
|
(...) There's no 1-16cyli.dat primitive because it hasn't been needed/asked for. The general approach is to not introduce primitives until they're needed. Steve (23 years ago, 28-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives)
|
| |
| | Why aren't the technic gear teeth primitives?
|
|
I was thinking that the teeth for the old technic gears (3647-1649) and the beveled ones (32270 and 32296) should be made into primitives. I tried editing the 3648 part in ldraw, but the file was too big to even load! (23 years ago, 28-Mar-02, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Two questions on primitives
|
|
(...) The INVERTNEXT directive takes care of this problem. Quoted from BFC proposal: "INVERTNEXT This option inverts a subfile. It may only be used immediately before a subfile command line, and it only influences the immediately following subfile (...) (23 years ago, 28-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives)
|
| |
| | Two questions on primitives
|
|
Two questions (if these have already been discussed, just direct me to the appropriate LUGNET post): 1.) I've noticed the new BFC complient primitives on the Parts Tracker. How are we going to resolve the fact that the cylindar primitve can be used (...) (23 years ago, 28-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives)
|
