51–60 of 86 posts
Lego had its own digital designer, I remember playing around with it a really long time ago, seems its still around. http://ldd.lego.com/en-us/
It's terrible.
The only issue is that the database of parts is starting to be outdated, and the database of parts that actually exist even more so.
Wow super cool! They should have a hot swappable rendering backend so we can get globally illuminated PBR renders out. Given the limited materials that Lego bricks are made out of, getting sensible default materials and automated lighting would be hella easy.
Was that something LeoCAD could do or would I need to use a different tool for that? (This wasn't a general purpose hidden surface removal, it was just removing all of the parts of the bricks associated with ensuring physical connections)
I'm wondering about the legal side of this. Is it OK from LEGO side to have stuff like this and other similar tools? And what if when you start printing stuff like that?
Presumably you need to set your printer to its slowest and most precise mode to get a usable block.
Earlier quoted context omitted.
It's terrible.
It's actually all but terrible. The constraint engine is better than all of LeoCAD, stud.io or mecabricks. The only issue is that the database of parts is starting to be outdated, and the database of parts that actually exist even more so.
Earlier quoted context omitted.
It's actually all but terrible. The constraint engine is better than all of LeoCAD, stud.io or mecabricks. The only issue is that the database of parts is starting to be outdated, and the database of parts that actually exist even more so.
Honest question: why do they need a constraint engine? Can't everything be done in exact integer multiples of the smallest brick size?
Earlier quoted context omitted.
It's actually all but terrible. The constraint engine is better than all of LeoCAD, stud.io or mecabricks. The only issue is that the database of parts is starting to be outdated, and the database of parts that actually exist even more so.
Honest question: why do they need a constraint engine? Can't everything be done in exact integer multiples of the smallest brick size?
Despite relying on basically one size (1.6 mm) and its multiples, the Lego system is really complex. To an untrained eye it seems like parts are very specialized, but actually they are just carefully designed.
Earlier quoted context omitted.
Honest question: why do they need a constraint engine? Can't everything be done in exact integer multiples of the smallest brick size?
You can build sideways whenever pieces have studs on the side, for example (the first brick with studs on the side was created in 1979 for headlights!). And also put sticks into hollow studs, "click" Technic pegs into holes, rotate Technic pegs and gears. And even place bricks and plates at an angle, using Pythagorean triples or careful rotations, and much more---this is what makes Lego fun for adults too! Despite re…
Earlier quoted context omitted.
You can build sideways whenever pieces have studs on the side, for example (the first brick with studs on the side was created in 1979 for headlights!). And also put sticks into hollow studs, "click" Technic pegs into holes, rotate Technic pegs and gears. And even place bricks and plates at an angle, using Pythagorean triples or careful rotations, and much more---this is what makes Lego fun for adults too! Despite re…
Oh yeah gearing. I guess this really does deserve the title of CAD software at that point.
Even kids-oriented sets sometimes enjoy using advanced build techniques. You can start with "Lego 31036 speed build" as the search query to enter the rabbit hole from.
I remember reading a mulitplayer Lego game dev talk about how her team spent most of their time creating algorithms to detect penis shaped block sets for censorship reasons.