 | | Re: Open cylinder primitives, any demand?
|
|
(...) This type of primitive would mostly be used in places where a cylinder appears between two other objects. One example would be the subpart at: (URL) currently uses 4-4cylc.dat where a 4-4cylo.dat (cylinder with edges open at both ends) would (...) (15 years ago, 3-Nov-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Open cylinder primitives, any demand?
|
|
(...) Guess I replied way too soon. I may revise my earlier reply after giving it some more thought. A 1/4 cylinder with both ends closed would of course be better for rounded cornerns. A cylinder with both ends open could be useful when making (...) (15 years ago, 3-Nov-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Open cylinder primitives, any demand?
|
|
(...) 4-4 and 2-4 cylc are released, 1-4 and 3-4cylc are already on PT. (...) I think the usefulness is quite low indeed. Philo (15 years ago, 3-Nov-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Open cylinder primitives, any demand?
|
|
(...) A cylinder with one closed end (4-4cylc.dat) was issued in the latest parts update (2009-02). See (URL) . If there is a need for a 1-4cylc.dat, feel free to submit it to the Parts Tracker. However, I'm struggling to see the utility of a (...) (15 years ago, 2-Nov-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Open cylinder primitives, any demand?
|
|
(...) Naming is not an important issue to me. Either name would be fine for me. The one important thing for me is that it doesn't mess up with renderers and utilities that make primitive substitutions. But I don't see that there should be any risk (...) (15 years ago, 2-Nov-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Technic ball joint socket naming
|
|
(...) Seems OK to me, but I don't like "circular" too much. Rounded, perhaps? Philo (15 years ago, 2-Nov-09, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Technic ball joint socket naming
|
|
(...) Hmm.. maybe I should really think another three dozen times more about what I propose. 32174.dat - Technic Ball Socket Single 3 x 2 Circular 47296.dat - Technic Ball Socket Single 3 x 2 Rectangular 47296.dat - Technic Ball Socket Double 5 x 2 (...) (15 years ago, 2-Nov-09, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Open cylinder primitives, any demand?
|
|
(...) Not being a part author, I can't comment on the utility, but to me the naming is confusing. The base cylinder primitives are already open at both ends; they just don't have edges there. So to me, cyle would make more since in the filename, and (...) (15 years ago, 2-Nov-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Technic ball joint socket naming
|
|
(...) I think it's a bad idea to have the double-socket parts be named so similarly to the single-socket parts. The double-socket parts are beams with sockets on either end, whereas the single socket parts are sockets with connectors out the (...) (15 years ago, 2-Nov-09, to lugnet.cad.dat.parts, FTX)
|
| |
| | Technic ball joint socket naming
|
|
(URL) Hi all - I'm currently working on the rectangular ball joint sockets and the naming issue (which I have tried to rise up a couple of times) is to me becoming a little critical. What I'd like is to unify the titles of all seven variants: the (...) (15 years ago, 2-Nov-09, to lugnet.cad.dat.parts, FTX)
|
| |
| | Open cylinder primitives, any demand? [DAT]
|
|
Is there any demand for this type of cylinder primitive that's open at both ends? 0 Cylinder open 1.0 0 Name: 4-4cylo.dat 0 Author: Mark Kennedy [mkennedy] 0 !LDRAW_ORG Unofficial_Primitive 0 !LICENSE Redistributable under CCAL version 2.0 : see (...) (15 years ago, 1-Nov-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: sticker with the shape in use (formed)
|
|
(...) Ah, basically the infamous texture mapping... I've seen a POC applied to LDRAW, and it's quite impressive. It'd be nice if we could move forward on that issue. Creating decorated parts the way it's done now is onerous to the extreme, IMHO. -- (...) (15 years ago, 31-Oct-09, to lugnet.cad.dat.parts)
|
| |
| | Re: sticker with the shape in use (formed)
|
|
(...) Of course, it would be most awesome to have a single part that could assume either configuration. But that is outside the scope of LDraw... Steve (15 years ago, 30-Oct-09, to lugnet.cad.dat.parts)
|
| |
| | Re: sticker with the shape in use (formed)
|
|
(...) The flat version can be applied on other bricks, or be used for bill of materials... Philo (15 years ago, 30-Oct-09, to lugnet.cad.dat.parts)
|
| |
| | sticker with the shape in use (formed)
|
|
At part (URL) there is mentioned a hint that this number should be used for the plain version of the sticker an 56711gc01.dat for the formed version. On first sight this seemed logical to me. On the second sight I wonder why we should make also a (...) (15 years ago, 30-Oct-09, to lugnet.cad.dat.parts)
|
| |
| | (canceled)
|
|
|
| |
| | Re: 4721 - Tyre Minifig Bicycle has wrong part number
|
|
(...) 4721.dat is a brazen cheat from me. I'm surprised that it has no hold votes. 8-) I wouldn't mind it being replaced by a more accurate version - when available. Like Michael correctly writes, I found the part # in Peeron. Changing the part # is (...) (15 years ago, 24-Oct-09, to lugnet.cad.dat.parts)
|
| |
| | Re: 4721 - Tyre Minifig Bicycle has wrong part number
|
|
(...) Tore writes from where he has the number: Peeron. As this is now 6 years ago I fear we never know from where this part no. is from at the beginning. cu mikeheide (15 years ago, 23-Oct-09, to lugnet.cad.dat.parts)
|
| |
| | 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)
|
| |
| | L(EGO)Draw parts - 3rd batch
|
|
Hi folks, the LEGO Universe Team has shared another batch of part shapes with the community, with the purpose to make them fit for the LDraw Parts Tracker. This time things are a bit different. The package we've got contains also shapes which are (...) (15 years ago, 15-Oct-09, to lugnet.cad, lugnet.cad.dev.org.ldraw, lugnet.cad.dat.parts, lugnet.announce, FTX) !
|
| |
| | Re: Official Parts using MLCad colors
|
|
(...) Let me stop this before it gets started... It's not an offense, Tore, nor were you wrong at the time. There is no witch hunt, finger pointing, or conspiracy. We are not on a crusade against you or anyone else. We simply want to upgrade the (...) (15 years ago, 2-Oct-09, to lugnet.cad.dat.parts, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Official Parts using MLCad colors
|
|
(...) It appears so, even if I wish it was just the opposite. I still haven't been convinced why it is so wrong to use the backwards compatible color number range when possible. I used color 462 for the orange part of the German flag because number (...) (15 years ago, 1-Oct-09, to lugnet.cad.dat.parts, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Official Parts using MLCad colors
|
|
(...) Hi, All these colors are in the 'dithered' range, if the actual dither color is wanted by the part author it has nothing to do with mlcad or has it? And isn't declaring new colors in the LDConfig using the dithered range breaking some kind of (...) (15 years ago, 1-Oct-09, to lugnet.cad.dat.parts, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Official Parts using MLCad colors
|
|
(...) There may be problems matching these colors. As you note, these are patterned parts and the colors Lego uses for the printing on patterned parts do not necessarily match the colors used for the plastic brick. -Orion (15 years ago, 1-Oct-09, to lugnet.cad.dat.parts, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Official Parts using MLCad colors
|
|
(...) When we updated the LDConfig.ldr 462 was already defined as Medium_Orange #FE9F06 and has therefore been kept. If Medium_Orange is appropriate for the German Flag is another story. The chart only list colors which are used in parts but are not (...) (15 years ago, 1-Oct-09, to lugnet.cad.dat.parts, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Official Parts using MLCad colors
|
|
(...) How about color 462 in 777p01.dat? (15 years ago, 30-Sep-09, to lugnet.cad.dat.parts, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Official Parts using MLCad colors
|
|
Hi, Scott Wardlaw has written a prog which matches the colors used in the official parts against the now updated LDConfig.ldr colors chart. This is a list of parts that use colors which were mainly defined in MLCad and have never been LDraw colors: (...) (15 years ago, 30-Sep-09, to lugnet.cad.dat.parts, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: 11-16 primitives?
|
|
(...) In the mklist beta I posted there's an undocumented -r switch to turn off the ragged edges and make room for 25 char filenames. There's also an undocumented -t to twiddle with the 78 vs 80 character line formats. But there's nothing yet for (...) (15 years ago, 29-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
Sorry to follow-up my own post, but I did a quick test on MLCAD. (...) I had a DUH! moment after posting the previous message. If MLCAD can use a ragged format file, of course it can use a fixed-25 format file. DOH. (...) I prepared a PARTS.LST file (...) (15 years ago, 29-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | mklist 1.6beta1
|
|
(...) I'm assuming the 80 char lines is what you're aiming for here, so based on the 64 char limit on descriptions I started the descriptions on the 16th character of the line. That gives room for a 15 character name and a single space before the (...) (15 years ago, 29-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) My thinking is the 'ragged' format has the least impact - if there are no long part nambers, then the output PARTS.LST would exactly match the classic format, without the user having to know anything about long/short part nambers. Of course, (...) (15 years ago, 29-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) Yeah, I was actually planning a -f to force it to finish and -q for quiet. (...) For now I've added a -8 to make it use the 8.3 format. As per Travis' suggestion it converts to the canonical short form under Windows. The function uppercases (...) (15 years ago, 28-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) For MLCAD it doesn't matter. Steve said that MLCAD worked fine with long filenames inside parts.lst. The only reason to put the short filename in is for other programs that might have problems with the long filename. And as long as mklist is (...) (15 years ago, 27-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) Sounds easy, but I think nobody can read that short filenames that would appear in the MLCad list!? cu mikeheide (15 years ago, 27-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) If it's running in Windows, I think a backwards-compatible switch should use the Win32 API to get the short filename (with the ~1 at the end, usually, determined using PathGetShortPath) and use that in place of the long filename. --Travis (15 years ago, 27-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) That would be good, I think. (...) Can you have two levels? Level One that still shows the warnings, but doesn't stop, and Level Two suppresses all warnings. (...) I'd keep the current line-format for all parts conforming to the 8.3 format, (...) (15 years ago, 27-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) I could update the mklist sources to work handle filenames with 25 chars I was going to add a quietmode commandline option this weekend anyhow. Should I allow 25 chars as the default, and perhaps include an optional command line arg to (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) If I understand that, this would mean that we could use a new mklist tool and we can start using that long filenames. The possibility to use MLCad for generating PARTS.LST will be away, but this only a little cut. cu mikeheide (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) Were any other issues anticipated? (...) I did a short test of MLCAD with a modified PARTS.LST. The results were mixed - MLCAD seems OK using an altered-format PARTS.LST file, but re-generating PARTS.LST from MLCAD results in an invalid file. (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) When the LSC updated the spec to allow 21.3 filenames, I don't think any of us were aware that this would create a problem for PARTS.LST. However, looking at the file, there's a chance that MLCAD will work perfectly well with longer filenames (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) Parts Tracker-wise (if I remember right, and if nothing's been changed), there's only one script which needs to be modified to accept 21.3 files instead of 8.3 files. Organizationally, I dunno if there is actually a hold-up. The specifications (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) This is the status quo now for many months. What action has been taken to solve that problem? To me it seems only to be a little adjustment to some lines of code (but maybe I am wrong). So my question would be: where is the bottleneck that (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) Well... imho this should not be an issue at all - if the parts tracker was updated! Philo (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) These truncated filenames never went past the LSC, and as such should probably be held. I personally feel that they are inappropriate, but whether or not I think they are appropriate, I believe that it's the LSC's job to determine that. (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
Hi Steve, (...) One reason: the Parts Tracker still doesn't like >8 names :( Philo (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) I ditto Phillippe's primary suggestion: use multiple files. It's good for multiple reasons. However, the current standards allow at least 25 characters in the filename, so is there a reason to worry about a 9 character primitive name? Steve (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) I would suggest avoiding the problem completely by using a 2-4edge + 3-16edge... In other instances the name was shortened: 3-16cone19 --> 3-16co19 11-48ring19 --> 11-48r19 Philo (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | 11-16 primitives?
|
|
What would be the suggested name for an 11-16 primitive for a cylinder or edge line since 11-16 contains 5 letters and tacking on edge or cyli at the end would give a 9 letter name? (15 years ago, 22-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Technic part file title issues and suggestions
|
|
It's this time of year again where I've got a bunch of part naming issues: - There are two official and a set of unofficial Technic Excavator Bucket parts. The problem just is that the buckets' don't only work as excavator buckets; front loaders, (...) (15 years ago, 17-Sep-09, to lugnet.cad.dat.parts)
|
| |
| | Re: 64179.dat
|
|
(...) Ah!!! interesting ;o) (...) It looks good (but I don't have the part - yet...) Philo (15 years ago, 11-Sep-09, to lugnet.cad.dat.parts)
|
| |
| | 64179.dat
|
|
Yes, I did state at (URL) that I couldn't model this piece due to my lack of it - but the Front Loader appeared convienently (sp?) in the store and I had all the cash for it, so... now I have modelled the 'O-beam' as well. Enough story-telling: I (...) (15 years ago, 9-Sep-09, to lugnet.cad.dat.parts, FTX)
|
| |
| | POV dat for L3P v1.4 - 3626bpse - Minifig Head with SW Scout Trooper Black Visor Pattern - POV [DAT]
|
|
Ok, so now I've found out why my minifig head dats with inline POV no longer work. New POV-Ray version was no problems this time. But two changes frm L3P 1.3 to 1.4 caused problems: The names of the colors have been changed from Color[n*] to (...) (15 years ago, 11-Aug-09, to lugnet.cad.ray, lugnet.cad.dat.parts)
|
| |
| | Looking for 64651.dat and 64645.dat files
|
|
I am looking for: 64651 Boat Base 13 x 16 Stern/Bow (URL) 64645 Boat Base 10 x 16 Stern/Bow (URL) LDraw files thanks kurt (URL) The Home of Republic of Texas Navy in LEGO> (15 years ago, 6-Jul-09, to lugnet.cad.dat.parts, FTX)
|
| |
| | Looking for 64651.dat and 64645.dat files
|
|
Hi I am looking for the new 64651 Boat Base 13 x 16 Stern/Bow 64645 Boat Base 10 x 16 Stern/Bow (4 URLs) DAT files thanks kurt (URL) The Home of Republic of Texas Navy in LEGO> (15 years ago, 6-Jul-09, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Help working the Non-CA and L(EGO)Draw parts queue
|
|
(...) Thx for pointing to - must have slipped my eagle eyes ;-) w. PS. And thx for polishing the Mechanical Arm Straight. (15 years ago, 24-Jun-09, to lugnet.cad.dat.parts)
|
| |
| | Re: Help working the Non-CA and L(EGO)Draw parts queue
|
|
(...) This one is also on the parts tracker: (URL) (15 years ago, 22-Jun-09, to lugnet.cad.dat.parts)
|
| |
| | Reverse Ratio torus naming convention
|
|
I have endorsed the Primitive Generator's naming convention for "reverse ratio" tori (toruses) with a minor update to the Primtives Reference ((URL) of the form r{ff}o{rrrr}.dat represent the outer section of a torus where the minor radius is (...) (15 years ago, 21-Jun-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Reverse torus naming convention
|
|
I have endorsed the Primitive Generator's naming convention for "reverse ratio" tori (toruses) with a minor update to the Primtives Reference ((URL) of the form r{ff}o{rrrr}.dat represent the outer section of a torus where the minor radius is (...) (15 years ago, 21-Jun-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Help working the Non-CA and L(EGO)Draw parts queue
|
|
(...) (URL) already on the PT mikeheide (15 years ago, 19-Jun-09, to lugnet.cad.dat.parts)
|
| |
| | Re: Help working the Non-CA and L(EGO)Draw parts queue
|
|
(...) (15 years ago, 19-Jun-09, to lugnet.cad.dat.parts)
|
| |
| | Help working the Non-CA and L(EGO)Draw parts queue
|
|
Hi folks, first of all a big "Thank you" to all the authores how have contributed re-writing Non-CA parts or get the so-called L(EGO)Draw parts (coming from the LEGO Group through the LEGO Universe team) fit for the PT. Some Non-CA parts still need (...) (15 years ago, 19-Jun-09, to lugnet.cad, lugnet.cad.dev.org.ldraw, lugnet.cad.dat.parts)
|
| |
| | Re: Error in part 3641
|
|
(...) Thanks. I hadn't realized there were parts in the unoicial library to sibstitute official parts. Jetro (15 years ago, 10-Jun-09, to lugnet.cad.dat.parts)
|
| |
| | Re: Error in part 3641
|
|
(...) Hello Jetro, This part in official version has indeed a lot of problems. But they have already been fixed in unofficial version on Parts Tracker: (URL) (15 years ago, 10-Jun-09, to lugnet.cad.dat.parts)
|
| |
| | Error in part 3641
|
|
When I open a file containing part #3641 (Tyre) in LDView I get a long list of errors similar to this one: Bad vertex sequence in BFC-enabled quad. File: C:/LDRAW/PARTS/3641.DAT Line #47 Line: 4 16 0 14 8 0 18 8 0 14 0 0 18 0 (Note: disabling BFC (...) (15 years ago, 10-Jun-09, to lugnet.cad.dat.parts)
|
| |
| | Re: 53533.dat
|
|
(...) I don't have the part :( Philo (15 years ago, 8-Jun-09, to lugnet.cad.dat.parts, FTX)
|
| |
| | 53533.dat
|
|
Anyone working on the 53533 Technic liftarm? see : (URL) Is not in the official / unofficial LDRAW parts library. Regards, Ludo (15 years ago, 7-Jun-09, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: 57587.dat origin
|
|
(...) Interesting... I'm agreeing with you, as it seems other dome parts have their top pointing upwards so I shall do it this way. Thank you. (15 years ago, 9-May-09, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: 57587.dat origin
|
|
(...) I would rotate that part, so it is easier to identify this part as a dome. Then I think the top should be at Y=0. I have already send a manipulated version of your mpd file to your address. cu mikeheide (15 years ago, 8-May-09, to lugnet.cad.dat.parts, FTX)
|
| |
| | 57587.dat origin
|
|
Hello all, I have recently been working on (URL).dat, "Technic Cylinder 6 x 6 x 4 with Dome Top" (though I have it here titled as "Technic Dome 7 x 7 x 5" because IMHO it's more like a dome than a cylinder). I've noticed the part origin is a problem (...) (15 years ago, 8-May-09, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Parts spreadsheet/tool?
|
|
(...) I plan on exporting a lot models to other formats, and need the parts to have correct winding. I basically just want to keep track of which parts have been BFC certified, and update and be ready to submit the ones that aren't when the need (...) (15 years ago, 25-Apr-09, to lugnet.cad.dat.parts)
|
| |
| | Re: Parts spreadsheet/tool?
|
|
(...) Mike From the 2008-01 complete library re-release, the !LDRAW_ORG line in the header should uniquely identify the version of the part, as it always includes the parts update number (YYYY-NN or ORIGINAL). If you have installed unofficial parts, (...) (15 years ago, 22-Apr-09, to lugnet.cad.dat.parts)
|
| |
| | Parts spreadsheet/tool?
|
|
Does anyone have a spreadsheet or tool that will report statistics regarding installed parts? It should list information such as certifications, number of lines, last modification date, etc. Thanks. -Mike (15 years ago, 22-Apr-09, to lugnet.cad.dat.parts)
|
| |
| | Re: Comments on some unofficial Train parts
|
|
(...) <SNIP>> (...) Thanks for this information. I have renamed 4093b to 4093c to leave space for the 6+3+6 hole version as 4093b. Chris (15 years ago, 19-Apr-09, to lugnet.cad.dat.parts)
|
| |
| | Re: Comments on some unofficial Train parts
|
|
(...) All battery boxes mentioned consists of several single parts like (URL) maybe (URL) all what you are looking for should be available at the PT. I hope that helps cu mikeheide (15 years ago, 16-Apr-09, to lugnet.cad.dat.parts)
|
| |
| | Re: Comments on some unofficial Train parts
|
|
(...) Thanks, I also think this is complete (good work!). I just suggested to split the "x560etc." into two parts, like: (URL) a question of what can be considered a part. Battery boxes are usually made of two "parts" in real life. I'm not sure if (...) (15 years ago, 16-Apr-09, to lugnet.cad.dat.parts)
|
| |
| | Re: Comments on some unofficial Train parts
|
|
(...) SNIP I think you are talking about these battery boxes: your type 1 (URL) type 3 (note the opening for the contacts in the case) (URL) type 2 (URL) think this is complete. See also here: (URL) (15 years ago, 15-Apr-09, to lugnet.cad.dat.parts)
|
| |
| | Comments on some unofficial Train parts
|
|
Hello everyone, glad to see the traffic on Parts Tracker! As a railway fan I am double-glad to see some Train-specific parts developing. However, I have noticed some issues with part naming so I think it's better to solve them while the parts are (...) (15 years ago, 15-Apr-09, to lugnet.cad.dat.parts)
|
| |
| | Re: Updated Primitives Reference
|
|
(...) Don't worry Chris, we all know the precarious nature of unofficial stuff. But in the meantime it helps to have a quick reference of the shapes available! Philo (15 years ago, 7-Apr-09, to lugnet.cad.dat.parts)
|
| |
| | Re: Updated Primitives Reference
|
|
(...) Sorry, but this is a bad idea. These primitives are unofficial - which means that before release the names might change. In fact some of them will definitely change. I don't like to break other peoples webpages, but this might happen now. (...) (15 years ago, 6-Apr-09, to lugnet.cad.dat.parts)
|
| |
| | Updated Primitives Reference
|
|
LDraw author J.C. Tchang has created an updated Primitives Reference, based on (URL) but including unofficial primitives on Parts Tracker as of 2008-12-08. It is available here: (URL) you can see it is written in French, but I hope that thanks to (...) (15 years ago, 20-Mar-09, to lugnet.cad.dat.parts)
|
| |
| | Re: Stretching cylinders [DAT]
|
|
(...) There is no way to get your shape using primitives, it would require non-linear transformations. So, as mentionned by Michael, the best way is to use Coverer. You can nonetheless get a similar (but quite different) shape using shearing as (...) (15 years ago, 15-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Stretching cylinders
|
|
Is this what you had in mind? (...) Basicly changing any of the non zero coordinates will scale along the coresponding axis. You can also accomplish shearing by replacing any of the zero's with a different number. (15 years ago, 14-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Stretching cylinders
|
|
(...) AFAIK there is no solution with primitives in this case. I would suggest use one of the tools from Philo ((URL) to fill the space between those 4-4edge.dat cu mikeheide (15 years ago, 15-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Stretching cylinders [DAT]
|
|
Well, it's my second thread today, but how would you go to "stretch" a cylinder, like a cone, but only in Y-axis, not X-axis? I've again attached a dat file to show what I mean. Basically I'd need a cylinder that'd fit those two 4-4edge.dat:s, any (...) (15 years ago, 14-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: cylt.dat
|
|
(...) Agh... guess it's going to take some time before I'll master those cyls.dat files. Well, this seems to save me a primitive. (15 years ago, 14-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: cylt.dat [DAT]
|
|
(...) As far as I can see the same can be build by 1-4cyls.dat like this: 0 Untitled 0 Name: Untitled.ldr 0 Author: Michael Heidemann [mikeheide] 0 Unofficial Model 1 16 -1 0 0 1 0 0 0 1 0 0 0 1 1-4cyls.dat 1 16 -1 0 0 1 0 0 0 1 0 0 0 -1 1-4cyls.dat (...) (15 years ago, 14-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | cylt.dat [DAT]
|
|
Hello, I've been in need of a primitive something similar to a sloped cylinder, but something little different, so I made such primitive. I can't describe the primitive, though. You'll have to see it yourself. :-) What I'm concerned now is the (...) (15 years ago, 14-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Official Parts using MLCad colors
|
|
Hi folks, working on the LDConfig file (URL) came across official parts that use colors present in MLCad but not the still official LDraw color chart: (URL) to mention a few: Color 430: 3811p02e.dat Color 431: 973p2e.dat Color 485: 973p4t.dat, (...) (15 years ago, 10-Feb-09, to lugnet.cad.dat.parts, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: searching for people that have 1966-1970 electric parts
|
|
(...) Can you please check the thickness of the pins of the cables. I think the red single connectors are a little bit thinner than the gray double connectors. If so, we have to care about the difference in building the LDraw-Parts. If I am right, (...) (15 years ago, 4-Feb-09, to lugnet.cad.dat.parts)
|
| |
| | Re: searching for people that have 1966-1970 electric parts
|
|
(...) (URL) 002 - have 2 in working condition. Dave K (15 years ago, 3-Feb-09, to lugnet.cad.dat.parts)
|
| |
| | searching for people that have 1966-1970 electric parts
|
|
I am searching for people that still have the electric parts that where produced during the time 1966 - 1970. If you have such parts, please leave a note here. As soon as I have my questions totally clear I will then ask in detail. cu mikeheide (15 years ago, 3-Feb-09, to lugnet.cad.dat.parts)
|
| |
| | Re: need help with 61808.dat
|
|
(...) The thing is that I got this far, but I don't know how to proceed. It's kind of split into three... First, the "wings" that, when assembled, cover the pump. I don't know how long should I make the quadrilaterals. I tried measuring but there (...) (15 years ago, 29-Jan-09, to lugnet.cad.dat.parts)
|
| |
| | Re: need help with 61808.dat
|
|
(...) Please tell us more exactly what problem you run into. So we can help to solve your problem. cu mikeheide (15 years ago, 29-Jan-09, to lugnet.cad.dat.parts)
|
| |
| | need help with 61808.dat [DAT]
|
|
Hey, I've been working on 61808.dat, the Nynrah Ghostblaster, though I've ran into problems with it, which should be quite obvious with a person who hasn't been modeling parts for long and a part as complex as this. I want to get this ready one day, (...) (15 years ago, 29-Jan-09, to lugnet.cad.dat.parts)
|
| |
| | Re: what's wrong with the POTM email?
|
|
(...) And what about LSC email? I have a few issues to submit but got a bounce back a few minutes ago :( Philo (15 years ago, 29-Jan-09, to lugnet.cad.dat.parts)
|
| |
| | Re: what's wrong with the POTM email?
|
|
(...) The motm address should now be fixed. -Orion (15 years ago, 29-Jan-09, to lugnet.cad.dat.parts)
|
| |
| | Re: what's wrong with the POTM email?
|
|
(...) As far as I know Dan and Orion are still working to fix the addresses after we had changes in the DNS. Please send your POTM submissions to my privat address at: ldraw[at]holly-wood(.)it Bye, Willy LDraw Contest Coordinator (15 years ago, 27-Jan-09, to lugnet.cad.dat.parts)
|
| |
| | Re: naming for some half-primitives
|
|
(...) Actually yeah, that's an even better approach... saves primitives. I guess I should do that instead. (15 years ago, 27-Jan-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: what's wrong with the POTM email?
|
|
(...) There is a problem with all email to the adresses that ends with ldraw.org. I also do not know exactly what is the problem, but it seems to be bigger because it is still not fixed. (15 years ago, 26-Jan-09, to lugnet.cad.dat.parts)
|
| |
| | Re: naming for some half-primitives
|
|
(...) If I have such a problem I use those primitives that are not presently available in the main file, while the other stuff goes into the subfile that I then use several times. cu mikeheide (15 years ago, 26-Jan-09, to lugnet.cad.dat.parts.primitives)
|
