To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cadOpen lugnet.cad in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / *45825 (-100)
  Re: *** MLCad V3.30 ***  [DAT]
 
Hi Michael, (...) I just stumbled on the same problem. This single line is enough to show the problem (Impossible to change the transformation matrix): 1 1 0 0 -25 38 0 0 0 0 -38 0 1 0 48\4-4edge.dat Philo (15 years ago, 9-Feb-10, to lugnet.cad.mlcad)
 
  Re: *** MLCad V3.30 ***
 
Hello Santeri, (...) Could you please save your file in such a case and send it to me for reproduction and testing? That would be of great help! Thanks for reporting! Best regards, Michael (15 years ago, 9-Feb-10, to lugnet.cad.mlcad)
 
  Re: German and Italian language add-on for MLCad 3.30 available
 
"Bernd Broich" <bernd.broich@online.de> schrieb im Newsbeitrag news:KxL26J.Bsw@lugnet.com... (...) Hi, this is realy strange. I've got the version from Willy in advance and it worked. Now I've also downloaded the version from Willys web and that (...) (15 years ago, 9-Feb-10, to lugnet.cad.mlcad)
 
  Re: *** MLCad V3.30 ***
 
Hello Michael (...) I'm currently looking into that. (...) ? I cannot understand. There is no such range, MLCad takes that what comes from LDConfig nothing more, nothing less. Dithered colors originally have been according to the original definition (...) (15 years ago, 9-Feb-10, to lugnet.cad.mlcad)
 
  Re: *** MLCad V3.30 ***
 
Hello Michael, I just want to thank you for the constant work you're doing to develop and upgrade this tremendous tool! Regards (URL) Marco> (15 years ago, 9-Feb-10, to lugnet.cad.mlcad, FTX)
 
  Re: "Dither" colors in patterned/sticker parts
 
(...) So, to expand a little on my earlier comments -- I think it would be reasonable, for now, to allow dithered colors1 in pattern/sticker parts and disallow RGB codes, with the thought that work would go forward on defining a texture mapping (...) (15 years ago, 9-Feb-10, to lugnet.cad.dat.parts, FTX)
 
  Re: "Dither" colors in patterned/sticker parts
 
(...) I heartfully agree !!! Philo (15 years ago, 9-Feb-10, to lugnet.cad.dat.parts, FTX)
 
  Re: "Dither" colors in patterned/sticker parts
 
(...) I would go for this option. I'm not a fan of allowing RGB values in official part files, I'd rather keep it to color codes. However, if there could be a standard for texture mapping patterns & stickers (and parts made by mixing multiple colors (...) (15 years ago, 9-Feb-10, to lugnet.cad.dat.parts, FTX)
 
  Re: "Dither" colors in patterned/sticker parts
 
(...) I hadn't thought about this, but I kinda like the idea. The original LDRAW defined values for all color codes, and some of the newer codes were assigned because they are a variation/change from existing colors. The downside of this idea is (...) (15 years ago, 9-Feb-10, to lugnet.cad.dat.parts, FTX)
 
  Re: German and Italian language add-on for MLCad 3.30 available
 
"Marco Tagliaferri" <mtagl@web.de> schrieb im Newsbeitrag news:KxKBDq.o9F@lugnet.com... (...) Hallo Willy, Marco, ich habe das gleiche Problem mit der deutschen DLL. Gruß Bernd (15 years ago, 9-Feb-10, to lugnet.cad.mlcad)
 
  Re: BBC Tech Know: The dreams that bricks are made of
 
(...) Very nice! I especially like the LDraw bits, good stuff from Chris Dee. (...) Be sure to watch the video -- there's a neat bit at the end about how they used LEGO for a conceptual model of the Falkirk Wheel, not included in the text. Steve (15 years ago, 9-Feb-10, to lugnet.loc.uk, lugnet.cad, FTX)
 
  Re: "Dither" colors in patterned/sticker parts
 
Hello, "Travis Cobbs" <tcobbs@REMOVEgmail.com> schrieb im Newsbeitrag news:KxEAq2.86J@lugnet.com... (...) I used dithered colors in the "Flag 2x2 with Goblets and Grapes" (2335p40). So in this case no other color would match the silver or gold color (...) (15 years ago, 9-Feb-10, to lugnet.cad.dat.parts)
 
  Re: LPub 4.0.0.4 CLEAR / BUFEXCHG issue
 
(...) Not yet, although I've seen you can do it. Trying to get the basic instructions and BOM made, then I'll look at all the wizzy extras (like cover pages) LPub 4 is very productive - (URL) - not bad seeing as I only started the layouts last Wed (...) (15 years ago, 9-Feb-10, to lugnet.cad)
 
  French language add-on for MLCad 3.30 available
 
Hi folks, I upgraded the French language add-on for MLCad version 3.30. You'll find the .zip-files along with a tutorial for how to change the language interface here: (URL) Regards. Marc Klein (15 years ago, 9-Feb-10, to lugnet.cad.mlcad)  
 
  Re: LPub 4.0.0.4: Submodels in parts list?
 
(...) Great! Thanks, Kevin! Longing for the next release... Philo (15 years ago, 9-Feb-10, to lugnet.cad)
 
  Re: German and Italian language add-on for MLCad 3.30 available
 
(...) Hello Willy, (...) thanks for that fast update! (...) The german dll seems also quite short (380kB) wheras the italkian one has more than 700kB. Could you please check... Regards Marco (15 years ago, 9-Feb-10, to lugnet.cad.mlcad)
 
  Re: LPub 4.0.0.0.4 BOM issue with BUFEXCHG
 
(...) 0 !LPUB PLI BEGIN SUB 3021.DAT 1 This one was broken too. Kevin (15 years ago, 9-Feb-10, to lugnet.cad)
 
  Re: LPub 4.0.0.4 CLEAR / BUFEXCHG issue
 
(...) Amen to that! (...) Yeah, LPub 4 is a bit different that LPub 2. It can be a lot more fun. Did you try resizing PLIs or BOMs? You can do it with the mouse. Kevin (15 years ago, 9-Feb-10, to lugnet.cad)
 
  Re: LPub 4.0.0.4: Submodels in parts list?
 
(...) <snip> (...) I have found and fixed this one too. (...) Kevin (15 years ago, 9-Feb-10, to lugnet.cad)
 
  Re: *** MLCad V3.30 ***
 
(...) That's something that has been around in the last version too. (...) I have another bug... in some cases I cannot manipulate the rotation matrix because the angle value in the vector field (which I never saw much use of anyhow) is something (...) (15 years ago, 8-Feb-10, to lugnet.cad.mlcad)
 
  Re: *** MLCad V3.30 ***
 
(...) This is excellent news Michael! Thank you so much for all of your hard work. We couldn't ask for anything more, especially since you do this for free! I hope that you know how much the entire community appreciates your effort! Many thanks, (...) (15 years ago, 8-Feb-10, to lugnet.cad.mlcad)
 
  Re: *** MLCad V3.30 ***
 
(...) Now that I have installed MLCad and read all informations I hope we can get an update soon. I have two reason: 1) Implementation of language support is different to what we have implemented. 2) I miss the "dithered" colours. Not the dithered (...) (15 years ago, 8-Feb-10, to lugnet.cad.mlcad)
 
  Re: *** MLCad V3.30 ***
 
(...) Thank you very much for updating MLCad to support LDConfig.ldr. I hope that this will not be the last update to this wonderful application. Now I have to see how it works. cu mikeheide (15 years ago, 8-Feb-10, to lugnet.cad.mlcad)
 
  Re: LPub 4.0.0.4 CLEAR / BUFEXCHG issue
 
(...) Pleasure. (I write software for a living and keep threatening to change the "on-hold music" to "If *you* can't replicate it, *I* can't fix it!") LPub 4 with LDView 4.1 has made making instructions fun again - from MLCad design/build suitable (...) (15 years ago, 8-Feb-10, to lugnet.cad)
 
  Re: *** MLCad V3.30 ***
 
(...) You just ground my yawn to a halt. LDConfig support is something I've been wanting for a *very* long time. Now I can define my own background colour by using the unused colour 31. :P Love it. -Santeri (15 years ago, 8-Feb-10, to lugnet.cad.mlcad)
 
  Re: LPub 4.0.0.4 CLEAR / BUFEXCHG issue
 
(...) <snip> Hi William, Once again, thanks for the simple example in the form of LDraw file. I have this one fixed. Kevin (15 years ago, 8-Feb-10, to lugnet.cad)
 
  Re: *** MLCad V3.30 ***
 
(...) BTW, this really deserves being posted on lugnet.announce as well!! (15 years ago, 8-Feb-10, to lugnet.cad.mlcad)
 
  Re: German and Italian language add-on for MLCad 3.30 available
 
(...) I would like to contribute to getting the Spanish language pack ready for MLCad 3.30. Please let me know how I can do this. Also, the search function doesn't work in any of the 3.20 language packs. Has that problem been fixed in 3.3? Regards, (...) (15 years ago, 8-Feb-10, to lugnet.cad.mlcad)
 
  Re: *** MLCad V3.30 ***
 
(...) Thank you for this long awaited release! Now let's spread the word! Jetro (15 years ago, 8-Feb-10, to lugnet.cad.mlcad)
 
  German and Italian language add-on for MLCad 3.30 available
 
Hi folks, I upgraded the German and Italian language add-on for MLCad. Both add-ons are now fit for version 3.30. You'll find the .zip-files along with a tutorial for how to change the language interface at: German - (URL) - (URL) w. (15 years ago, 8-Feb-10, to lugnet.cad, lugnet.announce, lugnet.cad.mlcad) ! 
 
  Re: *** MLCad V3.30 ***
 
You made my day! Thanks, Michael!!! Philo (15 years ago, 8-Feb-10, to lugnet.cad.mlcad)
 
  *** MLCad V3.30 ***
 
Hi, I would like to announce that I've just released a new version of MLCad! MLCad V3.30 What's new: - Development environment was changed to Visual Studio 2005 - Support for color definitions in LdConfig.ldr - Empty lines are no longer removed (for (...) (15 years ago, 8-Feb-10, to lugnet.cad.mlcad) !! 
 
  Re: "Dither" colors in patterned/sticker parts
 
(...) I have authored patterned parts, and for me this is the only viable option. This has worked just fine for the past decade, and I don't see any good reason why it should be broken. The second option (using 0x2RRGGBB) would just be very (...) (15 years ago, 8-Feb-10, to lugnet.cad.dat.parts, FTX)
 
  Re: "Dither" colors in patterned/sticker parts
 
(...) I didn't get it right at all, but now I think I do. It isn't an issue here and, believe it or not, I'm cool with it. :) (...) Good! :) (...) I'm glad that at least I'm not alone with this opinion. :) /T (15 years ago, 7-Feb-10, to lugnet.cad.dat.parts)
 
  Re: Technic Gear 42 Tooth (744.dat) issue?
 
(...) Works fine for me. But the 42z gear is part 644 and 744 is a "moved to" file on my system William (15 years ago, 7-Feb-10, to lugnet.cad.mlcad)
 
  Technic Gear 42 Tooth (744.dat) issue?
 
Anyone else have trouble displaying Technic Gear 42 Tooth (744.dat) in MLCad? Be careful, on my system, it causes an immediate hard crash of MLCad, losing any changes in your dat file! I'm pretty sure that it's the first time that I've ever seen (...) (15 years ago, 7-Feb-10, to lugnet.cad.mlcad)
 
  Re: "Dither" colors in patterned/sticker parts
 
(...) Two things. First of all, is Maersk Blue hard-coded into any part files? I would expect parts that show up in Maersk Blue to have color 16 encoded in the file, and the user to select Maersk Blue as the parts' color when building a model. Since (...) (15 years ago, 7-Feb-10, to lugnet.cad.dat.parts, FTX)
 
  LPub 4.0.0.0.4 BOM issue with BUFEXCHG  [DAT]
 
See below I would expect the BOM to contain 6 different coloured 2x3 plates, but the last two (added after the BOM END) are ignored - in fact with a very big file everything after the BOM END is ignored (almost as if the BOM END isn't seen) Also, I (...) (15 years ago, 7-Feb-10, to lugnet.cad)
 
  Re: "Dither" colors in patterned/sticker parts
 
(...) I don't know if I got that right. Isn't Maersk Blue one of those part colors most wrongfully and misleadingly labeled as a "dithered" color? (...) I suggest the 0x2RRGGBB form is recommended for less "basic"/established pattern and sticker (...) (15 years ago, 7-Feb-10, to lugnet.cad.dat.parts, FTX)
 
  LPub 4.0.0.4 CLEAR / BUFEXCHG issue  [DAT]
 
LPub 4.0.0.4 crashes if there is a CLEAR and a BUFEXCHG in the same MULTI-STEP group Two files below, first one is OK, second one crashes on page 2 0 FILE NoCrash.ldr 0 NoCrash 0 NAME: NoCrash.LDR 0 AUTHOR: MLCAD 0 UNOFFICIAL MODEL 0 !LPUB (...) (15 years ago, 6-Feb-10, to lugnet.cad)
 
  Re: Dungeon Delver: That Frog...
 
(...) Wow. I'm glad I posted my little picture, if for no other reason than to bring your amazing work to light again. I only get the chance to pop into Lugnet once in a while now, and had never seen this scnner of yours. It would be pretty amazing (...) (15 years ago, 6-Feb-10, to lugnet.cad)
 
  Re: "Dither" colors in patterned/sticker parts
 
(...) I'm not much of a part author, so my opinion probably counts for even less than usual here, but I actually find myself agreeing with Willy on a issue involving colors. That never happens! ;) But heck, who can argue against freedom and (...) (15 years ago, 6-Feb-10, to lugnet.cad.dat.parts)
 
  Re: "Dither" colors in patterned/sticker parts
 
(...) It would be very interesting which applications can not work with the (RGB colors (of the form 0x2RRGGBB)). Are they useful/necessary/developed? If someone has those application to test and make a summary of that would be great. cu mikeheide (15 years ago, 6-Feb-10, to lugnet.cad.dat.parts, FTX)
 
  Re: "Dither" colors in patterned/sticker parts
 
(...) For what it counts, I'd go for: * Explicitly disallow "dither" colors in all official parts, but allow RGB colors (of the form 0x2RRGGBB) in their place in patterned/sticker parts. This solution would give me the most freedom. I could just (...) (15 years ago, 6-Feb-10, to lugnet.cad.dat.parts)
 
  Re: LPub 4.0.0.4 CLEAR issue
 
(...) Hi William, Welcome to LPub 4.0! Its a bit different, eh? Your expectations for CLEAR are very reasonable. <snip> Thanks for the wonderfully simple example. I made a one line fix for this. After I get the "submodel in PLI" problem fixed, you (...) (15 years ago, 6-Feb-10, to lugnet.cad)
 
  Re: LPub 4.0.0.4: Submodels in parts list?
 
(...) I have found and fixed this one. (...) With it fixed, this should be fixed too. (...) I'll work on this next. (...) Kevin (15 years ago, 6-Feb-10, to lugnet.cad)
 
  "Dither" colors in patterned/sticker parts
 
Please read and respond to this message if you are a parts author, particularly if you have authored any patterned or sticker parts. The LSC is trying to come up with rules for colors for both LDConfig.ldr and official parts. We are having an (...) (15 years ago, 6-Feb-10, to lugnet.cad.dat.parts, FTX)  
 
  LDraw.org Parts numbering scheme for parts with unknown numbers.
 
The LSC has just ratified the LDraw.org Parts numbering scheme for parts with unknown numbers. It should allow to add parts to the library where the part number is not known. As the systematic that is used up to now has reached its limits this (...) (15 years ago, 5-Feb-10, to lugnet.cad, lugnet.announce)
 
  LPub 4.0.0.4 CLEAR issue  [DAT]
 
LPub 4.0.0.4 doesn't seem to honour the CLEAR command across multi-steps after the page after the clear (see sample below) 7 bricks in a row with steps between - A B C D E F G in three multi-step groups with a CLEAR after group 1 - (A B C) CLEAR (D (...) (15 years ago, 5-Feb-10, to lugnet.cad)
 
  Re: LPub 4.0.0.4: Callout placement
 
(...) Just started using LPub 4 (last used LPub 2!) and came across this. What seems to happen is that the callout placement meta-command *is* created, just after the callout end meta-command. So after moving the callout with the mouse you need to (...) (15 years ago, 5-Feb-10, to lugnet.cad)
 
  Re: Lego City Policeman and LdrDat2Dxf utility
 
(...) The tool is downloadable from (URL) (15 years ago, 4-Feb-10, to lugnet.cad)
 
  Updated Unofficial parts pack for LeoCAD
 
Following LeoCAD official parts update ((URL) here is an new version of my unofficial parts pack. It contains all LDraw unofficial parts available as of February 4, 2010. (URL) (15 years ago, 4-Feb-10, to lugnet.announce, lugnet.cad.leocad)
 
  Re: LEGO's Internal colour palette
 
For those capable of updating LDConfig, please add/change these LEGO colors to these existing colors: (...) No match. The correct color to match to already has an entry, that may also be correct in some capacity. Someone will need to go through all (...) (15 years ago, 3-Feb-10, to lugnet.cad)
 
  Re: Lego City Policeman and LdrDat2Dxf utility
 
(...) Interesting, I somehow missed the announcement of this tool. Did you try Rolf's Lugnet email address? (see (URL) the homepage is still available through Google cache: (URL) (15 years ago, 1-Feb-10, to lugnet.cad)
 
  Re: LEGO's Internal colour palette
 
--snip-- (...) Yeah that would be me speculating on things I haven't read properly... Please ignore. Tim (15 years ago, 1-Feb-10, to lugnet.cad)
 
  Lego City Policeman and LdrDat2Dxf utility
 
Hi everyone, I've started putting a website together with Lego models in various formats. My latest addition is a Lego Policeman. See following link for details: (URL) tried to provide a number of different model format downloads including 3ds, obj, (...) (15 years ago, 31-Jan-10, to lugnet.cad)
 
  Re: What's going on with 59443.dat?
 
(...) Yes, Philo is right. We try to release modifications/improvements to related official parts in the same parts update. That is one reason why some Certfied files get left on the Parts Tracker at each update. Chris (15 years ago, 31-Jan-10, to lugnet.cad, FTX)
 
  Re: Dungeon Delver: That Frog...
 
(...) (full story of its birth: (URL) (15 years ago, 31-Jan-10, to lugnet.cad)
 
  Re: LEGO's Internal colour palette
 
(...) If you can get Peeron/LDraw and Bricklink to agree on all color names, even if they don't match the official names, you win a freaking prize. (...) Yeah...it's hard enough for most people to keep track of a lot of the more common colors as it (...) (15 years ago, 31-Jan-10, to lugnet.cad)
 
  Re: LEGO's Internal colour palette
 
(...) Makes sense. That did look like it was a fairly new color, though the first instance I can recall of that color was the natives from the Indiana Jones graveyard set (the one with the new motorcycle fairing) (...) The what now? Which sets would (...) (15 years ago, 31-Jan-10, to lugnet.cad)
 
  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)


Next Page:  5 more | 10 more | 20 more | 100 more

Redisplay Messages:  All | Compact

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR