 | | Re: Parts Releases and the CA
|
|
(...) I may have missed this, but has LDraw.org released a list of the parts that need to be replaced? I would think that making such a list available and encouraging part authors to focus their efforts on those parts first would speed things up and (...) (18 years ago, 9-Sep-06, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) I found that performance went down somewhat when I copied and pre-translated all the studs too. I could be creating a memory cache penalty. Anyway it is only one matrix multiply per stud (stud is already flattened in itself), which goes onto (...) (18 years ago, 9-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
The thread seems to be splitting from the original point, It is a fact that OpenGL generally places a depth of 16 on any transforms. If an LDRAW model in MPD format was presented to OpenGL as a raw data block I suspect that OpenGL would easily hit (...) (18 years ago, 8-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) Actually on modern cards strips are always slower than optmized lists. You can always try adding degenerate triangles to stitch strips together to save the cost of multiple render calls (too bad PC cards don't support a primitive reset index). (...) (18 years ago, 8-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) Well, typically the multiplies that occur for different studs have the same rotation and scaling aspects, the only thing different is the position. So instead of repeating the multiplication on the original matrix, if the top left 3x3 values (...) (18 years ago, 7-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) Okay... 15% speedup is substantial... that means that it's better to pre-transform the subfiles when generating the operations for the current file. I won't worry about the maximum depth any more then. (...) How does a renderer know which (...) (18 years ago, 7-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) Same here for LDView. LDView always flattens part geometry, and this seems to improve performance enough to be noticed. LDView does use a display list for each part, and a nested display list for each nesting level above that (as long as you (...) (18 years ago, 7-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) MPD files don't add that many extra levels... usually only 2, isn't it? Further, the only stacking that generally needs to occur at the mpd level is modification of the modelview matrix, which opengl guarantees a minimum of 32. It's only in (...) (18 years ago, 7-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) I tested the performance of, and saw a decent gain from flattening part geometry. (Perhaps 15% in BrickDraw3D for QuickDraw3D or OpenGL.) What this means is that when a part is prepared into a drawing list, it is not a list of calls to (...) (18 years ago, 7-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) As far as building instructions go, LPub only provides for unique background color/backdrop for up to four levels. This is about as much as I've ever seen in LEGO building instructions. The renderers take care of nesting within individual part (...) (18 years ago, 7-Sep-06, to lugnet.cad.dev)
|
