 | | Re: LPub 4 Callouts (and other questions)
|
|
(...) OK, good tip for other users too, to not use dots in filenames. (...) I believe you have to create the submodels individually indead. That is what I always do anyway. (...) I'm afraid I do not have the exact answer to that, but I believe LPub (...) (15 years ago, 27-Oct-09, to lugnet.cad)
|
| |
| | Re: LPub 4 Callouts (and other questions)
|
|
(...) Thanks Jaco. Through the process of doing it manually and a lot of other trial and error, I discovered the problem. My submodels had a dot (.) in the title. This seemed to confuse LPub and result in the problems I saw. I converted all the dots (...) (15 years ago, 26-Oct-09, to lugnet.cad)
|
| |
| | Re: LDraw for teaching, drawings for production?
|
|
(...) I guess you could use any tool that can produce images from LDraw models, but for print LDView would be the best choice. You can add text to the picture in the way Phile suggested, but any photo editing tool or DTP program can do that. I think (...) (15 years ago, 26-Oct-09, to lugnet.cad)
|
| |
| | Re: LPub 4 Callouts
|
|
(...) Eric, I do not experience any problems in creating callouts. Positioning them is sometimes a bit tricky. Adding them manually is always a good thing to try. The syntax is this: 0 !LPUB CALLOUT BEGIN 1 x x x x x x submodel.ldr 0 !LPUB CALLOUT (...) (15 years ago, 26-Oct-09, to lugnet.cad)
|
| |
| | LPub 4 Callouts
|
|
I'm trying out LPub 4 for the first time and am having some trouble. (Note that I am a veteran of LPub 3). Every time I attempt to make a submodel into a callout, the program simply crashes. Has anyone else used the callout function successfully or (...) (15 years ago, 25-Oct-09, to lugnet.cad)
|
| |
| | Re: LDraw for teaching, drawings for production?
|
|
(...) One possibility is to add the text as a postprocessing step with an image editing program. Or you may embed the text as LDraw stickers, created with txt2dat ((URL) See for example the color chart I created: (URL) 3) printing of part lists etc (...) (15 years ago, 23-Oct-09, to lugnet.cad)
|
| |
| | LDraw for teaching, drawings for production?
|
|
Hello A friend of mine is doing training for production management & quality & stuff. She had found lego and realised that Ldraw is good and easy to use, and lego is easy to play with. But 2 questions: 1) is is possible to print drawings, for (...) (15 years ago, 23-Oct-09, to lugnet.cad)
|
| |
| | 4721 - Tyre Minifig Bicycle has wrong part number
|
|
Folks, Going through the L(EGO)Draw parts at picture 3 (URL) came across 2807. The LEGO database says: MINI CYCLE, TYRE 14 X 2 [1996-01] Use Design: 2807 which is also the number on BL. Peeron and LDdraw uses 4721 instead: (URL) a shrunken 70162 - (...) (15 years ago, 23-Oct-09, to lugnet.cad, lugnet.cad.dat.parts)
|
| |
| | 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: 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)
|
