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