| | calc_z4.c (Was: Math Problem Again)
|
|
(...) Sorry guys, just wanted to store this function in a safer place than my hard drive. :) I just don't want to remake it again...! Feel free to copy/paste/edit/port if you need it! /Tore // calc_z4 by Tore Eriksson // credits to Ronan Webb for (...) (15 years ago, 22-Oct-09, to lugnet.cad.dev)
|
|
| | Re: Voxelizer pluging for Blender to design Nathan Sawaya's style sculptures
|
|
(...) the site is not accessible any more... where does can I find this plugin? thank you Cristian (15 years ago, 22-Oct-09, to lugnet.cad.dat.ideas)
|
|
| | Re: ldlister 0.1
|
|
(...) Heh, that was it. Thanks for reminding me :-) In lugnet.cad, Travis Cobbs wrote: (...) Maybe, but this is Tcl in which case the right answer is to use [fconfigure $fp -translation auto crlf] and remove the \r from the output string (it makes (...) (15 years ago, 20-Oct-09, to lugnet.cad)
|
|
| | Re: Do these parts exist in LDRAW?
|
|
(...) You're spot-on Santeri. And the reason I said one might technically stick to the "correct" numbers is two-fold: on the off-off-off chance some renderer were to ever render based on the type of plastic (ABS versus polycarbonate), and also (...) (15 years ago, 20-Oct-09, to lugnet.cad)
|
|
| | Re: Color Manger - Program Testers Wanted
|
|
Sorry, found a small bug in the program. The custom edge colors had their second alpha value set to 0, so they looked fuzzy. Version 3.1... Download page: (URL) W. (15 years ago, 19-Oct-09, to lugnet.cad)
|
|
| | Re: ldlister 0.1
|
|
(...) If there's a Linux version, the best thing to do is to open the file as a binary file and continue using \r\n as the line ending in the source code. In other words, leave your text output code alone, but change the file open call to use binary (...) (15 years ago, 19-Oct-09, to lugnet.cad)
|
|
| | Re: ldlister 0.1
|
|
(...) Maybe you need the extra \r to get DOS file endings when running the linux version of ldlister? (15 years ago, 19-Oct-09, to lugnet.cad)
|
|
| | Re: ldlister 0.1
|
|
(...) :-) (...) Now that I look at the code, it does have a "\r" at the end of the string where it puts the part into the parts list... I wonder what was I thinking at the moment. On the (bit further away) works is a feature which lets primitives (...) (15 years ago, 19-Oct-09, to lugnet.cad)
|
|
| | Re: Do these parts exist in LDRAW?
|
|
(...) Nope, 50746.dat is merely an alias to 54200.dat and as such the parts appear identical in MLCad (and in any other editor one might use). If I recall correctly, it was something to do with the plastic used to mold the parts but don't trust me. (15 years ago, 19-Oct-09, to lugnet.cad)
|
|
| | Re: L(EGO)Draw parts - 3rd batch
|
|
(...) And I'll start on the 57565.dat as soon as I've finished the competition cannon. I've got the front cover, trigger and spring all three done and it doesn't look like it'll take too long for me to model the bulk of the cannon so I guess it'll (...) (15 years ago, 19-Oct-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: Do these parts exist in LDRAW?
|
|
(...) It's primarily to capture all the part numbers from LEGO. So if someone finds # XXXXX molded on their part, they'll be able to use that number in LDraw models. Steve (15 years ago, 19-Oct-09, to lugnet.cad)
|
|
| | Re: Do these parts exist in LDRAW?
|
|
(...) What is the purpose of having two versions? I assume that the transparent version has all the internals accurately modeled so you can see them when light passes through, but why not just use this one even when it is opaque? I am obviously (...) (15 years ago, 19-Oct-09, to lugnet.cad)
|
|
| | Re: L(EGO)Draw parts - 3rd batch
|
|
(...) Good point! Changed. w. (15 years ago, 19-Oct-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: L(EGO)Draw parts - 3rd batch
|
|
(...) Great, thanks! "If you wanna contribute just download the file you want work on, but don't forget to email the LDraw Administration Team telling the part number your working on - your name will be associated with the part in order to avoid (...) (15 years ago, 19-Oct-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: ldlister 0.1
|
|
(...) One small nit: in the output file, it seems the lines are terminated by a three-byte sequence 0D0D0A (CR-CR-LF). This sequence confuses WordPad, which shows the resulting PARTS.LST as all one line. Oddly, Notepad (which is confused by files (...) (15 years ago, 19-Oct-09, to lugnet.cad)
|
|
| | Re: L(EGO)Draw parts - 3rd batch
|
|
(...) I've uploaded the .dats to my website (the upload module at LDraw.org would have me driven crazy if I had to upload 1200 files one by one). The links can be found at the wiki. w. (15 years ago, 19-Oct-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: Do these parts exist in LDRAW?
|
|
(...) That comment is an oversimplification (and I helped put it there, so I feel qualified to denegrate the statement a bit), but Ronald is correct in that technically one should model transparent copies of this part in 50746 (without fail), and (...) (15 years ago, 19-Oct-09, to lugnet.cad)
|
|
| | Re: LDRAW color question
|
|
(...) Trans dark orange is 182, light bluish grey is 71, dark bluish grey is 72, dark green is 288. And yes, chrome is 383 and trans-black is 40. They're all defined in LDConfig.ldr - you might want to look there. (15 years ago, 19-Oct-09, to lugnet.cad)
|
|
| | Re: LDRAW color question
|
|
(...) I can't remember all of them off the top of my head, but I believe that trans-black is LDraw 40 and chrome silver is LDraw 383. HTH Dave! (15 years ago, 19-Oct-09, to lugnet.cad)
|
|
| | Re: Do these parts exist in LDRAW?
|
|
(...) "54200 is used for moulding opaque parts, 50746 for transparent parts." (15 years ago, 18-Oct-09, to lugnet.cad)
|