Here I am again Thanks a lot for making my previous request.
I would love to have 93081d also if its possible. Friends Accessories Flower with 6 Rounded Petals and Pin

Thanks a lot again!
George

Hello,

Can someone help create part# 13952 - Pearl Dark Gray Minifig, Weapon Laser Gun Kryptonian for me please?

Thanks,
Marc

I created a new topic since the old one was going to be more and more confusing and takes some time to load when displaying all messages at the same time.
Nevertheless, I am still targeting to release the version 0.8.0 Beta on Monday, 24 December 2014 edit: Tuesday, 7th April 2015
...and I just implemented a shader logic for chrome parts ;o)
https://lh4.googleusercontent.com/-4XXXJ...Shader.png

Done with SR3Dbuilder + LSynth + MLCad.
MPD built with MPDCenter. Should be OMR compatible.
Known errors: Missing stickers, Technic figure torsos has no pattern.
Cyborg figure has plain arms instead of a biomecanical ones, and a mockup for cyborg eye.
MPD file is here.

I have nearly completed the 42008 for Eric's Technicopedia and just in progress of adding the LSYNTH. There are four different types of LSYNTH generated parts necessary: PF-Cable, Pneumatic Hoses, Rigid Hoses and a String.

Generating the LSYNTH parts is no issue. I did them one by one, but then I noticed that LDView did not load the file properly and produced a hell lot of errors. When looking into the file I had literally thousands of lines just stating a position of 0, 0, 0 and "part unknown" the file explodes form 148k to 3 megabytes.

I noticed the following:
- Even if I have a completed LSYNTH in the file, another run of LSYNTH goes over it and generates the "empty" lines
- This seem to happen only for the "PNEUMATIC HOSE BEVELED", these sections get the additional lines
- no additional lines were added to the "Hose Rigid" and the "PF Cable"

Does anybody know why this is the case?

- I use as constraints for the "Hose Rigid" only the LS01 constraint
- for the PF-Cable only the LS06
- but for the Pneumatic Beveled, I use for the start the LS01 and for the guidance the LS02 constraints.

Now I did some experiements with stand alone files, I noticed:
-> I used only the same constraints for each part
-> Each time I press "Execute LSYNTH" I get an additional set of "SYNTH SYNTHESIZED BEGIN/END" statements
-> This a bit inconvenient but does not add to the filesize significantly
BUT
-> When I do a LSYNTH for a piece having different start/end than middle pieces I get havoc.
-> The first of "Execute LSYNTH" is fine
-> each other pass of "Execute LSYNTH" produces thousands of lines with "1 4294967295 0 0 0 1 0 0 0 1 0 0 0 1 Unknown"


Do I have some problem in the set-up or why is LSYNTH doing this to me?

Thansk in advance

Gerald

Looking for the new 13x23 bucket from the 42030 Volvo loader.

Hello there guys! I would love to have 93081c Friends Accessories Flower Rose with Pin

Thanks
Giorgos

Philo was kind enough to mock up the Code Pilot for me years ago when I was building the LDraw file of the 8479 garbage truck. I'm now getting to the point when I'll be preparing the 1997 edition of Technicopedia soon and would appreciate being able to show the part in greater detail. Of course, I can just photograph it and I realize that this is a very unique part that has little demand, so I understand if there are higher priorities. I see that it has been sitting in the unofficial queue for a long time so I thought I would mention it.

Thanks.

1st post!

I am researching a project where I will create LEGO versions of a series of existing wooden sculptures (which are 20 feet tall). The sculptures have 3D design files and I was hoping to be able to save a lot of work by converting the 3D files into LDraw compatible formats. The LEGO project will only use rectangular bricks (2x10, 1x4, etc). Is there any existing software that you know of which I could leverage? Can you imagine a better method for producing the brick design/instructions needed for this project?

thanks!
melting man.

Travis,

Not really sure if this is a bug in LDView or not. Thought I'd report it anyway in case it is of interest. I will concede it's arguably a pretty obscure set of circumstances.

With this minimal case MPD (it took me an hour to cut down my 50000+ part model to find the cause):