Michael Heidemann Wrote:You can use MPDCenter to combine what you need into one single LDR file!
But there is no possibility to split that file later again into its components.
So for viewing purpose you can have what you like.

I have a couple of questions regarding Blender:

1. When you export a multi-model scene (such as an MPD file or other file with sub-models) to Blender, is the result a single large object? Or can each model be modified individually?
2. Which versions of LDraw parts get exported? Low resolution or high resolution?
3. Can I create scripts or macros in Blender that generate meshes? For instance, a script that generates a road surface in the shape of a spline?
4. Which is the best tool to export to Blender at the current time?

I'm trying to figure out how to better space multiple steps on a single page.
By default LPUB will centre the steps on the page, but I would like them to be more evenly spaced.
Where should I look for a local value that will help me to increase distance beteen steps? Or is there a better way to do this?

A long time ago I created a POV-Ray road generator.

http://lib.povray.org/searchcollection/i...Tag=SharkD

I was wondering if someone could create a native LDraw version of it. I'm not that familiar with parts authoring or "real" programming languages.

The tricky bits are the center dashes, so they could be omitted I guess.

Thanks!

[edit]

P.S. I also could never figure out how to calculate the proper amount of banking around a curve given a certain speed limit.

Hi,

a beta of the LDraw All-In-One-Installer 2015-01 can be found here:

http://www.holly-wood.it/tmp/LDraw_AIOI_...bit_v1.zip

This AIOI does no longer contain SR3D as well as Sticker Generator. LPub has been upgraded to LPub3D. Please note that the LDraw Parts Library as well as LGEO haven't been updated so far. This beta focuses mainly on the LPub3D upgrade.

Please test and send me your .logs, which can be found in the c:\Windows\LDraw folder, if you encounter any errors.

Thanks, w.

Hi all,

I'm (finally) nearing the end of implementing file reloading in LDCad 1.5 which leaves only one major 1.5 feature to add; namely editing shadow (part snapping) information.

This means I'm basically adding a (very basic) part editing mode to the main editor. I don't want to go full part editing support with LDCad (as LDPartEditor and others are much better at it) but I'm open to suggestions on part reviewing options etc.

so if anyone has some ideas on this, feel free to let me know as I'm still in the planing stage of this feature meaning everything is fair game

screen shot of a part being edited in the current editor (it's readonly and a bit of hack still though).

Some notes:
Part editing will only be available after enabling an 'advanced' option.
The shadow source and the part's source are shown joined as that is the way they are loaded/compiled internally. I'll add some separation line or something though.
Visualization of the snap data is the temporary one (available through F11 in the alpha's) and will be replaced by nicer / interactive ones.

Attached Files

Thumbnail(s)
   

Hello all,

Just wanted to share some thoughts about the current LDraw colors / LDConfig.ldr

The thing is I think we need additional 'material types' to be used with new colors.

Take for example rope, people usually use black (0) but imho it should have its own number with a 'nylon' finish just as 256 has a 'rubber' finish.

And speaking of rubber the modern pneumatic hoses in technic sets seem to use a more plastic like rubber, I think those need a different 'finish' too.

And a minor thing: Shouldn't the file use dos line breaks instead of Linux ones as dictated by the standard?

Thoughts?

It would be wonderful if some kind person could produce this tire. Even a simplified version would be very helpful. It is very similar to 2902: Tire 81.6 x 15 Motorcycle, except that it has smooth tread.



Many thanks! Alexander

Greetings,

I've completed some more updates and enhancements from mostly community requests. The media is ready but SourceForge is not allowing uploads as they are still recovering from a major disaster. I'll upload as soon as Sf allows.

Media uploaded to SourceForge.net. You can update directly from LPub3D Help, Check for update...

Here are the completed items:

LPub3D 1.2.0.388.2

Features and enhancements
------------
-Sort PLI/BOM by part size (default), colour and category
-Improved model navigation - display selected model from model drop-down. Ignored 'meta=IGN'
submodels are not displayed even though they are in the drop-down list because they are
not assigned a page number. Previous behavior only displayed the model file in the LDraw editor.
-Display LDraw colour code on BOM/PLI tooltip - now showing colour description, colour code and
part description.
-Go To Page navigation combo box - allow page navigation using drop-down box.
-Show progress bar during display page processing/navigation etc...
-Text strings can now accomodate double quotes using escape character '\' - e.g. This \"Fat\" MOC
will display: This "Fat" MOC. For now, edits must always include the escape character '\'.

-CHANGE: Move PLI annotations settings to PLI/BOM Setup preferences.

-Fix: When changing the font on added text, the dialog starts with MS Shell Dlg 2 size 12.
The dialog now starts with display of the actual font perameters being changed.
-Fix: Change to PLI Times Used attribue on multi-step page now affects only the selected step.
when use local option selected.
-Fix: Change to PLI Text Annotation attribue on multi-step page now affects only the selected step.
when use local option selected.
-Fix: Change to PLI Background attribue on multi-step page now affects only the selected step.
when use local option selected.
-Fix: Change to PLI Border attribue on multi-step page now affects only the selected step.
when use local option selected.
-Fix: Change to Step number attribue on multi-step page now affects only the selected step. PARTIAL - Use
local selection still not working.

Screenshots:
   


  02.png (Size: 40.97 KB / Downloads: 0)

   

   

   

Cheers,
Trevor

Is it possible to run DATHeader without the UI? I know there's a command line option but that still just starts the normal application.
Inspired by some of the build and deploy automation we use in work, what I'd like to do is set up a Powershell script that runs DATHeader every time I save a file and writes the report to a specified location.
Is that currently possible? Is it a feature you could implement in a future version?