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