 | | Re: Black seems wrong in ldconfig.ldr
|
|
(...) (er, which official color chart?) (...) Uh, Travis, it's *black*. It's *supposed* to be dark. People have questioned/complained that it's not 'true black' (ie, 0,0,0). You might be right about the origin of the 33 value, but I believe I was (...) (21 years ago, 13-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) In fact the official LEGO colour chart mentioned here (URL) uses 27, 42, 52 for black. ROSCO (21 years ago, 13-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(I switched to FTX due to an unusually long link.) (...) I was referring to the one at ldraw.org (URL) (LDraw definitions at the bottom). I believe that the LDraw color definitions there came from some version of the LDraw FAQ. When I said (...) (21 years ago, 13-Jan-04, to lugnet.cad.dev, FTX)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) Given that ldconfig.ldr is part of the LDraw parts library, I was referring to the color reference on the LDraw.org site (noted in another message). However, it might make sense to use the colors above, since they came directly from Lego, and (...) (21 years ago, 13-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) Why not use the optional MATERIAL bits from this old discussion (URL) come up with a modified ldconfig.ldr? Then implement some code in LDVIEW to enable your metallic lighting goodies when ldconfig.ldr contains the proper MATERIAL settings. (...) (21 years ago, 13-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) I agree that something of that sort would be a good idea, but in the case of my metallic colors, I actually hand-tweaked the settings for each metallic color. They aren't all the same. This was done partially to differentiate between chrome (...) (21 years ago, 13-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) Where else would you put it? What if you break the material settings up into two parts? 1) a material tag on the COLOURDEF line: 0 COLOURDEF 334 ChromeGold 15 0xFFC40026 MATERIAL metallic 2) a MATERIALDEF line added to the end of the file that (...) (21 years ago, 14-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) We're working on it. Give us another 24 hours to have something to present. Not a final 'done deal', but at least a decent writeup. Steve (21 years ago, 16-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) You could put your custom information in an ldviewconfig.ldr file which you supply with the LDView install. Then add a setting to LDView, allowing the user to specify multiple pre-processing files. Default the setting to (...) (21 years ago, 16-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) Thanks. That's a good idea. I'll have to think about it, though. Up until now, I have purposely avoided creating any LDView-specific meta-commands. On the other hand, this would be one of the few reasons that might convince me that an (...) (21 years ago, 16-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) The good side of the LSC is that with the reduced number of people, you are hopefully able to actually come to a consensus in a reasonable time frame. The bad side is that since the discussions are private, you have to deal with hecklers like (...) (21 years ago, 16-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) Well, I hope the final syntax for the color definition statement will allow some space for programs to support their own special syntactic needs. So you hopefully won't need a super-custom meta-statement for LDView, just a special flavor for (...) (21 years ago, 17-Jan-04, to lugnet.cad.dev)
|
