[font=Arial, sans-serif][size=large]10030 UCS Star Destroyer [Star Wars]


[/size][/font]
Download MPD-File (OMR compliant)

Done with LDCad 1.5.

Dat file for Display Sticker generated with Sticker Generator by R.Melkert and imported into the mpd file as unofficial part via MPDCenter.

To show sticker in LDCad place the sticker image file alongside the model file.

The structure of the mpd file follows the instructions. So we have 135 submodels and around 600 steps.

Errors: hopefully none

I've been working on a mirror feature for LDCad 1.6 it is already working quite nice.

Problematic are the paired parts (e.g. left/right wing etc)

I managed to get the feature working for lots of parts without the need for additional information, but some parts will still need it .

For this I'm introducing a new LDCad meta for use in the shadow library. Some examples:

15209.dat "Tile  1 x  2 with  2 Teeth Vertical":

Hi :)
you wanted some tabs? Version 0.8.19 delivers it... ;)


As always, you can download LDPE from this page:
http://nilsschmidt1337.github.io/ldparteditor/

Changelog:
(5 new features and 4 bug fixes)

With this release you will be able to...

• ...use tabs in the 3D editor along with the tree on the left side.
  
• ...hit a button to synchronise the tab selection from tabs in the 3D editor with the text editor.
  
• ...see a dialog when you try to re-load an unsaved file again.
  
• ...smooth a set of vertices (with realtime preview)
  
• ...access the colour palette functions (load / save / reset) from a sub-menu.
  
• ...benefit from little performance improvements / refactoring.
  

1. [Recurring] "Conditional Control Point Vertices" caused flickering on multiple views.
   
2. Annoying mouse issues with the manipulator.
   
3. The selection highlight feature in the text editor was sometimes not synchronised with the 3D view.
   
4. [CSG] Rotating a part at 90 degree: It got undesired 0.0 digits.
   
5. One manipulator icon was a duplicate.
   

1. Download the zip-Archive
   
2. Extract the archive content to the location of your choice
   
3. On windows, double-click "run.bat" to start LDPE.
   
4. On linux/mac, you have to excecute the shell script "run.sh" to start LDPE.
   

1. On windows, double-click "update.bat" to search for updates.
   
2. On linux/mac, you have to excecute the shell script "update.sh".
   

• Java Runtime Environment (JRE) 1.8
  
• OpenGL 2.1 compatible Graphics Card
  
• Operating System (32/64bit): Windows [XP; Vista; 7 or newer], Mac OS X [>=10.6], Linux [e.g. Ubuntu Linux >=10.4]
  
• CPU: Multicore-Processor e.g. Intel Core 2 Duo or AMD Athlon II (>2.0Ghz)
  
• RAM: 4GB
  
• Video-Memory: 512 MB
  
• Free Disk Space: 100 MB
  

• Operating System (64bit): Windows 7, Mac OS X [>=10.6], Linux [e.g. Ubuntu Linux >=10.4]
  
• CPU: Multicore-Processor with 4 cores (or more)
  
• RAM: >4 GB
  
• Video-Memory: >=1 GB
  
• Free Disk Space: 512 MB
  

Hi all,

I'm currently experimenting with photogrammetry (Agisoft PhotoScan) to author complicated shape of lego parts.

Here is what I've acheived so far with Mickey's head:



There is a bit of mess around the nose but I'm quite happy with the raw conversion from photos to 3D mesh.
It's a first try but I'm pretty sure I can improve it.


A question for Philo: is this close to what you get from you 3D scanner? Do you think it could be workable to create a ldraw part?

As Lego part are made of shiny plastic I had to put some flour on the part to allow the software to track the geometry. This is maybe why I get this bumpy surface. If someone has a better idea, feel free!

[attachment=2381]Hallo Frindes

I need the sticker from 42009

Thanks Thorsten

I'm working on a model that has a lot of black parts, so I've started using fading to make it clearer where the parts go for each step.  However, I've run in to a problem that I can't seem to figure out.  When I use BUFEXCHG to go from an "exploded" view with arrows to the resulting assembly, the fading isn't working consistently on the subsequent step.  In one place, all of the parts added to the retrieved buffer in the next step are faded when they shouldn't be--resulting in a step that is all faded.  In another place, some of the parts are faded and some are not.

I've been flailing away at this for a while, but haven't come up with a way to get it to work properly.

The closest I've come is this approach:

1) Assemble the parts that are common the the "exploded" view and the final assembly (including 3 sub-assemblies).  This generates the building instructions for two of the sub-assemblies.  The third sub-assemble is a call-out
2) Store this in two buffers, A and B
3) Build up the rest of the assembly with parts in the proper position.
4) Store the resulting assembly in buffer B
5) Retrieve buffer A
6) Build up the rest of the "exploded" assembly between !LPUB PART BEGIN IGN and !LPUB PART END statements
7) Display this "exploded" assembly with a ROTSTEP statement
8) Retrieve buffer B
9) Display this assembly with a STEP statement.  Entire assembly shows up as faded.
10) Add the next step's parts and display with STEP statement.

I don't really want to display the faded assembly in step 9, but that's the only way I've gotten the subsequent step to display properly.  If I leave out the STEP statement at step 9, the parts in step 10 ended up faded along with the assembly generated in step 3.

It seems like LPub3D is having a hard time sorting out what constitutes a prior assembly for fading after buffer exchanges. 

If anybody has gotten this to work properly, please share your technique.  I'd be eternally grateful.

Trevor--if this is something that hadn't yet been planned for in the LPub code, I have a suggestion:  create a new 0 !LPUB directive that provides an unambiguous demarcation--a way to tell LPub that the current state of the assembly should be faded (without display) and subsequent parts not faded up until the next STEP, ROTSTEP, or the end of the (sub-)assembly.



For the record, I am resetting all caches prior to each attempt.    Also, it seems that resetting image and 3D caches (the first choice in the dropdown), also resets unsaved changes in the mpd file.  Minor inconvenience now that I've figured it out, but a frustrating PITA before that.

I'm attaching the current version of my mpd file.  The problem areas are in pages 11-13 and 31-32.

Thank you.


BTW--I use a custom annotation font and pli.mpd file, so you're results will probably be slightly different than mine, but these don't affect the fading.

Attached Files

  HobermanStand.mpd (Size: 130.81 KB / Downloads: 12)

I've attached the mpd so you can mess with it and understand the problem.

Edit Bunk_V2.
You'll see submodel Bunk_Wall_Rear2 in there. Notice how it's rotation is out of whack. Even with 1deg rotation, I can't get this part to line up correctly.

I think the problem is actually in the subfile itself. I think I got the rotation all whacky in there while creating it. And it probably goes all the way back to Cab_Wall_Rear which I duplicated to create Bunk_Wall_Rear.

Is there a way to select all of the parts and "center" everything in 3 dimensions?

Darren

Attached Files

  peterbilt389_darren_LDCad.ldr (Size: 103.32 KB / Downloads: 2)

Hello, I'm very new to LPub3D (and LDraw as a whole for that matter), and I've encountered a problem that I haven't been able to figure out in LPub3D.

I have 2 different submodels that I want to be called out in a step, each submodel having 2 instances. When I convert one of them into a callout, it works as per normal, and the callout has a little "x2" at the bottom right-hand corner. When I try to call out the second submodel (which is a mirror image of the first), the callout pops up without the "x2", and the instructions for the submodel are still there in the previous pages, but the "x2" is gone there. I can then turn the previous remaining pages into a callout, but then I end up having 2 identical callouts on a page, where I should just have a single one with a "x2" at the bottom.

It seems that for one submodel, the instances are getting treated as instances of one unit, but in the other submodel, they get treated as individual submodels once converted to callouts.

Has anyone else experienced this? How can I fix it? Am I even making sense?
Thanks in advance!

I need help getting a ldr into an mpd as a submodel and not just a bunch of individual parts.

Here's the deal. I made a whole whack of edits to an mpd to get it near where I wanted it. Then I added an entire submodel for the tank on the front trailer.
Then I decided I wanted to start all over and keep some of what I took out of the original.

So I went back to the original, made the edits I wanted and I'm happy with that file right now. It's attached as B-Train_Powered_Tanks_Darren.mpd.
I then went to the other mpd I had created and duplicated the subfile I wanted out to a new ldr which is attached here as Front_Tank.ldr.

When I open both of these files and go to the parts bin and drag the Front_Tank.ldr into the larger mpd, it inserts as individual parts instead of a submodel. It does the same thing whether I use the Ins key or I drag and drop it.

Attached Files

  B-Train_Powered_Tanks_Darren.mpd (Size: 104.83 KB / Downloads: 1)
  Front_Tank.ldr (Size: 58.46 KB / Downloads: 2)

the server forums.ldraw.org currently no longer seems to have a working icon associated.

I wonder if we could copy the favicon.ico from the parts tracker to there (or use a different one, maybe, with a different brick color, e.g. blue)