|
| | Re: ring 3 to 5
|
| (...) One thing you should be careful of, though. If you do inline it so that your new sub-part is used and doesn't reference any actual primitives, programs like L3P and LDView can end up displaying things with gaps. Both LDView and L3P perform (...) (22 years ago, 2-May-02, to lugnet.cad.dat.parts.primitives)
| | | | Re: ring 3 to 5
|
| Hello, in this case i would agree tp Franklin's opinion regarding using two ring instead of creating a new primitive because if we create a new primitive section for this you will have very big number of possible combinations (ring 1 +ring 2, ring 1 (...) (22 years ago, 2-May-02, to lugnet.cad.dat.parts.primitives)
| | | | Re: ring 3 to 5
|
| (...) It's all a compromise (just like life!). If you go creating primitives for every little sub-part that's used a few times, you end up with a primitive directory that's unwieldy & lots of parts which inline because they don't know the (...) (22 years ago, 2-May-02, to lugnet.cad.dat.parts.primitives)
| | | | Re: ring 3 to 5
|
| (...) As a program author, I believe that yes this would result in twice the polygon count. While I aggree that programs should generally do everything they can to make authoring parts easier, I also think that Part Authors ought to keep in mind (...) (22 years ago, 2-May-02, to lugnet.cad.dat.parts.primitives)
| | | | Re: ring 3 to 5
|
| (...) Wouldn't that result in twice as many polys that have to be rendered? Forgive if that's a dumb question, I ain't much of an author, you know. :-) (22 years ago, 2-May-02, to lugnet.cad.dat.parts.primitives)
| |