DATHeader 3.0.18.1 is out now.

New:
1) Bad lines are now detected and reported
2) Triangle with the same vertices than one quad will be reported
3) The filenae of subparts usually ends with sXX. This will be checked and reported.

I hope you like the changes.

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

Have Fun

mikeheide

Greetings,

I wanted to test LPub3D's fast-fix framework so I fixed some issues reported by the community. I also included a little enhancement to the PLI annotation management; hence, the version change.

To implement these updates, just click Help=>Check for Updates. Alternatively, you can turn on automatic update check in the Configuration=>Preferences=>Updates tab.

Here are the changes:

LPub3D 1.1.0.370.2

Features and enhancements
------------
-Enable/disable PLI annotations (Preference Dialog) - see image below
-Edit part title annotations - see image below
-Fix: .dat subFiles not processed for 3D viewer - causes abnormal end (expected
dat files to be treated as part and placed in Official/unofficial parts).
Dat subfiles are now treated same as mpd/ldr subfiles.

-CHANGE: isSubmodel check no longer observes meta !LDRAW_ORG as Submodel=False

-KNOWN ISSUE: When an image (e.g. logo) is placed bottom left or bottom right
right of the page header, dragging the image produces unexpected placement - the same
may be true with regards to placement relative to the page footer.
WORKAROUND: If you want to reposition by dragging, set the image relative to the Page
(any relative position) or bottom center of the header/ top center of the footer.

Images:

Turn off PLI Annotation
   


Edit PLI Part Title Annotation
   

Hi,

I had to do a little job with Sticker Generator (after a long, long time I last used it) and found it really buggy so I'm gonna delete it form the AIOI.

w.

Disregard. Things are working now. Somehow the preference set got switched to 'Quality'.

Greetings,

As there has been some interest in the LPub3DViewer prototype screenshots I posted some time ago, I have industrialized my additions and uploaded version 1.0 to LPub3D on SourceForge.net.

Here are most of the added features/enhancements:


  LPub128.png (Size: 12.9 KB / Downloads: 2)

LPub3D 1.0.0.320.2
------------
-Integrated 3D Viewer powered by LeoCAD
-Set ROTSTEP (step rotation) meta using 3D Viewer
-Fade previous step's parts
-Use any LDraw colour as fade colour
-Manage colour parts for complete part fade
-Unlimited PLI part annotations
-Split the BOM (divide parts over number of BOM occurrences)
-Formatted front and back cover pages
-Automatically generate formatted cover pages
-POV/L3P high-quality rendered instructions
-Customizable front and back cover pages
-Text and picture (e.g. logo) front and back page attributes
-Customizable content page header and footer
-LDraw editor line numbers
-64/32-bit automatic installer
-Automatic check for updates
-Qt 4.8.6
-Bugfixes and robustness improvements

Screenshots:

   
   
   
   

Cheers,
Trevor

After I finished 53400, the PF curved track, I started on the PF points (53404 & 53407). As these are going to be big files I wondered if I could reduce the file size. The most obvious way would be to make the steps or sections in the curved rails bigger so as an experiment I changed 53400 from roughly 10LDU sections to 20LDU sections. That took 42% off the combined file sizes of the sub files. I then viewed both versions in LDView and didn't spot a difference:
https://www.flickr.com/photos/duq/195108...ateposted/
So what do you think? Going forward, use 10LDU or 20LDU 'resolution' for curved track parts?

Dear All,

the following part is missing: bfloat2c01, LEGO Boat Hull 25 x 10 x 4 1/3 (from set 4011)

at least I am unable to find it

Is there anyone who could create it?

Thank you in advance,
Best regards,
Marek Kaminski

PS. and as my gratefulness, I'd like to share with you, when the part is created, a model of my swimming NXT RC trimaran (I miss this one (middle) hull to create its building instructions)

Never got a clear answer about this... is it useful to make subparts for parts that has symmetries or repetitions, strictly for rendering speed? (I won't discuss here the other benefits of subparting such as file size savings).

Is there a way to definitively know whether a particular .ldr or .dat file is a full part as opposed to a subpart or primitive? I'm writing an online LDraw visualizer using three.js, and one feature I'd like to add is an animation of the model "blowing up" - all of the pieces coming apart and falling to the floor. In order to do this, I'll need to know which definitions are linked and which aren't (i.e., I don't want the studs coming off the bricks).

My first thought is to assume that all subfile references in the root .ldr file are their own parts. However, I'm not sure if this is a reasonable assumption to make (this would do strange things if one was viewing a part directly, like a 2x4 brick (3001.dat) ).

Being able to identify individual parts will also help with seam width calculations.

Hello everybody.

You probably know that the situation about LPub and other SW needed for LDraw instructions creation is not optimal. One needs to make several utilities to cooperate to be able to do the full work from the idea through LDraw model to final PDF with instructions: the editor, renderers, LPub... And some of those utilities are no longer maintained. The situation is little bit worse on Linux because of some Linux-specific issues (like the fact Linux filesystems are case-sensitive).

I'm glad I can announce the result of our effort to help in this area: we created a github group to collect all SW needed to create the instructions using LPub (in the end). We imported the history of original projects (CVS or SVN), we continue to merge with upstream if it is alive (like for LeoCAD) and, thanks to github, we open a chance for everybody to cooperate: build, test, improve, send patches back. You do not need any special permission like in CVS/sourceforge times! Let's join us!

https://github.com/ldraw-linux

As you can see it is named ldraw-linux. This may confuse somebody so I clearly say at the beginning: the project started to make those utilities working on Linux, hence the name. But all our patches are Windows-compatible and the only limitation is that we do not have any machine and knowledge to test Windows builds now. Such a help is really appreciated - send me a PM or say here in this thread!

In short: our goal is: join our forces together and make this not only working but even improved!

At the end, I want to thank SUSE company for the hackweek: this allows us to work on any opensource project at work, during that week. And you can see there are really many projects people work on