Subject:
|
Re: New Part: 3001_d.dat - Duplo Brick 2 x 4
|
Newsgroups:
|
lugnet.cad.dat.parts
|
Date:
|
Thu, 4 Jan 2001 23:12:59 GMT
|
Viewed:
|
981 times
|
| |
|
|
Whoops- I forgot to add something... this is a working copy only. It
certainly needs work. Mainly, it has none of the interior ribs. I'm just
posting it because I am already using it as a standin piece right now. If
someone else wants to do it properly, go for it (not trying to step on
anyone's toes, here!)
--
Tony Hafner
www.hafhead.com
In lugnet.cad.dat.parts, Tony Hafner writes:
> Again, I'm not an expert on naming conventions. But it makes sense to me to
> name a Duplo piece after the corresponding System piece and append it with
> "_d". But if someone more up on this sort of thing has a better idea, by
> all means correct me (not like I could stop you from doing so...)
>
> Here is a Duplo 2 x 4, using these recently posted primitives:
> Tore Eriksson's "Studdu2.dat":
> http://news.lugnet.com/cad/dat/parts/primitives/?n=123
> my recently posted "Stud4du.dat":
> http://news.lugnet.com/cad/dat/parts/primitives/?n=125
>
> When I tried to load a construction using this part into MLCAD, I got a
> missing file error for "stu24du.dat". Seeing that I never referenced this
> file, I assumed that it is an alternate rendering file that is implicitly
> required by the inclusion of the "stud4du.dat" primitive. I cheated and
> simply copied "stud4du.dat" with that filename and got no more complaints.
> But I have no idea how this actually affects anything... I assume it's not a
> good thing.
>
> I have a sample model file, using this part, here:
> http://www.hafhead.com/lego/files/Duplo_Example.dat
>
> That folder also contains all the referenced primitives.
> http://www.hafhead.com/lego/files
>
> --
> Tony Hafner
> www.hafhead.com
>
>
> 0 Duplo Brick 2 x 4
> 0 Name 3001_d.dat
> 0 Author: Tony Hafner
> 0 Unofficial part
>
> 1 16 40 4 0 1 0 0 0 -10 0 0 0 1 stud4du.dat
> 1 16 0 4 0 1 0 0 0 -10 0 0 0 1 stud4du.dat
> 1 16 -40 4 0 1 0 0 0 -10 0 0 0 1 stud4du.dat
>
> 1 16 0 48 0 76 0 0 0 -44 0 0 0 36 box5.dat
>
> 4 16 80 48 40 76 48 36 -76 48 36 -80 48 40
> 4 16 -80 48 40 -76 48 36 -76 48 -36 -80 48 -40
> 4 16 -80 48 -40 -76 48 -36 76 48 -36 80 48 -40
> 4 16 80 48 -40 76 48 -36 76 48 36 80 48 40
>
> 1 16 0 48 0 80 0 0 0 -48 0 0 0 40 box5.dat
>
> 1 16 60 0 20 1 0 0 0 1 0 0 0 1 studdu2.dat
> 1 16 20 0 20 1 0 0 0 1 0 0 0 1 studdu2.dat
> 1 16 -20 0 20 1 0 0 0 1 0 0 0 1 studdu2.dat
> 1 16 -60 0 20 1 0 0 0 1 0 0 0 1 studdu2.dat
> 1 16 60 0 -20 1 0 0 0 1 0 0 0 1 studdu2.dat
> 1 16 20 0 -20 1 0 0 0 1 0 0 0 1 studdu2.dat
> 1 16 -20 0 -20 1 0 0 0 1 0 0 0 1 studdu2.dat
> 1 16 -60 0 -20 1 0 0 0 1 0 0 0 1 studdu2.dat
>
> 0
|
|
Message has 1 Reply:
 | | Updated Part: 3001_d.dat - Duplo Brick 2 x 4 [DAT]
|
| 2nd reply to my own post... After realizing that the inner bits aren't really all that hard (time-consuming, perhaps, but not too hard), I added the interior ribs and associated lines. I hadn't planned on doing this today, but it's been quiet around (...) (24 years ago, 5-Jan-01, to lugnet.cad.dat.parts)
|
Message is in Reply To:
| | New Part: 3001_d.dat - Duplo Brick 2 x 4 [DAT]
|
| Again, I'm not an expert on naming conventions. But it makes sense to me to name a Duplo piece after the corresponding System piece and append it with "_d". But if someone more up on this sort of thing has a better idea, by all means correct me (not (...) (24 years ago, 4-Jan-01, to lugnet.cad.dat.parts)
|
17 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
