 | | Re: Color page updated
|
|
(...) It might fix it (I think it would still gum up the PT with over-zealous hold votes); but why break anything when we're just talking about adding fewer than 200 lines to the config file? I think it's a terrible idea to make dozens of (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw, FTX)
|
| |
| | Re: Color page updated
|
|
(...) I have had parts on the Part Tracker held because they used one of these colors. That means it is limiting. (...) Color numbers 32-47 and 256-511 is not every color under the rainbow. (...) This is exactly the problem. (...) If this is the (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) There are already two very old ways to specify RGB colors in LDraw files. One comes from ldlite with somewhere between 12 and 15 effective bits of color information, and the other from L3Lab/L3P with 24 bits of color information. If we're (...) (15 years ago, 3-Dec-09, to lugnet.cad.dev.org.ldraw, FTX)
|
| |
| | Re: Color page updated
|
|
(...) Of course it would - as well as it does LDView. But after adding x, y, z coordinates and correcting RGB code syntax would work fine with both LDView as well as L3Lab! 1 0x02F2F2F2 0 0 0 1 0 0 0 1 0 0 0 1 part.dat Don't know about MLCad, but I (...) (15 years ago, 3-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) Neither did I but if you really cannot find a suitable color for your pattern an RGB say in the form: 1 #F2F2F2 1 0 0 0 1 0 0 0 1 part.dat would surely solve your problem. And I'm going to propose this to the new elected LSC. As for the broken (...) (15 years ago, 3-Dec-09, to lugnet.cad.dev.org.ldraw, FTX)
|
| |
| | Re: Color page updated
|
|
(...) I never said that it was meant to limit, only that it is made up of these colors now. Please don't take this to mean that new colors can't be added, or that it invalidates other colors. We already know of at least one color that should be (...) (15 years ago, 3-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) I disagree that this was the original purpose of the ldconfig file. I can say that definitively, since I was the one who first proposed the file here: (URL). The purpose was that when *new* colors were added, ldraw software tools would have a (...) (15 years ago, 3-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) This isn't the first time that LDconfig.ldr has been updated - and it is just that, the file has been updated with MORE colors than before. I think we are loosing sight of the purpose of LDconfig.ldr... The LDconfig file is meant to be a quick (...) (15 years ago, 3-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) Although I have decided to refrain from participation in this thread (you already know my position and you totally neglect it), I make one exception and say "Amen!" to all of Andy's points above. /Tore (15 years ago, 2-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) I apparently have missed the discussion when it comes to certain colors are suddenly "not supported," but I'd like to register my opinion on it. It is a huge error to be calling colors in the ranges of 32-47 and 256-511 as "MLCad color codes" (...) (15 years ago, 2-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) That is correct. LDView has its own internal color table, which is used if you don't check the "Process ldconfig.ldr" check box in the General tab of its preferences. When you check that check box, it overrides these default colors using the (...) (15 years ago, 2-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) That's a really good new!!! since something is moving on and that's enough for me. In the while I will translate all missed color codes in the range on transparent colors to a light grey transparent (having code between 32 and 63) and all the (...) (15 years ago, 2-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) I started fixing those parts and they will be uploaded to the PT for certification since some also include minor primitive substitution as well as BFCing. However I cannot forseen when those fixes will be ultimately be shipped in an official (...) (15 years ago, 2-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) That's good! Anyway, there are still many color codes included in official parts (39,257,258,260...) that seems are not supported. I have already rosen the problem in a previous discussion and the answer was that they where MLCad color codes (...) (15 years ago, 2-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) All this work on the colours is fantastic, guys. If I get some time I plan to try to work out how to make the pearl colours in POVray. But time is the precious commodity. For those that are interested (and have a copy of perl) I wrote a little (...) (15 years ago, 2-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: 2009/2010 LDraw Standards Committee (LSC): Election results
|
|
(...) Thanks for voting for me and congratulation to the other members of the committee! cu mikeheide (15 years ago, 1-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Color page updated
|
|
Hi folks, the colors page at LDraw.org has been updated: (URL) find links to localized versions of the color table as well as Philo's Visual LDConfig.ldr picture: (URL) w. (15 years ago, 1-Dec-09, to lugnet.cad, lugnet.cad.dev.org.ldraw, lugnet.announce)
|
| |
| | 2009/2010 LDraw Standards Committee (LSC): Election results
|
|
The winners of the 2009/2010 LDraw Standards Committee (LSC) election are (in alphabetical order by last name): Travis Cobbs Mike Heidemann Santeri Piippo Allen Smith Scott Wardlaw Congratulations to the new LDraw Standards Committee (LSC) members! (...) (15 years ago, 1-Dec-09, to lugnet.cad, lugnet.cad.dev.org.ldraw, lugnet.announce)
|
| |
| | Re: *** LSynth 3.1 Released ***
|
|
(...) Thanks, I don't know how I missed that. There was also a small typo in the source code release that prevents it from compiling on OSX. That's 2 for 2 failures on the released files. Oh well, maybe 3.1.1 will be perfect? (15 years ago, 24-Nov-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: *** LSynth 3.1 Released ***
|
|
(...) default was "(Default)", instead of LSynth or something similar. I'm not sure if it matters, but this was in Windows 7. --Travis (15 years ago, 23-Nov-09, to lugnet.cad.dev.org.ldraw)
|
