8099 - Midi-Scale Imperial Star Destroyer
OMR Compliant
Missing: Nothing
Comments: The hull plate angles are as close as they can be but there is still a small amount of part overlap.

Attached Files

  8099 - Midi-Scale Imperial Star Destroyer.mpd (Size: 22.2 KB / Downloads: 10)

As we are in the progress of amending the Sticker Specifications, what do you think of adding this one:

recently, LEGO started to print numbers next to their stickers to easier identify them, it looks like common sense to include this number as a letter in the part number, i.e. 01 -> "a", etc.
If there are more than 26 stickers on a sheet, they should be numbered as 27 -> aa, 28 -> ab

WOuld it make sense to add this and is it compatible with the library, i.e. was there enough common sense in the past to number the stickers accordingly since they introduced this scheme?

Hi all,

Is it possible to use a script to create a submodel in LDCad?
I ask this because I have to create multiple submodels that all require some basic other (LPub3D) metacommands and one or more parts, always in the same place.
This should be done by looping through a simple series of model names and descriptions.

I need to have submodels called A1, A2, A3, A4, .... A16
And B1, B2, B3 to B16 etc.
All the way to H.

Then I need submodels LA1, LA2, etc. to LH16

The A1, B1, etc. submodels should all have these lines:

Hello World,

Thank you for the amazing work!

I have been working on the packaging of ldraw for the conda package manager (both ldraw-parts and ldraw-list) and I have come across a couple of pitfalls I wanted to report back - even though it is not completely a blocker for moving forward.

1. mklist

- The mklist package does not build out of the box. Everyone (FreeBSD, Debian, ArchLinux) appears to be applying the same patches to the makefile and sources so that it builds succesfully (and I had to do so as well). It may be worth including these patches upstream and bump the version of mklist which has not been updated in a while. If the package was hosted on GitHub or GitLab, it may be easier to submit patches back.

- The mklist source tarball is included in the parts zip file, including built artefacts for windows. Since it is a very simple program, I think that it is fine to provide a built executable on the website, although the parts library and mklist may be better separated.

- Quick note if anyone on this forum is involved in the debian packaging: the version number for the ldraw-mklist debian package appears to be the same as for parts library, while it should really be 1.6.

2. Persistent source tarballs for the parts library

It seems that with every update of the parts library, the new parts are uploaded in a separate zip file, while the complete.zip file is overwritten with the new version of the full library.
This may be an issue because old versions of complete.zip are not available anymore and we can't use a persistent URL for a given version. If you kept a complete-????.zip around for each release, we would be able to point to it persistently.

I am looking forward to hearing back, and super excited to work on the packaging of the lego CAD stack for conda!

Cheers,

Hello,

I am working on some instructions that will use this part but in some other, custom, colors. Would it be possible to get this part re configured such that the panel is always trans clear and the color of the printing is the selectable color.

Thanks,
Cameron

Please vote on the following change to the Official Library Specification for Sticker Parts:

Update the following text:

Quote:The sticker pattern is modelled in its true colours; they are not modifiable from the outside. All printed colours of the pattern must be matched, and the background (non-printed portion) of the pattern must use colour 16. Mimicking a colour by blending in the background colour of the part underneath using colour 16 is not allowed.

Quote:The sticker pattern is modelled in its true colours; they are not modifiable from the outside. All colours of the top surface must be matched, and the back side and sides of the sticker must use colour 16. Print on a transparent plastic sticker sheet should use colour 16 on the transparent part of the top surface.

Currently, the following text exists in the sticker spec:

Quote:The sticker pattern is modelled in its true colours; they are not modifiable from the outside. All printed colours of the pattern must be matched, and the background (non-printed portion) of the pattern must use colour 16. Mimicking a colour by blending in the background colour of the part underneath using colour 16 is not allowed.

Quote:The sticker pattern is modelled in its true colours; they are not modifiable from the outside. All colours of the top surface must be matched, and the back side and sides of the sticker must use colour 16. Print on a transparent plastic sticker sheet should use colour 16 on the transparent part of the top surface.

Guys,

goes the hole in 11062 - Lamppost 2 x 2 x 7 with 4 Base Flutes through the entire part? How thick is this hole - 3 LDU?



Thx,

w.

It appears to have been 12 months since the last post in this forum so I thought I would bump one up.

Are there any things needing help for the running, maintenance or development of the LDraw group at the moment?

Whilst there are many people who I am sure are more qualified than I am on here, I am still happy to assist in any way possible. Even happy if this post is enough to bump the memory of those people with specialist knowledge to help in some way.

Cheer

Adam

Currently I've been using Buf3D+ on my Google Pixel 2 XL but I was curious to know if LDraw team has any plans to release a dedicated mobile client in near future..

______________________________________________________________________________________________________________________________________________________________________
Regards, [font=Tahoma, Verdana, Arial, sans-serif]Afynyth Showbox[/font]