 | | Re: ring 3 to 5
|
| (...) Yes, otherwise you get anomalies like this one: (URL) the outer ring of the tile got high-quality-ified but the fill in (non primitive?) circle didn't, leaving gaps. Also the plate below it, since it has stud cutouts, isn't as "round" as the (...) (25 years ago, 3-May-02, to lugnet.cad.dat.parts.primitives)
| | | | | Re: ring 3 to 5
|
| (...) True. But it's more than nothing. (...) LDraw (and LEdit, I assume) don't cache any files in memory. Read it (line by line), process it, and throw it away. (...) Reducing the number of files may not be important to rendering speed, but it is (...) (25 years ago, 3-May-02, to lugnet.cad.dat.parts.primitives)
| | | | | Re: ring 3 to 5
|
| (...) Actually, for rounded elements, it's almost always[1] preferable to use primitives. That way, programs that do primitives substitution can replace the polygonal primitive with a true round object. -- Steve 1) 'almost always' meaning, 'I can't (...) (25 years ago, 3-May-02, to lugnet.cad.dat.parts.primitives)
| | | | | Re: ring 3 to 5
|
| (...) However, when deciding whether or not to in-line sub-parts, reducing polygon count isn't a consideration. Any other advantage, small or not, should be maximised. (...) Whether they do or not, there's still extra time spent identifying the (...) (25 years ago, 3-May-02, to lugnet.cad.dat.parts.primitives)
| | | | | Re: ring 3 to 5
|
| (...) I think it is an extremely small advantage. What programs actually read any file more than once? I mean, Are there programs that actaully open the file and read the part in every time it's referenced? Or are there programs that even if they (...) (25 years ago, 3-May-02, to lugnet.cad.dat.parts.primitives)
|
|
