Hi all,

Maybe a strange question from me, but what settings does LPub use when rendering with LDView?
I've never been able to figure that out after all these years working with LPub (original and now LPub3D).

I have more PC's that run LDraw where I produce instructions and I am under the impressions it is different on every manchine, though the LDraw installation is pretty standard.
Also the resolution of the screen seems to affect the width/height of the images.
Where on one machine all assemblies fit nicely on the page, rendering the same LDraw file on another machine the images are either bigger (alas don't fit anymore) or are smaller.

Is there a way to force LPub(3D) what LDView settings it uses?

Thanks.

Hello everyone,

This is my first post here so ill add a quick introduction of myself:

Hello all, my name here is Home Brew (aka Michael Nelson) I am a gamer, but also a 3D modeler, using programs such as Blender and photoshop to produce coolish models, ive found LDraw looking to rebuild a LEGO set from when i was younger, the 4743 Ice Blade from the Alpha Team theme.

So with that in mind the default LDraw build does not come with 6 pieces that i need to complete and i've not found enough resources to rebuild these pieces from scratch.

If someone could help me figure out how to install the .dat files from the unofficial list of parts it would be great!

(Also as a extra note, i need parts #47846 #4868b #4869 #44032 #44034 and #47843

Included below is a picture of how far i've completed, and a extra image of a custom lego figure hailing from the dropped LEGO Universe game from 2010-2012:

Hi all,

Through regular expressions the part annotation can be extracted from the part description.
I'd like the annotation for Technic Bricks to be only the length (like beams).
The regex now is ^Technic Brick\s+(\d+\s+(x|X)\s+\d+\s*(x*|X*)\s*\d*\.*\d*)\s*.*$
This extracts the full size of the brick, ie. Technice Brick 1 x 16 gives "1 x 16".
What I'd like is only the 16.
How do I do that?

Thanks.

Conversion LDD<-->LDraw

Hi everyone,

I would like to inform you all that at the following link you will be able to find the Ldraw.xml file updated on a regular basis, as soon as new conversions are available. Everyone can also contribute by sending me updates via the built-in messaging system.
I will make sure to:

1) test the submitted parts
2) update the xml file
3) release a new rev in the same location.

I included at the bottom of the page a log of the latest changes.

http://www.brickpassion.com/#!ldraw/cgjo

Comments are welcome.

- Mattia

Disclaimer: flexible parts (or multi bones: i.e. hoses, strings, ...) cannot be converted (limitation of LDD) and are therefore missing in the Ldraw converted file.

EDIT: If you plan on contributing please make sure to send me tested parts conversions only. In case I get wrong ones I will just notify the contributor and ask to fix and resend. Thanks

This question may have been asked before but if it has I couldn't find it.
From the little I know about 3D modelling and rendering both t-junctions and long sharp triangles should be avoided if possible. The question is, which is worse?
See the example below; which of the three solutions is best for this shape?

T-Junction or Sharp angle by Duq, on Flickr

http://www.ldraw.org/cgi-bin/ptdetail.cg.../54272.dat

I once tried to model this one but couldn't figure the saw details out. I just found out that an LDD model for it exists and is listed on this page but is redacted because the part exists on the PT.

Any way to retrieve the LDD model? I could try stitch the geometry from that onto the unfinished LDraw version. I'm grateful to my past self that I was smart enough to upload the unfinished version onto the parts tracker..

Hello,

as answered here, I was able to solve a little background image bug.

Please download and install the latest release directly from sourceforge.net.

Change log:

Fixed bug:

• Hiding/opening the background image preferences could reset the image offset to (0|0) at 100% zoom.
  

DATHeader 3.0.18.3 is out now.

BUGFIXES:
1) Typ-o 'supbart'
2) StarWars filename ending ..ps1.dat is detected as subpart.
3) In special cases colinear vertices are not detected
4) Error if first character in the title is a number
5) Wrong comment for official files not correctly detected.

I hope these errors are now gone.
If you find anything else not working like expected, please report it as answer here or write a PM.

Please download as usually from http://ldraw.heidemann.org/index.php?page=datheader

Have Fun

mikeheide

Hello,

as mentioned here, I could not resist to fix the scroll wheel bug in LDPatternCreator on Windows 10.

If you are already using a version greater than 1.5.0 you cannot update your installation by clicking on "Help -> Install Updates" anymore.
Please download and install the latest release directly from sourceforge.net.

Change log:

Fixed bug/new feature:

• You can now zoom in/out with the scroll wheel on Windows 10.
  

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