 | | Dungeon Delver: That Frog...
|
|
Well, I've been working with MLCad and LDView for a few weeks now. Back to it from years back... Spent some time today to buld this little scene. Used MLCad to build it, LDView to catch the snapshot, and Paint Shop Pro to resize and add a little (...) (15 years ago, 31-Jan-10, to lugnet.cad, lugnet.castle)
|
| |
| | Re: LEGO's Internal colour palette
|
|
(...) That's why I went no farther than with the pinks/purples. (...) (snippage) I see 2 possible solutions to this whole mess: 1. Poll/talk with everyone until names we can all agree on are found. 2. Drop names altogether and refer to colors (...) (15 years ago, 31-Jan-10, to lugnet.cad)
|
| |
| | Re: LEGO's Internal colour palette
|
|
(...) Don't burn out your brain trying to figure out how they came up with the official color names. All that is required is to understand that there's some _serious_ disparity between their names and ours. For instance: They call it Brick Yellow. (...) (15 years ago, 30-Jan-10, to lugnet.cad)
|
| |
| | Re: LEGO's Internal colour palette
|
|
(...) I wonder why that color is called Bright Purple? On Bricklink and elsewhere, it's called Dark Pink. It don't look purple at all. What's the diff between pink and purple? Pink = Red + White. Purple = Red + Blue. The pinks and purples seems to (...) (15 years ago, 30-Jan-10, to lugnet.cad)
|
| |
| | Re: What's going on with 59443.dat?
|
|
(...) Yes, they are and remain official. The new version of angle connectors will hopefully become official at the same time as (unofficial) part 59443, keeping coherency in the library. But indeed as you need to use unofficial 59443 the way to go (...) (15 years ago, 30-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: What's going on with 59443.dat?
|
|
(...) Does this mean that the other angle connectors are no longer official parts and I need unofficial copies? (15 years ago, 30-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: LEGO's Internal colour palette
|
|
(...) Pretty sure that medium nougat is the middle-eastern skintone from Indiana Jones sets. Bright purple is probably the purple they've settled on to minimise the colour issues (in quite a few sets this year). Tim (15 years ago, 30-Jan-10, to lugnet.cad)
|
| |
| | Re: What's going on with 59443.dat?
|
|
Hi Eric, (...) I have recently updated angle connectors to add the engraved identification number. Doing so I also improved the shape to more closely match real parts. After that I updated 59443 to match the new angle connectors shape. You should (...) (15 years ago, 29-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: LEGO's Internal colour palette
|
|
(...) Phosphorous Green is Glow-in-the-Dark. It's already noted in the Peeron color chart (far right column for 50 Phosphorous White), but there are at least two distinct GitD colors (noted as opaque and translucent in Bricklink), and I couldn't (...) (15 years ago, 29-Jan-10, to lugnet.cad)
|
| |
| | What's going on with 59443.dat?
|
|
What's going on with 59443.dat? This is the Technic inline axle joiner, the one which has NO circumferential ridges to fit with the drive ring but instead is smooth to match with the other angle connectors. There used to be two different versions of (...) (15 years ago, 29-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: LEGO's Internal colour palette
|
|
Comparing this list to the LDConfig on my machine, there are three new colors: 221 Bright Purple 294 Phosphorous Green 312 Medium Nougat Unless anyone else volunteers, I'll take some time next week to match them to the BrickLink colors. Scott (15 years ago, 29-Jan-10, to lugnet.cad)
|
| |
| | Re: LEGO's Internal colour palette
|
|
(...) Yeah the full list is much huger. This is just the ones available at present but it gives an idea of eg. the best colours to focus on for renders and potentially other forms of restriction. Tim (15 years ago, 29-Jan-10, to lugnet.cad)
|
| |
| | Re: LEGO's Internal colour palette
|
|
Thanks for the heads up Tim. Looks like that is a list of the colors that are currently in production; as it is almost 100 colors short of the complete historical list. Also, they seem to match closest to the colors found in the instruction manuals (...) (15 years ago, 29-Jan-10, to lugnet.cad)
|
| |
| | LEGO's Internal colour palette
|
|
Hi guys, Not sure if this is really that interesting but I figured I should give a heads up to .cad. TLG have released their internal colour pallette (URL) Good luck finding something to do with it ;) Tim (15 years ago, 28-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: Instead of ~Moved to
|
|
In lugnet.cad, Allen Smith wrote: <SNIP> (...) Depending on their viewpoint and experience with LDraw, different users might argue that either inclusion OR exlclusion can be confusing. By including both in the library and providing a way to identify (...) (15 years ago, 25-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: Problem when rendering custom colors
|
|
(...) I tried to add my custom colors to the lg_color.inc file. It works now This is how my lg_color.inc looks: ___...___ // 0 #declare lg_black = texture { pigment { rgb <33/255, 33/255, 33/255> } finish { lg_solid_finish } } // 1 #declare lg_blue (...) (15 years ago, 23-Jan-10, to lugnet.cad)
|
| |
| | Re: Problem when rendering custom colors
|
|
(...) It looks to me like a texture issue rather than the color itself. I would recommend adding your color directly to the lg_color.inc file. Copy the definition for the existing blue and change nothing but the RGB color values for the pigment. (...) (15 years ago, 22-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: Problem when rendering custom colors
|
|
(...) SNIP (...) I am not very familar with POV-Ray. But could it be that the color 162 is not completely described or that is uses the slope surface here? The problem occur only at that place at the object where the light direct reflect. So I (...) (15 years ago, 22-Jan-10, to lugnet.cad)
|
| |
| | Re: Problem when rendering custom colors [DAT]
|
|
(...) Hello Eric, to further explain my problem Ive rendered a scene. (URL) left part of the fig uses the normal blue (color 1). Teh right part uses my personal color 162 (a darker blue) As you can see, the color 2 part of the torso front looks (...) (15 years ago, 22-Jan-10, to lugnet.cad)
|
| |
| | Re: Problem when rendering custom colors
|
|
(...) It's pretty hard to say what is happening without seeing your files. I need to see the portions of the POV-Ray file which define colors, or the include files which show colors. You could also post an example *.ldr file. Eric Albrecht (15 years ago, 22-Jan-10, to lugnet.cad)
|
| |
| | Problem when rendering custom colors
|
|
Hello, Im new to LUGNET. Although I use LDRAW yet for some years, I recently got interested ib creating and using custom parts (especially minifig torsos). I've created some easy to use template so I can create custom minifig torsos via bmp2ldraw32. (...) (15 years ago, 22-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
In lugnet.cad, Chris Dee wrote: snip (...) The zip archive's chief virtue is not its familiarity, but its cross-platform portability. It's very important to maintain that. (...) I fixed that Bricksmith bug about a year and a half ago, so you don't (...) (15 years ago, 22-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: LDraw Names for Monorail Parts
|
|
(...) It makes more sense for "Monorail" to be a valid CATEGORY than some of the existing ones, so I added it a while ago. The definitive list is at (URL) Chris (15 years ago, 21-Jan-10, to lugnet.cad.dev, lugnet.trains)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) I think there is some part of your equation that we don't realize/understand? I can view all my LDRAW models without any updating, thanks to the "moved to" concept. The models doesn't become obsolete even though the part numbers are updated. (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) I was going to start my response with "I don't understand", but Orion beat me to it. It is absolutely not necessary to update existing models with the replacement file referred to by the "~Moved to" file, but maybe I am missing something about (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) You should take heart from the fact that this phenomenon has slowed a GREAT deal in recent times, the number of possible renumbers is way way down, and number accuracy is way up. TLG doesn't tend to switch from solid to hollow studs anymore, (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) Hmmm, subparts are used by many parts so I can see how they might be referenced a gazillion times by an extremely large model file like Datsville. (...) What tool makes the movedto.log file that's giving you such trouble? Can it be adjusted to (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) I don't understand what you're saying here, Tore. The ~Moved To files prevent the need to update already existing files by providing a back reference to the old part number. This prevents a part from disappearing from a model simply because (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) Yes, I know my suggested approach has its obvious downsides. But the current system really makes me Yike!, too. When do we reach the point where the downsides of the current system overturn the advantages? I think we've already passed that (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) <snip> (...) (the "fake" number 111 sticks around, and the official design number 2222 points to it) Yikes! So you want everyone stuck with 111 for all eternity? With the current system, I'm free to remove 111.dat if I don't want it, and end (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) <SNIP> (...) The problem is that it doesn't. As I pointed out in my latest post, (URL) , almost every single existing LDraw model file ever made needs to be updated with every parts update realeasd. That has absolutely nothing to do with true (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) For some reason, those 18 "moved to" files in parts\s make a lot of noise for me. I know they shouldn't but they do and I haven't figured out the reason yet. There is another problem. It is kind of subtile, so I don't know if I'm able to (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) Advanced folks could have MovedTo directory and move all the "0 ~Moved To" files there. You can then add MovedTo to MLCad.ini to tell it about the MovedTo directory. You keep the MovedTo files (if you want), MLCad's auto update, and yet not (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: LDDP version 2.1 beta test
|
|
(...) I have not tested version 2.1 yet, but in version 2.0 you could disable polling in the extra menu. Or enable to poll on demand. cu mikeheide (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) Yes, another method will break MLCad's update mechanism. I also like that. But maybe also another solution will work that way, but it has to be implemented. On the other side if we use the proposed way you also will have the latest geometrie (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
Tore, I'm not really seeing the problem in the parts\s directory - there are 18 "moved to" files there. My parts directory has 456 "moved to" files, but there's not really any way around having those -- they serve two purposes: a) provide backwards (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) I'm not much of an expert in this area, but that never stops me from shooting my mouth off! On unix (e.g. Mac), it would be easy enough to use grep/find to find the files that contain "0 ~Moved to" and simply remove them. Cygwin on Windows (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: LDDP version 2.1 beta test
|
|
In lugnet.cad, Philippe Hurbain wrote: SNIP (...) indeed! Also I'd appreciate an option to turn polling off globally and completely would be great. I'm getting sick of getting greeted by tens of Confirm boxes each time I save my part in MLCad and (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
I also agree that the current system is...extravagant. 'litter files' also seems like an appropriate term for the thousands of unnecessary files that clutter my LDraw library. Personnally, I'd like my library to only have actual parts; no ~Moved to (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: LDDP version 2.1 beta test
|
|
Hi Orion, (...) Works fine. (...) Works fine too on everything I tested. (...) OK, indeed inlining works (perhaps I goofed last time). (...) It is. Other things I noticed: - After starting this new version my preferences were again cleared - It (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
