 | | 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)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) Hmm. I use MPD models a lot, there can be several levels of nesting within a single .mpd file, and I have been known to refer to .mpd files from other .mpd files. I'm not sure how deep my nesting of model files goes, but I'd be a little (...) (18 years ago, 6-Sep-06, to lugnet.cad.dev)
|
| |
| | 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)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) Well, one that I have gives a warning message that says it can't handle color 24 and substitutes 16 for such lines. But I wasn't sure if that was correct behaviour. Another one that I've played with quietly accepts such lines, but appears to (...) (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) Actually, that grep doesn't return anything. '^[ \t]*1 24' does return hits from three files, though. Every single place in the library that this is used, it's used in a reference to one of the edge primitives. The edge primitives use color 24 (...) (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) In the case of some kind of direct color, I guess the rendering program is free to do whatever it wants. The simplest action would be to default to black (either LDraw 0, or RGB #000000). I'd be interested to hear what actual rendering (...) (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
Okay... that makes sense. But what if the contrast color for the current file's main color is just an RGB value rather than a color index? What should the subfile's contrast color be set to in that case? Thank you for your help, by the way. >> Mark (...) (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) The contrast color within the subfile would be defined in the normal way - use the main color for the subfile, and look up the contrast color from the color table. The fact that the originating linetype 1 used color code 24 shouldn't matter by (...) (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) Right... but what should the contrast color be defined as within the subfile? The same? >> Mark (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) Not exactly -- just use the current contrast color as the main color for the subfile. Whenever a subfile is rendered, it should already be looking up the local contrast color based on the local main color. Steve (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) Does that mean that it would be appropriate for a renderer to just swap the main and contrast colors when it encounters such a line, or what? I just want know what a renderer is supposed to do. (...) Well, doing grep '^1 24 ' on the parts (...) (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) It will be the constrast color for the constrast color. Which may be the same as the main color -- but it may not. Also, some viewers (like L3Lab) may balk at rendering a file which uses color 24 in a line type 1. Steve (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) OK, I was partly right. There actually is a standard defined for colour extensions, you can view it here (URL) it only applies to colours defined either in ldconfig.ldr, or in the part files or model files themselves. And it is still up to the (...) (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) Hi Mark, I'm pretty sure there is no standard for that, and it depends on which renderer you use. ROSCO (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | What does a subpart with color=24 mean?
|
|
How is the contrast color defined for line type 1, when color=24? >> Mark (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Proposal for MLCad.ini Enhancements
|
|
(...) hi allen, many thx for the .ini file fixes you sent me via mail. I'll load them up asap. the rest is michael's territory as I'm only the maintainer of the data. bye, w. (18 years ago, 19-Aug-06, to lugnet.cad.dev)
|
| |
| | Proposal for MLCad.ini Enhancements
|
|
In the course of writing a minifigure generator for my Bricksmith program, I've really come to appreciate how nifty it is to have something like the MLCad.ini file to work with. I've very grateful to the people who designed and maintain it. However, (...) (18 years ago, 18-Aug-06, to lugnet.cad.dev, FTX)
|
| |
| | Re: 48 directory and non filename only line 1 part file names
|
|
(...) Yes, basically. It wouldn't make any sense to add the parts\s directory, because those files are segments of parts -- they aren't complete objects in any sense. They are only intended to be used by part files, which should refer to them (...) (18 years ago, 31-Jul-06, to lugnet.cad.dev)
|
