Hi,

I've written a little JavaScript to break an .ldr file into steps (assuming it has none): ldr-stepper

It sorts an .ldr file's pieces by an axis (x, y [default], or z) in ascending order. You can choose to split the file into n pieces per step, or m total steps.

The output can be a reasonable place to start breaking your model into steps. I wrote this for a 375-piece model, so YMMV.

No other heuristics are performed. If anyone has any suggestions to improve the algorithm, or finds this useful, please let me know! You can reply here or file an issue on the GitHub.

For those unfamiliar with NodeJS, just follow the instructions in the README. Please let me know if you have issues--I've heard NodeJS is better on Windows if you run cygwin.

Chris

Is there a general-purpose brick-snapping algorithm published anywhere?

I have some ideas around computer-generated LEGO models, and things would be much easier if I didn't have to figure it out myself.

Chris

Complete with printed tiles

feedback welcome.

Chris

Attached Files

  21303 - Wall-E.mpd (Size: 110.75 KB / Downloads: 39)

Download MPD (OMR compliant)
Known errors: None
Done with LDCad 1.5alpha4.

My attention was drawn to this topic by a post by Sylvain Sauvage on LeoCAD list:

I started cleaning up some old tutorials on the wiki, but the images aren't showing up. You can see here that a lot of images are affected:

http://wiki.ldraw.org/index.php?title=Sp...&offset=50

Any change we can get this fixed?

Can this part connect flush on a baseplate? I am looking at the bottom and there does not seem to be room for every stud. Compare to part 3943a.dat which does connect well on a baseplate (I think).

MLCad Arrow when import model to LICreator https://www.dropbox.com/s/0tkc3m7tajo4s0q/LIC.jpg?dl=0

What you can do with LICreator

  lic_arrow_actions.png (Size: 50 KB / Downloads: 1)

The question is how do IT this work correctly ?!!.

Go to https://github.com/Jeremy1980/licreator and try new release. This compilation is under Python v2.7.8 and newest PyOpenGL libraries.

Changes related to previous 2.0.016 version Wrote::: Can change layout orientation for selected pages in one time
:: Can remove empty|blank pages automatically
:: Can expand only children of selected node in tree view
:: Change tool bar icon size to 18 pixels
:: Re-grouped tool bar actions
:: Lock icon use SmoothTransformation and ItemIgnoresTransformations flags now
:: Layout orientation actually remember in undo stack
:: For more look into changelog.txt

• setuptools-18.3.1
  
• pyinstaller-2.1
  
• PIL-1.1.7.win32-py2.7
  
• PyOpenGL-3.1.0.win32
  
• PyQt4-4.10-gpl-Py2.7-Qt4.8.4-x32
  
• pywin32-219.win32-py2.7
  

Under what circumstances and to what extent should the inside of a part be modelled?
The reason I'm asking this is that I'm working on the PF Track points and their 9V counterparts have the entire inside detailed in the part; the bottom cover is a complete part and everything below it is modelled too.
Personally I don't see any use or need for these details. That bottom cover is not intended to be removed and I'd say 99% of owners never have and never will.
In comparison, for example the PF motors don't have their insides modelled; the shell components are only drawn as far as they can be seen without disassembling the part.
Are there rules or guidelines about this? My intention would be to build the track points like the PF motors; only model what you can see. This would also affect the Monorail track switch that's being discussed elsewhere.