 | | Re: Opinions needed for Color and Edge Values
|
|
(...) I completely agree that changing the colour codes at this stage is a terrible idea. However I have nothing against duplicating them. One thing we do need is to maintain, alongside the LDraw codes, mapping lists to other known systems such as (...) (16 years ago, 25-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) Since MLCAD (and other programs) do not support color codes above 511, a different approach to reading TLG colors is needed. However, I have to strongly agree with Philo. Changing color codes that have been defined for years is not a good (...) (16 years ago, 25-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) We should be able to have TLG names as a language file, since every TLG color value should map to every BL (BrickLink) color value. I certainly understand the drive to have them in the file in one form or another. Perhaps the most benefit can (...) (16 years ago, 25-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) I am _strongly_ against that. Imho this is the same mistake LEGO did a few years ago with the stone colors. What would be the point of defining a standard (ldconfig.ldr) to change it at the first drawback? Colors 70..72 are defined for more (...) (16 years ago, 25-Nov-08, to lugnet.cad)
|
| |
| | Re: LDraw (and LDraw.org) questions
|
|
(...) This has never been implemented. The SteerCo has had some discussions about also considering to use the wiki for the OMR but never reached consensus. IMHO I'd rather have a module for the CMS taking for granted that I'm not talking about a (...) (16 years ago, 25-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) I'd like to hear some opinions on how we do define backwards compatibility? Considering that most user built their models using MLCad (no idea which color numbers are supported by Leo, Bricksmith or SR3D) which comes with very limited color (...) (16 years ago, 25-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) The "besides the color code" isn’t a collateral damage but the main problem! We cannot ship the TLG numbering in a simple language file. Think about a blue car colored with LDraw code 1. Loading the TLG colors as language file you would (...) (16 years ago, 25-Nov-08, to lugnet.cad)
|
| |
| | LDraw (and LDraw.org) questions
|
|
A couple of questions regarding LDraw and LDraw.org. 1) Will the LDraw specification ever support normal vectors to facilitate polygon smoothing? 2) One of the pages on LDraw.org mentions an Official Model Repository. Where can I find this? Thanks! (...) (16 years ago, 25-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
In lugnet.cad, Scott Wardlaw wrote: You use in your description the attribute SPECKLE that is not yet official. So if we use that (I recommend that) we have to update the article (URL) as well. Only as a reminder. cu mikeheide (16 years ago, 24-Nov-08, to lugnet.cad)
|
| |
| | Re: LGEO update
|
|
(...) Sorry, I was mixing up different files. The error in 32062 was that the declare for "32062_clear" said "32064_clear". Maybe you have already fixed it. The one with the missing semicolon is actually lg_4262. It is on line 493. (16 years ago, 24-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) This is done with two exceptions to follow the BL naming scheme. Teal is not one of the BL color names, but the color values for LDraw Teal are almost the same as Dark_Tuquoise, according to Peeron and my own observation. Light_Red is also not (...) (16 years ago, 24-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) The file is "work in progress". Feel free to contribute. w. (16 years ago, 24-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values [DAT]
|
|
(...) Hi Willy, Why so many colors defined in present ldconfig.ldr ((URL) are missing from your chart? Otherwise, I had a look at the defined colors (LDraw, 0 to 28), imho there is not enough contrast for brown (6) and Violet (22). These colors (...) (16 years ago, 24-Nov-08, to lugnet.cad)
|
| |
| | Re: LGEO update
|
|
(...) Yeah, that's what I was remembering. -Mike (16 years ago, 24-Nov-08, to lugnet.cad, FTX)
|
| |
| | Re: LGEO update
|
|
(...) Oh, I never knew about that. I will make a #declare switch for the logo to display LGEO or LEGO and set it to display as LEGO by default. It will be included in the next update, so for now you have to remove the translate statements. Lutz (16 years ago, 24-Nov-08, to lugnet.cad, FTX)
|
| |
| | Re: LGEO update
|
|
(...) I remember the same thing in reference to an LDraw display at Legoland California. They didn't want 3D LDraw renders shown in the park with "LDraw" written on the studs. That was a number of years ago. --Travis (16 years ago, 24-Nov-08, to lugnet.cad, FTX)
|
| |
| | Re: LGEO update
|
|
(...) IIRC, there was discussion a long time ago, to the effect that LEGO *insisted* that the studs correctly display the logo, otherwise they *would not* lend their approval. You'd have to dig deep for the thread. -Mike (16 years ago, 24-Nov-08, to lugnet.cad, FTX)
|
| |
| | Re: LGEO update
|
|
(...) I suspected that might be the reason, and I figured out how to do the swap. However, POV export is a new feature of the upcoming LDView 4.0, along with LGEO support in that POV export. I'd prefer if there were an easy way that I could force (...) (16 years ago, 24-Nov-08, to lugnet.cad, FTX)
|
| |
| | Re: LGEO update
|
|
(...) Hi Travis, I did not want the LEGO text for copyright issues. In ld_defs.inc, just remove the translate statements at the end of declarations for letters E and G to create original logo as L3P uses. Lutz (16 years ago, 23-Nov-08, to lugnet.cad)
|
| |
| | Re: LGEO update
|
|
(...) I have a question about the stud logos. The code in lg_defs.inc makes it look like they should say LEGO, but they in fact say LGEO. (The letter comments are in the order L...E...G...O), but the E and G have translations inserted to swap them. (...) (16 years ago, 23-Nov-08, to lugnet.cad)
|
