 | | Planes & Requirements for a generic download-tool
|
|
Hy, after exchanging some mails with Tim Courtney, I'm planing to write a generic download-utility for LDraw/LEdit stuff. The basic idea behind is to have a utility which can be used to download a specific program and/or the part libraries. Also an (...) (24 years ago, 13-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Can LDAO do this? (was: anyone interested in rendering for me?)
|
|
(...) I've simply used the POV-Ray 3.1 manual, which has a tutorial on most major features, and a nice reference. It can be gotten from (URL) (24 years ago, 13-Jul-00, to lugnet.cad.ray, lugnet.cad.dev)
|
| |
| | Re: Category Statement
|
|
But this also tells me that I will wait before implementing anything regarding this topic! Michael Manfred Moolhuysen <moom@nospamchello.nl> schrieb in im Newsbeitrag: FxJL77.4oo@lugnet.com... (...) basis (...) instructions. (...) (24 years ago, 13-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Part Command (1)
|
|
Ok, thanks - than I will restrict the possible file-names when entering for mpd to 8.3 notation to be compatible. Michael Steve Bliss <blisses@worldnet.att.net> schrieb in im Newsbeitrag: i06pms8b3fjj71uns1jo...4ax.com... (...) the (...) (24 years ago, 13-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: question on naming - pirate guns vs. modern guns
|
|
(...) Which wouldn't explain an arquebus, the muzzle-loading precursor to the musket. I believe the difference between the two when both were used was that the musket had a longer barrel and fired a heavier ball (armor could be "proof" against an (...) (24 years ago, 12-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: question on naming - pirate guns vs. modern guns
|
|
(...) Not all muskets have a belled muzzle. Civil War era muskets were non-belled, making them much more accurate. I believe "musket" refers to muzzle loading, as a butt loading rifle was known as a carbine. Sorry, I'm a stickler for history. -John (...) (24 years ago, 12-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Can LDAO do this? (was: anyone interested in rendering for me?)
|
|
(...) The main file for, say, SKETCH.DAT, shows up as a union block named sketch_dot_dat. I suppose that a post-l3p tool could just read in the POV output file and parse this union and insert the clock-checking logic. The same tool could also spit (...) (24 years ago, 12-Jul-00, to lugnet.cad.ray, lugnet.cad.dev)
|
| |
| | Re: Can LDAO do this? (was: anyone interested in rendering for me?)
|
|
(...) Yeah, and the docs aren't the best, either. Do you know of any decent tutorials for the 3.1 language? Online or book would be great, but all I've seen is stuff for 3.0... Cheers, - jsproat (24 years ago, 12-Jul-00, to lugnet.cad.ray, lugnet.cad.dev)
|
| |
| | Re: Can LDAO do this? (was: anyone interested in rendering for me?)
|
|
(...) Yeah, you got it! I used the POV-Ray clock to make an animation a year ago, so I learned a bit about it. I'm sure you've all seen it before: (URL) I get the time, I'm planning to make another animation, but don't hold your breath! ;-) (...) (...) (24 years ago, 12-Jul-00, to lugnet.cad.ray, lugnet.cad.dev)
|
| |
| | Re: Can LDAO do this? (was: anyone interested in rendering for me?)
|
|
(...) I suppose some of you may want to try this out, so do something like this with your POV-Ray file, as generated by L3P. Identify the portion of the file where the "0 STEP" lines are present and add #if and #end statements like this: // [DAT (...) (24 years ago, 12-Jul-00, to lugnet.cad.ray, lugnet.cad.dev)
|
| |
| | Re: Can LDAO do this? (was: anyone interested in rendering for me?)
|
|
(...) Selective rendering of parts based upon the animation clock value or something like that? Cool, I didn't know POVRay could do that. Is it a preprocessor macro thingy, or something else? I was thinking, however, more along the lines of being (...) (24 years ago, 12-Jul-00, to lugnet.cad.ray, lugnet.cad.dev)
|
| |
| | Re: Can LDAO do this? (was: anyone interested in rendering for me?)
|
|
(...) It is much more sane to use POV-Ray's animation system to do this automatically. That way, you could issue one POV-Ray command and render all the instruction steps in one run, using only one POV-file. I have suggested this to Lars C Hassing, (...) (24 years ago, 12-Jul-00, to lugnet.cad.ray, lugnet.cad.dev)
|
| |
| | Re: Can LDAO do this? (was: anyone interested in rendering for me?)
|
|
(...) Sweet! Since POV renderings take a while, and that you'd need a POV for each step anyway, I'm wondering if all the L3P output could be saved, e.g. STEP0001.POV, STEP0002.POV, etc. Cheers, - jsproat (24 years ago, 12-Jul-00, to lugnet.cad.ray, lugnet.cad.dev)
|
| |
| | Re: question on naming - pirate guns vs. modern guns
|
|
(...) Hmm. Possibly. I thought a "musket" was a gun with a belled/flared muzzle (among other characteristics). Typical usage is for long-barrelled weapons. (...) I guess I'd be OK with that. Steve (24 years ago, 12-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Can LDAO do this? (was: anyone interested in rendering for me?)
|
|
(...) Actually, it shouldn't take much change to LDAO. Just an additional loop to spit out a DAT file for each step, then use L3P to translate it, and POV-Ray to render it. Steve (24 years ago, 12-Jul-00, to lugnet.cad.ray, lugnet.cad.dev)
|
| |
| | Re: Part Command (1)
|
|
(...) Like Rui said, LDraw only uses 8.3, and other programs (and part authors) should do the same. *Especially* for part-files. (...) Yes. Also, either format allows the inclusion of path information as part of the file name. Steve (24 years ago, 12-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Partial list of parts for 2000-02 Update
|
|
(...) Yep. (...) A. Because the barrel is a legitimate and common point for minifig to grip their muskets. B. Because it's a more standard orientation than going for the "grip". Maybe I forgot, but I meant to also ask you to insert a comment-line, (...) (24 years ago, 12-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Part Command (1)
|
|
(...) As far as I know, they should be compatible with Ldraw, which means compatible with DOS or more preciselly filenames must have a name like "8.3" ie, 8 characters for name, and 3 for the extension. Besides this, you can also use regular DOS (...) (24 years ago, 12-Jul-00, to lugnet.cad.dev)
|
| |
| | Part Command (1)
|
|
How should the file name in the part command be handled? Should it be one word only (e.g. xyz.dat) or can it included spaces (e.g. Special Part.dat)? Is this handling the same for dat and mpd files? Michael (24 years ago, 12-Jul-00, to lugnet.cad.dev)
|
| |
| | Can LDAO do this? (was: anyone interested in rendering for me?)
|
|
(...) What would be better is if there were a utility to help automate POVRAY rendering of MOC instruction books, kinda like what LDraw Add-On does for LDLite instruction renderings. Steve, do you know how much change LDAO would need in order to do (...) (24 years ago, 11-Jul-00, to lugnet.cad.ray, lugnet.cad.dev)
|
| |
| | Re: Category Statement
|
|
(...) By all means! I was secretly hoping that my questions would lead to such a type of action. Feel free to rearange them into a clear set of instructions. You've earned my gratitude again, M. Moolhuysen. (24 years ago, 11-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: question on naming - pirate guns vs. modern guns
|
|
(...) Isn't "Musket Pistol" an oxymoron? Why not just name them Minifig Flintlock Pistol Minifig Flintlock Musket Minifig Revolver eric (24 years ago, 11-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: question on naming - pirate guns vs. modern guns
|
|
(...) I'm fairly happy with keeping the names short, and introducing longer names when (if) it becomes necessary. Minifig Revolver is (currently) clear Minifig Rifle is clear Minifig Musket is not clear So Minifig Musket Longarm (or whatever other (...) (24 years ago, 11-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Partial list of parts for 2000-02 Update
|
|
(...) No need. Now that I've gotten LDAO installed correctly (KNOCK ON WOOD), I can take care of the musket myself. It'll take a day or so, I'm foguring. Thanks, though. BTW: IIRC, you asked that I re-orient the musket so that the *barrel* is the (...) (24 years ago, 11-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Category Statement
|
|
In lugnet.cad.dev, Manfred Moolhuysen wrote: Moving this one to the top: (...) CATEGORY provides a method to place all parts in a comprehensive classification system. KEYWORDS provides a method to associate potential search-terms with a part. (...) (24 years ago, 11-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Partial list of parts for 2000-02 Update
|
|
(...) Sorry about the employment thing. I know what its like to be fired. If you want, I can reorient the longarm musket part. I'll do it the same way you would - with LDAO. Steve (24 years ago, 11-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: question on naming - pirate guns vs. modern guns
|
|
(...) *either* the "Pirate Musket Pistol" *or* the "Wild West Pistol Revolver"... You *don't* know for *certain* just by looking at that name... (Continued below.) (...) By using "modern" and "archaic", there would be *no* ambiguity: an *archaic* (...) (24 years ago, 11-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: question on naming - pirate guns vs. modern guns
|
|
How about just minifig gun musket minifig gun pistol minifig gun revolver and minifig gun rifle (24 years ago, 10-Jul-00, to lugnet.cad.dev)
|
| |
| | question on naming - pirate guns vs. modern guns
|
|
OK, I've done DAT files for three of the four firearms that LegoCo produces for Lego minifigs (the pirate pistol, the pirate musket, and the wild west revolver), and I still have questions on how we should name these weapons. Both the wild west guns (...) (24 years ago, 10-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Partial list of parts for 2000-02 Update
|
|
(...) Yeah, about that... I had LDAO loaded on my PC at the office. I just recently got internet access at home. Having been fired recently -- and thus no more access to my work PC with all the other programs loaded -- I've been uploading programs, (...) (24 years ago, 10-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Partial list of parts for 2000-02 Update
|
|
(...) Fair enough. I did only completely change the name. BTW, the word "Accessory" shouldn't be there. It should just be X59.DAT Minifig Sword Large (...) Not exactly, but that's a part of the big picture. Basically, the theme-based categories (...) (24 years ago, 10-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: [somewhat of Topic] Connecting an Arm to a Gear [DAT]
|
|
Since none replyed, maybe you didn't get the ideia ! So, here is my best setup so far, does anyone have any other usefull setup. 0 Untitled 0 Name: Arm.dat 1 0 0 -46 0 1 0 0 0 0 -1 0 1 0 32073.DAT 1 7 0 -46 0 0 0 -1 0 1 0 1 0 0 3648.DAT 1 0 0 -36 (...) (24 years ago, 10-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Category Statement
|
|
(...) In lugnet.cad.dev, Steve Bliss writes: (...) I would like to add those headers to my part files. I remember I've asked this before, I did get an answer back then, but it wasn't very clear to me. I discontinued the thread, because I didn't have (...) (24 years ago, 9-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Category Statement
|
|
I thought about a new feature in MLCad where the user can define his own groups to be show in the part preview and in the part tree. Each group will have a certain rule (search criteria) which assigns parts to this groups. The part assignment is (...) (24 years ago, 8-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Partial list of parts for 2000-02 Update
|
|
(...) I have a beef with this. The NAME I gave this was "Castle Greatsword" (not "Minifig Accessory Sword Large"). Now, if I understand correctly, you want to eventually migrate all minifig accessories *away* from the "Castle" (and "Pirate") (...) (24 years ago, 8-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: New Parts Category: Cockpit
|
|
(...) Does anyone else see things the same way as Jonathan does? It's not what I had been thinking, but Cockpit could be defined to include both the base parts and the canopy parts. The only thing is this: Windscreen is a fairly cleanly- defined (...) (24 years ago, 7-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: New Parts Category: Cockpit
|
|
Talking about the subject summarized at: (...) I think canopy pieces should probably stay in the Windscreen group. I can see putting the Space Nose and Space Cabin Base pieces in a Cockpit group. There's not really any other place to stick them, (...) (24 years ago, 7-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Category Statement
|
|
(...) I'd say there are no plans to add statements for all part files. The 'default value' for category is the first word in the partname. Since, 3001.dat doesn't have a 0 CATEGORY statement, its category comes from the part name, and the category (...) (24 years ago, 7-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Speaking of colors...
|
|
(...) Silver looks more like brushed aluminum. (...) I think so -- it appears that the new silver is actually the color of the plastic, not a post-molding layer that's plated onto the parts. (...) suggestions being trans-black, 32, or trans-dark (...) (24 years ago, 7-Jul-00, to lugnet.cad.dev)
|
| |
| | Category Statement
|
|
I thought about making use of the category statement in MLCad. This would have allowed to group the parts by category rather than by name or something else .... ... but I did a quick check on the parts and found out that only arround 5% of the parts (...) (24 years ago, 7-Jul-00, to lugnet.cad.dev)
|
