 | | 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)
|
