 | | Re: MLCad being used by Lego Universe dev team?
|
|
(...) So do I. I definitely think it's very cool to have a shot from my program show up in an official page at lego.com. Of course, as far as I can tell, LEGO Universe is being developed by a 3rd party (NetDevil Studios), so the shot presumably (...) (16 years ago, 3-Dec-08, to lugnet.cad, FTX)
|
| |
| | Re: Tool to reconstruct models from POV files
|
|
(...) I don't think it's safe to assume that L3P won't change its POV output, and I don't think it's fair for the existence of a tool that depends on that output to discourage Lars from changing it. (I know you weren't implying that it would, but (...) (16 years ago, 3-Dec-08, to lugnet.cad)
|
| |
| | Re: MLCad being used by Lego Universe dev team?
|
|
(...) I think that's pretty darned cool. Jim (16 years ago, 3-Dec-08, to lugnet.cad, FTX)
|
| |
| | Tool to reconstruct models from POV files
|
|
I'm thinking of creating a tool to reconstruct LDR models from L3P-generated POV files. I'm wondering before I start what particular potential problems I should look out for. POV SDL is quirky to say the least, but at first glance L3P's output (...) (16 years ago, 3-Dec-08, to lugnet.cad)
|
| |
| | Re: MLCad being used by Lego Universe dev team?
|
|
The LDraw suite of tools might be the easier method to create simple models from scratch than the heavyweight parts-authoring tools they probably use in-house. In fact, I still find the original ledit.exe by James Jessiman to be in many ways more (...) (16 years ago, 3-Dec-08, to lugnet.cad, FTX)
|
| |
| | Re: "LGEO" and "L3P v1.4 BETA 20080930"
|
|
One additional suggestion I'd like to make is to, instead of writing the same data repeatedly over and over for each part, store the part data (matrix transformations and materials) in arrays and then traverse at the end of a file using loops. (...) (16 years ago, 3-Dec-08, to lugnet.cad)
|
| |
| | Re: MLCad being used by Lego Universe dev team?
|
|
(...) Here's a snapshot from LDView with settings and light angle tweaked to reproduce the image as closely as possible: (URL) I don't know about you, but I know what I think ;-). --Travis (16 years ago, 3-Dec-08, to lugnet.cad, FTX)
|
| |
| | Re: MLCad being used by Lego Universe dev team?
|
|
(...) The shading looks too smooth to be MLCAD. Also, the studs in the image have the logo on top, which MLCAD doesn't do. -Mike (16 years ago, 3-Dec-08, to lugnet.cad)
|
| |
| | MLCad being used by Lego Universe dev team?
|
|
Hey guys, Got the latest Lego Universe newsletter, and found this interesting. (URL) screenshot of the CAD bricks seems to be from MLCad, with the edge lines and stud resolution. I would think they'd be using Lego's internal Maya library. -Stefan- (16 years ago, 3-Dec-08, to lugnet.cad)
|
| |
| | Re: MOC Updates
|
|
(...) Thanks! I'm working on an interactive tour using panoramic images. The scenes are taking a long time to render, so it might still be a few days before I am finished. -Mike (16 years ago, 3-Dec-08, to lugnet.cad.dat.models)
|
| |
| | Re: Minifig arms
|
|
(...) Hehe. yeah, I thought of using the wizard in MLCad after I posted the message. -Mike (16 years ago, 3-Dec-08, to lugnet.cad.dat.models)
|
| |
| | Re: LGEO update
|
|
I've also noticed some glitches with respect to head pieces when using the POV-Ray 3.7 beta: * 390.DAT is glitchy. * 3901.DAT doesn't appear at all. * 3834.DAT does not appear at all. * 3626BP05.DAT is missing certain subparts. * I can't see the (...) (16 years ago, 3-Dec-08, to lugnet.cad)
|
| |
| | Re: "LGEO" and "L3P v1.4 BETA 20080930"
|
|
Does anyone know of if "fastrad.inc" is compatible with the L3P 1.4 output? Thanks. -Mike (16 years ago, 2-Dec-08, to lugnet.cad)
|
| |
| | Re: *** LDView Version 4.0 Beta 1 Released ***
|
|
(...) ... (...) This is a big update. I heartily recommend you give it a try, especially if you are working with LPub or using a Mac (or both). Travis has made some great additions to the program. Jim (16 years ago, 2-Dec-08, to lugnet.cad, lugnet.cad.dev.mac, FTX)
|
| |
| | *** LDView Version 4.0 Beta 1 Released ***
|
|
LDView 4.0 Beta 1 is now available for download from the LDView downloads page here: (URL) This is a Beta release, which means that I’m hoping to get as much feedback as possible. This also means that it is likely not as stable as a final release, (...) (16 years ago, 2-Dec-08, to lugnet.announce, lugnet.cad, FTX) !
|
| |
| | Re: Summary of LPub4 Meta commands? [DAT]
|
|
(...) But if you have something besides Strut between the two Strut, it doesn't work. 1 71 30 -70 -50 0.66913 -0.743145 0 0.743145 0.669131 0 0 0 1 Strut 1 0 0 0 0 1 0 0 0 1 0 0 0 1 foo.dat 1 71 -30 -70 -50 0.66913 0.743145 0 -0.743145 0.66913 0 0 0 (...) (16 years ago, 2-Dec-08, to lugnet.cad)
|
| |
| | Re: Summary of LPub4 Meta commands?
|
|
(...) I've observed similar issues. Typically the reason appears to be that a statement is inserted outside the appropriate MULTI_STEP BEGIN/END block. (I don't think this happens by design.) As you've found, typing or cut and pasting the statement (...) (16 years ago, 2-Dec-08, to lugnet.cad)
|
| |
| | Re: Summary of LPub4 Meta commands?
|
|
(...) I second that! I must admit never trying LPub before this version so you can only imagine my astonishment. I managed to find only a few strange things (sorry if it has said before and I missed it): - Being a metric person, I started (...) (16 years ago, 2-Dec-08, to lugnet.cad)
|
| |
| | Re: Welcome digitalbricks.org, goodbye digitalbricks.nl
|
|
Jeroen, I've read this before, wanted to answer, but didn't. But now, I've come across it again. Question is: What becomes of the domainname digitalbricks.nl? Are you keeping it and registered? If not, I would be interested in taking over ownership (...) (16 years ago, 1-Dec-08, to lugnet.cad)
|
| |
| | Re: LGEO update
|
|
(...) Seems to affect only 73435. Is fixed for the next update. For a workaround open lg_73435.inc and change to rotation at the end of object definitions from -90 to 90. Regards, Lutz (16 years ago, 1-Dec-08, to lugnet.cad)
|
| |
| | Re: L3P Question
|
|
(...) The AR option is implemented for now as a technical test. I wanted to make use of some of Antons parts, such as minifig gear and curved parts. These are hard to redesign in LGEO with the small cylinder edges. To make use of Antons parts, I (...) (16 years ago, 1-Dec-08, to lugnet.cad, FTX)
|
| |
| | Re: L3P Question
|
|
(...) If L3P is using the Anton Raves support in the latest LGEO, then at this point there are very few parts supported. However, you can convert LDraw models using Anton's online converter here: (URL) On a side note, your Brickshelf gallery isn't (...) (16 years ago, 1-Dec-08, to lugnet.cad, FTX)
|
| |
| | L3P Question
|
|
Pardon the idiocy, but it is taking me too much time figure out how to do this. I have recently started trying my hand at rendering. There are a large number of programs to learn! LDRAW, MLCAD, L3P, POV-Ray, MEGA-POV, and so forth. I've been doing (...) (16 years ago, 1-Dec-08, to lugnet.cad, FTX)
|
| |
| | Re: Minifig arms
|
|
(...) What editor do you use? I know that Bricksmith and MLCAD have minifig editors, and I'm pretty sure LeoCAD has a minifig "wizard", too. (...) Good idea. Jim (16 years ago, 30-Nov-08, to lugnet.cad.dat.models)
|
| |
| | Minifig arms
|
|
I am having troule rotating the minifig arms so that they connect properly with the torsos. What are the correct rotation angles? Also, the pre-made minifigs seem to use old versions of the arm parts. Maybe it could be updated to use the newest (...) (16 years ago, 30-Nov-08, to lugnet.cad.dat.models)
|
| |
| | Re: LGEO update
|
|
(...) The part #73435 (Door 1 x 4 x 5 Right) is misaligned when I use the LGEO option. It seems the part's origin may be different in the two files. Haven't checked whether this happens with the Left door as well. -Mike (16 years ago, 30-Nov-08, to lugnet.cad)
|
| |
| | LDCalc 0.1.0.3 released
|
|
I have just finished version 0.1.0.3 of LDCalc. The changes are: Option Tab Now easy to use 'Save' Button to change the default values. Triangle Tab Some additional checks of the values provided are made. Triangle Preview installed, based on the (...) (16 years ago, 30-Nov-08, to lugnet.cad)
|
| |
| | Re: L3PAO 1.9 Beta
|
|
It looks like you have put a lot of work into updating L3PAO! If you don't mind, I'd like to request the follow defaults be changed: check / mark Render Upon Completion automatically populate the Output Filename text box change output image size to (...) (16 years ago, 30-Nov-08, to lugnet.cad)
|
| |
| | Re: L3PAO 1.9 Beta
|
|
(...) There are actually two .ocx files missing. These are components that would be included in an installation / setup. I have zipped them and put them here for anyone to download: (URL) place them in your system32 directory and restart your (...) (16 years ago, 30-Nov-08, to lugnet.cad)
|
| |
| | Re: L3PAO 1.9 Beta
|
|
(...) OK. Pitty. I will have to install the old version on my XP machine then. (16 years ago, 30-Nov-08, to lugnet.cad, FTX)
|
| |
| | Version 535 of my library is available now.
|
|
Version 535 of the Library can be found on my website now, 7 new pieces have been added. The Reference Gallery has been updated to version 535 too now. With the kindest of greetings, Anton Raves (URL) (16 years ago, 30-Nov-08, to lugnet.cad)
|
| |
| | Re: L3PAO 1.9 Beta
|
|
(...) I am running Win XP SP3 under VMware (which shouldn't make any difference) so it happens under XP too. Mike (16 years ago, 30-Nov-08, to lugnet.cad, FTX)
|
| |
| | Re: L3PAO 1.9 Beta
|
|
(...) On my Vista laptop an old version L3PAO (1.4.0.2) gives me this message: "Component 'COMDLG32.OCX' or one of its dependencies not correctly registered: a file is missing or invalid" (...) I get the same message as Mike using the new beta (...) (16 years ago, 29-Nov-08, to lugnet.cad, FTX)
|
| |
| | Re: Summary of LPub4 Meta commands?
|
|
(...) It is. LPub should do so automatically when you create a callout of a submodel used multiple times in one step. The callout begin/end meta commands surround both references. For example: 0 !LPUB CALLOUT BEGIN 1 71 30 -70 -50 0.66913 -0.743145 (...) (16 years ago, 29-Nov-08, to lugnet.cad)
|
| |
| | Re: Summary of LPub4 Meta commands?
|
|
(...) Well this is just slicker than snot! It didn't even occur to me to use the right mouse button. After playing with it a bit it looks like I need to reorganize my model to achieve what I want. I still couldn't figure out to to make one callout (...) (16 years ago, 29-Nov-08, to lugnet.cad)
|
| |
| | Re: L3PAO 1.9 Beta
|
|
(...) ... snipped .. I'd like to try this but I get a message about a missing file SYSINFO.OCX which appears to be one of the ActiveX controls you noted might be a problem. Is there an easy solution? Thanks, Mike (16 years ago, 29-Nov-08, to lugnet.cad, FTX)
|
| |
| | Re: MOC Updates
|
|
(...) Jim (16 years ago, 29-Nov-08, to lugnet.cad.dat.models)
|
| |
| | Re: Summary of LPub4 Meta commands?
|
|
(...) Hi, Mike. To make a callout, right-click the background of a submodel page and select "Convert to Callout". To do the reverse, right-click a callout and select "Unpack Callout". The corresponding meta commands are !LPUB CALLOUT BEGIN and !LPUB (...) (16 years ago, 29-Nov-08, to lugnet.cad)
|
| |
| | Summary of LPub4 Meta commands?
|
|
Is there a summary of all of the LPub4 meta commands available? I have started playing with LPub4 and I am really impressed. What a huuuugggee improvement over prior versions of LPub. I am playing with a model I have which has about a dozen (...) (16 years ago, 29-Nov-08, to lugnet.cad)
|
| |
| | Re: "LGEO" and "L3P v1.4 BETA 20080930"
|
|
Awesome! I totally missed this. A couple of requests: 1) An option to search for and "#include" L3P-generated parts instead of writing them all to the POV file. 2) Replace mesh objects with mesh2. Thanks for all the hard work! -Mike (16 years ago, 29-Nov-08, to lugnet.cad)
|
| |
| | Re: LGEO update
|
|
(...) Nevermind. The problem was that the beta version of L3P needs to be installed. There's no mention of this on your site. -Mike (16 years ago, 29-Nov-08, to lugnet.cad)
|
| |
| | Re: LGEO update
|
|
(...) L3PAO complains when I direct it to the location of this archive. Are there any incompatibilities between the two I should worry about? -Mike (16 years ago, 29-Nov-08, to lugnet.cad)
|
| |
| | Re: LDraw (and LDraw.org) questions
|
|
(...) Awesome! Thanks! -Mike (16 years ago, 29-Nov-08, to lugnet.cad)
|
| |
| | Re: Mesh Enhancer?
|
|
(...) Could you please send me a copy as well? The whole domain where the site was hosted seems to be down. -Mike (16 years ago, 29-Nov-08, to lugnet.cad, lugnet.technic, FTX)
|
| |
| | MOC Updates
|
|
I've updated my digital MOCs page. None of the models are new, but they are all freshly rendered using radiosity and are all available for download. (URL) hope you like them! -Mike (16 years ago, 29-Nov-08, to lugnet.announce.moc, lugnet.cad.dat.models)
|
| |
| | Re: Unified installer
|
|
(...) Ah, I clicked on the "Download" link (bolded) on the ldraw.org sidebar and didn't see it anywhere. It is listed in the "Getting Started" section instead. -Mike (16 years ago, 29-Nov-08, to lugnet.cad)
|
| |
| | Re: Unified installer
|
|
(...) The LDRAW ALL-IN-ONE-INSATLLER does this already. The user gets to choose 1 of 3 options. 1) BASIC install which installed LDRAW Part libary, MLCAD, and LDVIEW 2) INTERMEDIATE which installs BASIC + L3P, L3PA, LPUB, LGEO and POV-Ray 3.1g and (...) (16 years ago, 28-Nov-08, to lugnet.cad)
|
| |
| | Re: Unified installer
|
|
(...) This problem has been indintified a long ago, but a quick solution was blocked by the fact that several of the included part files are historicly not licenced for distribution in another form then included within the original LDraw Package. In (...) (16 years ago, 26-Nov-08, to lugnet.cad, FTX)
|
| |
| | Unified installer
|
|
I think the way that the LDraw utilities are installed is a bit complicated for novice users, especially children or parents of children. Essentially, the current scheme asks users to first install the resources required by the software, and *then* (...) (16 years ago, 25-Nov-08, to lugnet.cad)
|
| |
| | 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)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) I set up a new LDConfig.ldr file in sync with the above. Check it out at the wiki: (URL) (16 years ago, 23-Nov-08, to lugnet.cad)
|
| |
| | Best option for real-time viewing on the web
|
|
I was wondering what the best option was for real-time viewing on the web. I notice there's a utitlity on LDraw.org, but it requires regestering a component. I'm thinking that VRML is still the best option. -Mike (16 years ago, 23-Nov-08, to lugnet.cad)
|
| |
| | Re: LGEO update
|
|
(...) There is a typo at line 176 in "lg_4858.inc". The vector needs to be closed with a greater than sign instead of a less than sign. -Mike (16 years ago, 23-Nov-08, to lugnet.cad)
|
| |
| | Re: LGEO update
|
|
(...) Ok, in 3647 the lg_angle is obsolete. in 3649 you can switch the numbers divided for a workaround. #declare lg_angle1=acos((0.3+...R_SPACE)); (...) I cannot find a missing semicolon in this file? I have fixed an other error in this file (...) (16 years ago, 23-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) 'Persons' can be male or female so 1 in 12 of 1 in 2 are coloublind. AKA 1 in 24 ;) Tim (16 years ago, 23-Nov-08, to lugnet.cad, lugnet.off-topic.geek)
|
| |
| | Re: LGEO update
|
|
(...) I discovered a couple of errors in the library: lg_3647 & lg_3649: Both of these generate a domain error on Line 15. I suspect that the acos formula is starting with a value not between -1 and 1. lg_32062: Missing a semicolon at the end of one (...) (16 years ago, 23-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) Thant sounds very good to me. The support for language support I can imagine a new file for each language that is called LDconfig.de for German for example. The syntax can be: 0 !COLOUR Weiss CODE 30001 When there is no entry for the requested (...) (16 years ago, 22-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) Did you miss your morning coffee? :-) 1/12 = 0.08333... 1/24 = 0.04166... Or are you saying that only ~4% of the males are 'color blind'? Both Wikipedia (5-8%) and Swedish statistics (~8%) agree with the 8% figure, but you might live in a (...) (16 years ago, 22-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) I've been questioned about the directions we are going with our efforts. The current plan for the LDConfig.ldr is: * Keep the core color numbers from 0-50, plus some historical colors like Black_Rubber, Chrom or Gold for backwards (...) (16 years ago, 22-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) I like this proposal but I'd like to run a test file using the 52 threshold and try also different shades of gray first before diving into more detail. w. (16 years ago, 22-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) Like me. Which is why I'm not a good person for making comments on the colours in this thread but am a good person to make comments about edge lines. Tim PS. It's 1 in 24 persons to be precise but I know what you mean ;) (16 years ago, 22-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) SNIP (...) I just found an old thread thread that has also no solution to the question of the edge colors. (URL) I believe we have to found one now. I have found also other threads regarding this issue and I try to sum up: 1) Black is the (...) (16 years ago, 21-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) Thanks Jaco for this hint. The above lines are all the lines that are not the same the standard MLCad colors. And in this case this are really standard MLCad color. MLCad has a build in check for colors. So we can change the MLCad.cfg, to what (...) (16 years ago, 21-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) These files were created outside of MLCAD and are intended for testing purposes only. They are not meant for regular use. MLCAD was designed to allow the user to create custom colors and save them to the model file. Since the MLCAD.cfg files (...) (16 years ago, 21-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
Hi all, I've been experimenting with these new colors and configuration files. I am however now ending up with these lines of code once I edit a file in MLCad: 0 COLOR 64 Bright_Light Blue 0 208 255 255 255 208 255 255 255 0 COLOR 65 Bright_Light (...) (16 years ago, 21-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) If you use the above mentioned calculation, you get a color value that represents a gray color with the same brightness than the color itself. I also feel that the 50% value (127) is not a good value. It should be maybe at 40, if we do use a (...) (16 years ago, 21-Nov-08, to lugnet.cad, FTX)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) Yeah I agree that Gray and Dark_Gray only work on the very darkest of colors like Black or Dark_Brown. Unless someone wants to spend a lot of time customizing an edge for each color, I'd recommend setting a dividing break point at which to (...) (16 years ago, 21-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) Hmmm ... where do these values come from? I changed the edge line using this calculation and used a 50% Gray for the lighter edge and pitch black for a dark edge (applied only to the first row, the rest is still #1F1F1F). IMHO it looks AWFUL (...) (16 years ago, 21-Nov-08, to lugnet.cad, FTX)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) Definitely not! You should hear me and my wife 'quarrel' if a color is blue or green. We have very different perception of that border line... Only ~8% of males (< 1% for females) are red-green 'color blind', but that still means 1 out of 12 (...) (16 years ago, 20-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) If you use LDView as your renderer for LPub, make sure you have "Process ldconfig.ldr" set in LDView's General Preferences. Then, use an ldconfig.ldr file that has the colors you want. Willy posted one in this thread. The ldconfig.ldr file (...) (16 years ago, 21-Nov-08, to lugnet.cad, FTX)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) The color values in the MLCAD.cfg files that I converted are not my creation. Most of these values come straight from The LEGO Group. A very few of them are from Peeron and one or two from Bricklink. The Dark_Green that you see is from TLG and (...) (16 years ago, 20-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) SNIP (...) The current LDConfig.ldr values in the MLCAD.cfg converted. You can download that mlcad.zip at (URL) (16 years ago, 20-Nov-08, to lugnet.cad, FTX)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) Yes, Dark Green is ok, but I think the values are too low. Scott, have you calibrated you systems where you have created your colors?(Please see my previous post) cu mikeheide (16 years ago, 20-Nov-08, to lugnet.cad, FTX)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
The color is not green, it is dark green: (URL) Scott (16 years ago, 20-Nov-08, to lugnet.cad, FTX)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) Maybe this is also an issue regarding the jpg file format. I have just loaded that picture file to the picture program "Paint.NET" and found with the color picker that the values for the green color is approx. R 4 - G 15 - B 9. That is realy (...) (16 years ago, 20-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) I'd say "Definitely!" (...) settings) according to that page, and now I don't have to adjust gamma inside PaintShop Pro anymore! Unfortunately, the comparison2.jpg still shows black where it should show green, but I can't increase gamma or (...) (16 years ago, 20-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
Great stuff here with those colors. I've created a tutorial in Dutch for my homepage on how to use the new colors. Question: how do I get LPub (4.0.0.x) to work with these configuration files? (16 years ago, 20-Nov-08, to lugnet.cad, FTX)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) Thanks Scott, I got it to work. Strange that I've never given this any attention before... :-) (16 years ago, 20-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) The intensity of a colour is usually given by I = 0.299R + 0.587G + 0.114B so your cutoff should be based on that rather than a simple mean. Tim (16 years ago, 20-Nov-08, to lugnet.cad, FTX)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) Yeah! That IS the problem with colors. You can adjust so many settings, that on an other monitor it looks completely different. I am using WinXP with a ATI Radeon 9250 and a TFT Benq monitor. So far I can see windows does not provide a (...) (16 years ago, 19-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) BTW, both these pictures look quite awful on my Windows CRT monitor with a gamma of 1.0. I had to copy them to my painting program and adjust the gamma correction to 2.60 before I realized that the engine in Comparison.jpg was gray/yellow, not (...) (16 years ago, 19-Nov-08, to lugnet.cad)
|
