|
| |
|  
ldraw
(score: 1.151)
|
|
| |
|
ldraw
(score: 1.151)
|
|
| |
|
ldraw
(score: 1.151)
|
|
| |
|
ldraw
(score: 1.151)
|
|
| |
|
ldraw
(score: 1.151)
|
|
| |
|
ldraw
(score: 1.151)
|
|
| |
|
ldraw
(score: 1.151)
|
|
| |
|
ldraw
(score: 1.151)
|
|
| |
|
ldraw
(score: 1.151)
|
|
| |
|
ldraw
(score: 1.151)
|
|
| |
|
ldraw
(score: 1.151)
|
|
 | | Maximum depth of ldraw models?
|
| I notice that no maximum depth is given by the standard. How potentially non-compliant would a renderer be if it fails because parts in a model are too deeply nested (a maximum of as little as 16 on some OpenGL implementations). I notice that no (...) (18 years ago, 6-Sep-06, to lugnet.cad.dev)
| |
|
ldraw
(score: 1.151)
|
|
| | 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)
| |
|
ldraw
(score: 1.151)
|
|
| | 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)
| |
|
ldraw
(score: 1.151)
|
|
| | 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)
| |
|
ldraw
(score: 1.151)
|
|
| | 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)
| |
|
ldraw
(score: 1.151)
|
|
| | 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)
| |
|
ldraw
(score: 1.151)
|
|
| |
|
ldraw
(score: 1.151)
|
|
| |
|
ldraw
(score: 1.151)
|
|
| |
|
ldraw
(score: 1.151)
|
