Automatic Binding Bricks
Sets 700/1, 700/2, 700/3 (1949) — the very first!

These models are arguably the first "official models" ever. While instructions weren't yet included in the original LEGO sets, these three houses appear in the catalog of 1950 as examples of what could be built with each of the three basic sets.

However…as far as I can tell, they actually couldn't be built from those sets, at least not according to the listed contents. Maybe some of them could, but at least with 700/1, the model uses more 2x4 bricks (115) than are included in the set (84), and there aren't enough 2x2's left over to substitute for them. And that's not even accounting for the available color selection and slot configurations…

This, of course, assumes that these are meant to be full, 4-sided models—and they really must be, or the roofs wouldn't stand. (I'm not even sure they would in the first place!) So I've guessed at what the two hidden sides might be, as well as the color scheme. These were two-tone colorized B&W photos anyway, and the color selection was not fixed in those days—you were limited to whatever colors you got in the box! So that's also conjectural.

But in any event, it's an interesting glimpse into what the building process would have been with these very oldest bricks, available in only two sizes and two slot configurations—and with no real clutch power at all, despite the name!

Hi,


I'm using the 3-16ndis.dat primitive in the part I'm working on (35103).


In fact I had to slice a 2-4ndis, so I replaced it by two 3-16ndis and the two quads I get using SlicerPro.


The matter is that, there's a realy small gap between the 3-16ndis primitive and each quad. But this gap disappears when I inline the primitive with LDDP, so I deduced it's a matter of precision using SlicerPro. The problem is that even with a better precision the gap is still here.
I've the same problem with 3-8cyli.dat for the vertical part.


So my question is : should I keep the primitive and the gap, or should I inline the primitive to close the gap ?


Or maybe there's  a third way I didn't thought about...

Hi all,
There we go, my first thread here. It's about LPub3D. Despite my well defined love-hate relation with LPub3D, I still can't figure out how to get a decent BOM of the instructions. Sure, one page works fine, but multiple pages end up to ... nothing actually.
With a big model you have to zoom out to get to the bottom-middle of the BOM to change it's shape. But since the page itself stays in the middle, AND CANNOT SCROLL the page/viewport, you end up with a tine black square that is so small that you can't select it anymore. A solution is to change the shape of the BOM, from 'area' to colums for instance.
But then you end up with a very long list you still cannot resize.
So you split the BOM. Splitting the BOM doesn't take landscape orientation into account and besides this, you work with columns. So the list is split as if the page was portrait.
And so on and on and on and....

How do you make a BOM that:
- can span multiple pages
- splits at reasonable points
- does not jump to an different/arbitrary) location if you resize, move, split or change its shape

Has anybody success of making a BOM in LPub3D that didn't take hours and hours and didn't had to, after using one A0 page, use Photoshop to make things easier?

I realise and concur that the author of LPub3D did a great job. But that doesn't take away the fact that I'm starting to hate building MOCs I cannot publish.
My advice to LPub3D is therefore, stop making exotic features work; work on functionality and reliability. LPub3D crashes way to often, and I hate, as a law abiding citizen, looking at a blue turning cursor idicating that the program is busy. Well, it's not.

Note. As you can see, I'm having trouble not to reflect my frustration. Yes I'm thankful for/yo people like Sandy. But LPub3d is not only consuming way to much time, it spoils the fun of being an AFOL too much. We're here to share our love for and involvement with other LEGO fans, not to bug-fix some appliaction.

Ciao, and thanks in advance,
Eef

Is there some sort of "flood fill" utility to triangle-ize the blank space in a pattern (up to a defined bounding rectangle). Filling in the negative space with color 16 triangles is super time consuming. 

Maybe this exists and just to dense to find it.

I would like to request a simple tool to randomly distribute objects (such as trees or bushes) over a wide area, taking into account collision with other objects and the ground. I.e. just drop them vertically from the sky and make sure the trees 1) don't intersect with each other and 2) stop falling when they collide with other objects below them such as bumpy terrain. If the tool runs from the command line that is okay! Thanks!

Hi I'm looking for

Minifig Hat Bicorner with Black Admiral Pattern - 2528px2.


Tomasz

I've started to model the 42125 set, and I have a problem with the front hood. This one is a 5-bar linkage, not so easy to create directly in LDCad. I created a Geogebra model that easily gives me a solution, but when I bring the values in the model the hood is placed very low and there is a collision between the hood and the chassis. I think I verified correctly all the assemblies, so I'm puzzled... That's probably a big, obvious mistake, but...
Geogebra file: https://www.geogebra.org/calculator/jrbf4qav
Model in current state attached.

Attached Files

  42125 - Ferrari 488 GTE AF Corse.mpd (Size: 46.7 KB / Downloads: 10)

Who has this part? Could someone please check this geometry:

1 4 0 0 0 1 0 0 0 1 0 0 0 1 43936.dat
1 15 0 22.5 -38 1 0 0 0 1 0 0 0 1 3031.dat
1 15 0 14.5 -68 1 0 0 0 1 0 0 0 1 3710.dat
1 15 0 -9.5 -68 1 0 0 0 1 0 0 0 1 3701.dat
1 15 0 -17.5 -68 1 0 0 0 1 0 0 0 1 3710.dat
1 15 0 -25.5 -68 1 0 0 0 1 0 0 0 1 3710.dat


And check the pin hole?

It's my understanding that these two parts actually represent a single part with a two-sided design, rather than two parts with distinct designs. Should they be merged? and if so, under what number?